agenthaven-dev-mcp.yml
Agent Bench operates ONE remote MCP server at https://travel.agenthaven.dev/mcp, on the same host as its A2A JSON-RPC endpoint (/a2a) and its documentation. It is POST-only Streamable HTTP without server-initiated streams (a GET returns 405 {"error":{"code":"sse_unsupported","message":"This MCP endpoint does not open server-initiated streams. POST JSON-RPC messages instead."}}), speaks MCP protocol version 2025-06-18, identifies itself as serverInfo {name: agent-bench-travel-merchant, version: 0.1.0}, and answers initialize and tools/list anonymously with two tools carrying full JSON Schema inputSchema AND outputSchema (draft-07), with examples, patterns and const constraints. resources/list and prompts/list return -32601 with a message naming the implemented set: "initialize, ping, tools/list and tools/call". The server is provider-built — the tool names, the merchant_id const "demo-travel-seller" and the mandate/ledger vocabulary match no shared platform fingerprint. The A2A agent card advertises this endpoint in supportedInterfaces[1] and delegates its skill schemas to it. This is the machine-readable contract for the provider: there is no OpenAPI.
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.
Documentation
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.