English Français العربية

Namespace guard for merged toolboxes

Official registry Security

Pre-connection collision audit for merged MCP toolboxes, trust-graded, with signed routing receipts.

Website

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http namespace-guard-for-merged-toolboxes 'https://textforagents.com/products/namespace-guard-for-merged-toolboxes/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "namespace-guard-for-merged-toolboxes": {
            "type": "http",
            "url": "https://textforagents.com/products/namespace-guard-for-merged-toolboxes/mcp"
        }
    }
}

Frequently asked questions

What is Namespace guard for merged toolboxes?

Pre-connection collision audit for merged MCP toolboxes, trust-graded, with signed routing receipts.

How do I install Namespace guard for merged toolboxes?

It runs as a remote server. In Claude Code: claude mcp add --transport http namespace-guard-for-merged-toolboxes 'https://textforagents.com/products/namespace-guard-for-merged-toolboxes/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Namespace guard for merged toolboxes need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Who maintains Namespace guard for merged toolboxes?

It is published by com.textforagents. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.