Npx castov audit – find secrets hiding in your MCP setup

Castov launched a developer utility suite spanning web interfaces, terminal execution via npx castov, and AI agent integration through the Model Context Protocol, as detailed in castov.com's report. The platform provides 61 total browser utilities alongside a dedicated 13-tool MCP server designed to operate directly inside environments like Cursor and Claude. The release emphasizes zero-data logging and local client-side execution, running cryptography, JSON validation, timestamp conversions, and JWT inspections within local device memory using WebCrypto. For terminal environments, the company distributes a global npm package alongside a container image on Docker Hub that executes the CLI and MCP runtime inside an isolated, non-root Alpine container with a 50MB footprint.

This report examines Castov's local developer toolkit, focusing on its auditing functions, security scanners, runtime architecture, and integration with agentic coding environments. It is intended for software engineers, DevOps specialists, and security practitioners who integrate local command-line tools and Model Context Protocol servers into automated developer workflows. The suite combines everyday formatters with zero-knowledge secret vaults, universal configuration synchronizers, and local browser sandboxes. By reviewing the exact capabilities, container parameters, encryption standards, and protocol bindings, teams can evaluate how to inspect their local toolchains and safeguard sensitive operational credentials from external server leakage.

Npx castov audit – find secrets hiding: what actually changed

Castov unified its utility catalog into a cross-platform architecture that executes identical toolsets across web browsers, local terminal sessions, and AI coding agents. The company introduced Castov DevShell v0.2.0, an in-browser sandbox that simulates the full command-line suite using WebCrypto primitives and instant data transforms. Users can execute utilities through the npx castov runner, install the package globally using npm i -g castov, or invoke castov mcp to launch Model Context Protocol communication. The system organizes 61 distinct tools into dedicated operational categories, including timestamp parsers, date and duration calculators, timezone converters, general developer utilities, and experimental labs.

Rather than treating developer utilities as disconnected web calculators, the platform introduced chained tool pipelines that pass outputs between utilities in a single step without manual clipboard transfers. A JSON structure can pipe directly into TypeScript interfaces, cron schedules can project directly across international time zones, and structural diffs can stream into schema generators. The system incorporates encrypted URL sharing, where entire state payloads, diffs, and settings are compressed directly into the URL hash fragment. Because hash fragments are not transmitted to host servers during HTTP requests, the operational data remains strictly client-side during team link sharing.

Npx castov audit – find secrets hiding: how it works

The execution layer operates locally by default, avoiding remote server logging by performing cryptographic operations and text transforms within local memory. Developers running terminal tasks can use npx castov or deploy the official castovdev/castov:latest container from Docker Hub. The container runs on an Alpine Linux base with an approximate 50MB footprint, enforcing non-root execution under USER node and streaming MCP transport messages directly over stdin and stdout. For AI assistant integration, the 13-tool MCP server exposes utilities to Claude and Cursor, allowing agents to call core developer functions programmatically through standard input and output streams without external network egress.

Security and configuration analysis relies on specialized tools within the 33-item developer category, notably the Universal Secret Scanner and the Zero-Knowledge .env Vault. Teams manage credentials through RSA-OAEP encrypted Team Vaults connected via GitHub OAuth or through browser-native steganography that hides AES keys inside standard image pixels. For collaborative workflows, Castov includes a peer-to-peer multiplayer canvas built with WebRTC data channels and Yjs conflict-free replicated data types. Public signaling servers manage initial connection metadata, but the underlying workflow graphs and data payloads remain restricted to peer nodes without persistence on central servers.

Npx castov audit – find secrets hiding: why it matters

Command-line utilities and AI editor extensions frequently expose sensitive corporate configuration data to third-party infrastructure through tracking telemetry or cloud-assisted parsing. By enforcing client-side WebCrypto execution across all core utilities, Castov prevents API tokens, private keys, and structured payloads from touching external network hosts. Developers debugging authorization headers can decode JSON Web Tokens, inspect Unix timestamps, or calculate CIDR network blocks without leaking internal network topologies or proprietary identity tokens to third-party logging engines. The absence of server tracking ensures compliance with strict enterprise development standards.

The integration of Model Context Protocol tooling addresses security visibility inside agentic development environments. When coding assistants like Claude or Cursor run shell scripts or access configuration files, embedded credentials inside local files create operational exposure. Castov provides specialized components such as the Universal Secret Scanner, Shadow API Load Tester, and Universal Config Sync to evaluate local project trees. Operating these audits through an isolated container footprint or a zero-telemetry MCP pipeline enables engineering teams to inspect sensitive assets without sending authentication secrets across public cloud application programming interfaces.

Npx castov audit – find secrets hiding: who is affected

Software engineers using Cursor, Claude, and terminal-based workflows are directly affected by the availability of standardized MCP server tooling. Teams that routinely manage secret material across distributed environments can use the encrypted Team Vaults to exchange .env files using RSA-OAEP encryption, replacing the cleartext pasting of credentials into internal chat applications. Frontend engineers can deploy the platform's Service Worker API Mocker, which intercepts GET /api/v1/users and similar routes to return mock user objects entirely within the browser, enabling frontend component testing without maintaining an active backend server.

DevOps engineers and system administrators managing CI/CD pipelines can deploy Castov utilities within containerized environments using the official Docker image. Because the container runs with a 50MB footprint as the node user with zero host dependencies, automation pipelines can run linting, diff checking, and schema generation steps securely. The suite also provides distributed tooling for development teams through its Homebrew tap, Open VSX registry, VS Code marketplace, GitHub Actions, and Firefox add-on distributions, allowing organizations to standardize conversion and inspection scripts across disparate developer workstations.

Npx castov audit – find secrets hiding: what to watch

Adoption patterns around local client-side developer tooling will depend on how Castov expands its experimental labs and monetizes its free infrastructure. The platform currently offers all 61 tools without fees, user accounts, or usage limitations, though the project notes that display advertisements may appear in the future to offset operational hosting costs. Certain collaborative features deliberately touch external networks, including encrypted cloud syncing for registered GitHub workspaces, public STUN discovery for P2P Ghost Tunnel connections, and signaling servers for WebRTC canvas coordination, requiring teams to monitor network boundaries.

Engineering organizations should track developments across Castov's 10 experimental lab projects, which explore advanced browser-native capabilities. These initiatives include the P2P Ghost Tunnel for localhost sharing via WebRTC, the Steganography Env Vault for embedding configuration keys into PNG image pixels, and AST Conflict Telepathy for semantic Git merge resolution. Additional experiments feature local regex evolution via genetic algorithms, in-browser WebGL computing through the Holographic JSON Explorer, and decentralized WebGPU AI workloads on NexusGrid, signaling a broader migration of complex engineering toolchains into sandboxed, local execution environments.