berrergate-com-mcp.yml

BerrerGate publishes ONE remote MCP server at https://api.berrergate.com/mcp, declared in three places the provider controls: the API host's llms.txt ("MCP: POST https://api.berrergate.com/mcp"), an MCP server.json manifest at /.well-known/mcp/server.json (schema 2025-12-11, name com.berrergate/capability-wisdom, version 1.0.0, one streamable-http remote) and the AI Registry Discovery catalog, which describes it as a "Stateless MCP 2026-07-28 discovery/intake adapter" with ToolDiscovery, CapabilityCheck and PurchaseInstructions capabilities that "never settles money; canonical payment remains HTTP x402". The endpoint is live and speaks JSON-RPC 2.0, but its tool list could NOT be introspected: without an MCP-Protocol-Version header it answers HTTP 400 {"error":"A10A10_MCP_PROTOCOL_VERSION_REQUIRED", "required":"2026-07-28"}; with that header, initialize and tools/list in every standard shape (bare, params {}, params._meta.protocolVersion, top-level _meta) return -32600 "Invalid MCP request" or "MCP _meta protocolVersion required". The server's own CORS allow-list names non-standard request headers (mcp-protocol-version, mcp-method, mcp-name), which suggests a bespoke envelope a stock MCP client does not send. The tool names, count and inputSchemas are therefore unknown; nothing below is derived from the OpenAPI to stand in for them.

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.