Skip to content
MCP server

Namespace guard for merged toolboxes

Audits tool-name collisions before a new MCP server joins your merged toolbox

Install
Pricing
Free trial
Platforms
API
Runs
Remotely
Version
1.0.18
Listing updated
2 days ago

About Namespace guard for merged toolboxes

Namespace guard for merged toolboxes is an MCP server for security. It runs as a hosted remote server, so there is nothing to install locally.

When several MCP servers are attached to one agent and expose a tool with the same name, the agent cannot tell them apart, and the MCP specification has no namespace mechanism to fix that. This service checks a candidate server's tool names against your existing toolbox before you connect it, matching both exact and normalised names and grading trust. If there is a clash, it names the colliding publisher.

After the audit you can merge the servers with names bound to their publisher. For any call on a name that has ever collided, a signed routing receipt records which server handled it, under which rule, with a hash of the arguments. Raw arguments are never stored in a receipt.

The vendor is candid about limits: its fixture overlap figure is not a market number, the live overlap rate is unmeasured, receipt-chain checks only detect tampering against a pinned chain head, and host resolution rules are documentary rather than probed live.

Install

Run in a terminal

claude mcp add --transport http namespace-guard-for-merged-toolboxes https://textforagents.com/products/namespace-guard-for-merged-toolboxes/mcp

Add to Settings → Connectors → Add custom connector

https://textforagents.com/products/namespace-guard-for-merged-toolboxes/mcp
Install in CursorOpens Cursor, which asks you to confirm. Or add it by hand:

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "namespace-guard-for-merged-toolboxes": {
      "url": "https://textforagents.com/products/namespace-guard-for-merged-toolboxes/mcp"
    }
  }
}
Install in VS CodeOpens VS Code, which asks you to confirm. Or add it by hand:

Add to .vscode/mcp.json

{
  "servers": {
    "namespace-guard-for-merged-toolboxes": {
      "type": "http",
      "url": "https://textforagents.com/products/namespace-guard-for-merged-toolboxes/mcp"
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "namespace-guard-for-merged-toolboxes": {
      "serverUrl": "https://textforagents.com/products/namespace-guard-for-merged-toolboxes/mcp"
    }
  }
}

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "namespace-guard-for-merged-toolboxes": {
      "type": "http",
      "url": "https://textforagents.com/products/namespace-guard-for-merged-toolboxes/mcp"
    }
  }
}

What it does

Pre-connection audit
Compares a new server's tool names with your toolbox before it is attached.
Exact and normalised matching
Catches near-duplicate names as well as identical ones.
Trust grading
Grades the result and names the colliding publisher.
Signed routing receipts
Records server, rule and an args hash for calls on names that collided.
Fleet and org passes
Standing re-audits when a tool list changes or a server joins.

Good for

  • Vet a new MCP server before connecting it to an agent fleet
  • Prove which server handled a call on an ambiguous tool name
  • Keep a shared toolbox audited as servers change

Pricing

Free trial, from $9.99 a month

One free audit per operator; $4.99 per audit, $9.99 to $49.99 per month plans

Prices change. Check textforagents.com before you buy.

Namespace guard for merged toolboxes FAQ

What does a collision audit cost?

$4.99 per server audited; verdict queries are $0.01 each, and each operator gets one free audit.

What do receipts contain?

The server, the rule applied and an args hash; raw arguments are never included.

How do I start?

POST /register, then POST /trial/claim to get an API token and the one-time trial grant.

What are the monthly plans?

Routing receipts add-on $9.99 per fleet, fleet pass $19.99 per fleet and organisation pass $49.99 per org.

Is Namespace guard for merged toolboxes free?

Namespace guard for merged toolboxes is a paid product with a free trial. Paid plans start at $9.99 a month.

How do I add Namespace guard for merged toolboxes to Claude Code?

Run this command in your terminal: claude mcp add --transport http namespace-guard-for-merged-toolboxes https://textforagents.com/products/namespace-guard-for-merged-toolboxes/mcp

What are the best alternatives to Namespace guard for merged toolboxes?

The closest alternatives to Namespace guard for merged toolboxes are REA, Codebase Memory, GitHub, Serena MCP: the IDE for your agent and XERJ.

Alternatives to Namespace guard for merged toolboxes

  1. REA

    MCP server

    CLI and MCP server that lets coding agents reverse engineer apps and binaries

    Runs locally
    • Open source
    • 464K GitHub stars
    • Developer tools
  2. Codebase Memory

    MCP server

    Local MCP server that builds a code knowledge graph for AI coding agents

    Runs locally
    • Open source
    • 48.7K GitHub stars
    • Knowledge and memory
  3. GitHub

    MCP server

    Official MCP server connecting AI assistants to GitHub repos, issues and workflows

    Not checked yet
    • Remote
    • Open source
    • 34.5K GitHub stars
    • Developer tools
  4. MCP toolkit giving coding agents symbol-level code retrieval and editing

    Runs locally
    • Open source
    • 31.5K GitHub stars
    • Developer tools
  5. XERJ

    MCP server

    Local search engine for AI agents with cited answers over your code and docs

    Runs locally
    • Open source
    • 19.2K GitHub stars
    • Knowledge and memory
  6. Ouroboros

    MCP server

    Spec-first layer that pins requirements and verifies results of AI coding agent work

    Runs locally
    • Open source
    • 6.4K GitHub stars
    • Developer tools