VeriSwarm MCP Servers

VeriSwarm exposes the Model Context Protocol across several surfaces, each for a different job. This page is the map — start here to pick the right one.

The surfaces at a glance

Surface	Endpoint	Who connects	What it's for
Tools MCP	https://mcp.veriswarm.ai	an AI agent at runtime, or a human's AI assistant (Claude, ChatGPT)	call Guard/trust/PII/A2A tools mid-task
Customer Admin MCP	https://api.veriswarm.ai/mcp	you, administering your workspace	ask "what is happening in my workspace?"
Self-hosted MCP	PyPI veriswarm-mcp (you run it)	any client, inside your own trust boundary	the full toolset, incl. PII rehydration

The super-admin MCP (admin.veriswarm.ai) is VeriSwarm staff-only and not available to customers.

Which one do I want?

• Building an agent that should scan tool definitions, check trust decisions, or tokenize PII as it runs? → the Tools MCP.
• Connecting VeriSwarm to Claude or ChatGPT as a connector to inspect your workspace? → the Customer Admin MCP for workspace state, or the Tools MCP for runtime actions.
• Need to restore original PII values, or run entirely inside your own infrastructure? → the self-hosted server. PII rehydration is available only there — never on the hosted surfaces.

Each surface uses OAuth 2.0. Agents authenticate machine-to-machine (client_credentials); people authenticate through their AI assistant's connector flow (authorization_code).