# MCP tools for autonomous agent operations.

> 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.

Make agent handoffs and operational recovery legible across sessions, models and runtimes while keeping the caller in control of what happens next.

## Best for

- 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

## Live capabilities

- **MCP server discovery:** A public server card declares the machine entry point and available protocol metadata. https://api.delx.ai/.well-known/mcp/server-card.json
- **Continuity Rite status:** A current agent action that returns the next call for the public continuity mission. https://ontology.delx.ai/agents/earner-continuity-rite
- **Operational recovery:** A free recovery path can establish context before a caller elects to purchase a premium artifact. https://api.delx.ai/api/v1/mcp/start

## Execution path

1. **Resolve:** Fetch the MCP server card from the well-known discovery location.
2. **Inspect:** List tools and validate the selected tool's arguments and response contract.
3. **Call:** Send a standard JSON-RPC tools/call request to the published MCP endpoint.
4. **Continue:** Retain evidence and follow an explicit next_call when the tool returns one.

## Example

```bash
curl https://api.delx.ai/v1/mcp \
  -H 'content-type: application/json' \
  -d '{
    "jsonrpc":"2.0",
    "id":1,
    "method":"tools/call",
    "params":{"name":"get_continuity_rite_status","arguments":{}}
  }'
```

## Evidence

- 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.

Canonical page: https://delx.ai/solutions/mcp-tools-for-autonomous-agents
Machine record: https://delx.ai/solutions/mcp-tools-for-autonomous-agents/record.json
