getvda-ai-mcp.yml

Verified Digital Agents runs FOUR live remote MCP surfaces on its own hosts plus a 98-server metered fleet, all Streamable HTTP (POST JSON-RPC 2.0) and all probed anonymously on 2026-09-19. (1) Witness at https://witness.getvda.ai/api/witness/mcp — protocol 2024-11-05, serverInfo {vda-witness 1.0.0, vendor "Verified Digital Agents (VDA)"}, 16 tools with real inputSchemas returned to an anonymous tools/list; discovery, `verify`, `verify_record_issuer`, `check_valid` and free key minting (`get_test_key`) need no credential, sealing needs the Witness bearer key the server itself mints. (2) C2MD at https://c2md.getvda.ai/mcp — protocol 2024-11-05, serverInfo {c2md-compliance-agent 1.0.0}, 11 tools; initialize/tools/list/`assess_agent_risk`/`get_test_key` are anonymous, the generative tools need a Witness bearer whose account tier maps to the c2md:* scopes. (3) HITL at https://hitl.getvda.ai/mcp — GATED: initialize itself answers 401 {"error":"unauthorized","message":"missing bearer credential"}; its 9 tools (raise/list/get/resolve items, baselines, authority config, quota) are documented with inputSchemas in the served agent card and mirror the REST /v1/tools/* operations 1:1 in the OpenAPI. (4) The GOSCE Portfolio Router at https://router.getvda.ai/mcp — protocol 2026-07-28, serverInfo {router 0.1.0}, 2 tools (invoke, selftest); `invoke` answered anonymously with the capability index (the router's free tier). Behind it sit 98 templated fleet servers (.getvda.ai/mcp, 2 tools each, invoke metered at $0.025 USDC per call via x402 v2 or a Stripe card rail, selftest free), enumerated in well-known/getvda-ai-agents-ai-catalog.json. ACP declares an MCP surface as PLANNED in its agent card (mcp.status: planned) and POST /mcp on acp.getvda.ai is a 404 — it is recorded here as absent, not derived. Authorship is unambiguous: every serverInfo/vendor string, tool name and description is VDA-specific (seal_hitl_decision, issue_admission_credential, generate_dpia_fria_scaffold) and matches no shared-platform fingerprint.

One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.

Provider: Verified Digital Agents (VDA) Type: Documentation link Transport: Host: witness.getvda.ai

Documentation

https://witness.getvda.ai/api/witness/mcp

Documentation link · transport

About MCP

The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.

Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.

Work with this as data

Every MCP server here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for mcp servers

4 MCP tools reach this
  • find_mcpBrowse and filter every MCP server in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This MCP server
curl "https://apis.io/api/v1/mcp/getvda-ai-mcp-yml"
All mcp servers
curl "https://apis.io/api/v1/mcp?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.