{"schema":"delx/institutional-solution/v1","canonical":"https://delx.ai/solutions/mcp-tools-for-autonomous-agents","markdown":"https://delx.ai/solutions/mcp-tools-for-autonomous-agents/index.md","slug":"mcp-tools-for-autonomous-agents","eyebrow":"MCP tools","title":"MCP tools for autonomous agent operations.","description":"Give agents a standards-based path to discover tools, preserve operational continuity and execute against explicit contracts.","directAnswer":"Delx exposes an MCP server card and JSON-RPC endpoint for autonomous agents that need discoverable operational tools. Agents can inspect the published surface, call free continuity and recovery tools, and follow returned next actions without relying on undocumented prompts.","outcome":"Make agent handoffs and operational recovery legible across sessions, models and runtimes while keeping the caller in control of what happens next.","bestFor":["Long-running agents that cross context windows or model sessions","Multi-agent workflows that need explicit handoffs and recovery paths","Builders adopting MCP without coupling to a private adapter"],"capabilities":[{"name":"MCP server discovery","description":"A public server card declares the machine entry point and available protocol metadata.","href":"https://api.delx.ai/.well-known/mcp/server-card.json"},{"name":"Continuity Rite status","description":"A current agent action that returns the next call for the public continuity mission.","href":"https://ontology.delx.ai/agents/earner-continuity-rite"},{"name":"Operational recovery","description":"A free recovery path can establish context before a caller elects to purchase a premium artifact.","href":"https://api.delx.ai/api/v1/mcp/start"}],"steps":[{"name":"Resolve","description":"Fetch the MCP server card from the well-known discovery location."},{"name":"Inspect","description":"List tools and validate the selected tool's arguments and response contract."},{"name":"Call","description":"Send a standard JSON-RPC tools/call request to the published MCP endpoint."},{"name":"Continue","description":"Retain evidence and follow an explicit next_call when the tool returns one."}],"proof":["The server card, MCP schema and JSON-RPC endpoint are public and independently inspectable.","The institutional domain preserves stable MCP discovery links for existing consumers.","Continuity actions return explicit next steps instead of relying on hidden conversational state."],"boundaries":["The MCP discovery surface does not imply that every Delx paid service is an MCP tool.","Callers must inspect each tool schema and should not send secrets unless a contract explicitly requires and protects them.","Delx Ontology owns the experimental continuity protocol; Delx Commerce owns paid service terms."],"codeLabel":"JSON-RPC · MCP tool call","code":"curl https://api.delx.ai/v1/mcp \\\n  -H 'content-type: application/json' \\\n  -d '{\n    \"jsonrpc\":\"2.0\",\n    \"id\":1,\n    \"method\":\"tools/call\",\n    \"params\":{\"name\":\"get_continuity_rite_status\",\"arguments\":{}}\n  }'","primary":{"label":"Open the MCP server card","href":"https://api.delx.ai/.well-known/mcp/server-card.json"},"secondary":{"label":"Read integration guidance","href":"/developers"},"faqs":[{"question":"Where is the Delx MCP server card?","answer":"The canonical MCP server card is published at api.delx.ai/.well-known/mcp/server-card.json and is also linked from the delx.ai discovery graph."},{"question":"Can an MCP client use Delx without a proprietary SDK?","answer":"Yes. Delx publishes standards-based discovery and JSON-RPC entry points. A client should still inspect the current server card and tool schemas before calling them."},{"question":"Are MCP tools and x402 APIs the same catalog?","answer":"No. They are related discovery and execution surfaces with explicit ownership. Individual capabilities declare which protocols they actually support."}]}