Skip to content
DELX

MCP tools

MCP tools for autonomous agent operations.

Give agents a standards-based path to discover tools, preserve operational continuity and execute against explicit contracts.

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.

Open the MCP server cardRead integration guidance
MarkdownJSONOpenAPI

Outcome

A precise job, not a generic promise.

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

01

Long-running agents that cross context windows or model sessions

02

Multi-agent workflows that need explicit handoffs and recovery paths

03

Builders adopting MCP without coupling to a private adapter

Live capability map

Start from a governed contract.

Each capability links to the property that owns its current terms. Inspect that source immediately before execution.

MCP server discovery

A public server card declares the machine entry point and available protocol metadata.

Inspect the contract →

Continuity Rite status

A current agent action that returns the next call for the public continuity mission.

Inspect the contract →

Operational recovery

A free recovery path can establish context before a caller elects to purchase a premium artifact.

Inspect the contract →

Execution

Readable by a person. Runnable by an agent.

The same path can be evaluated manually, embedded in a toolchain or followed autonomously within a bounded authorization.

  1. ResolveFetch the MCP server card from the well-known discovery location.
  2. InspectList tools and validate the selected tool's arguments and response contract.
  3. CallSend a standard JSON-RPC tools/call request to the published MCP endpoint.
  4. ContinueRetain evidence and follow an explicit next_call when the tool returns one.
JSON-RPC · MCP tool call
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

What can be verified.

  • 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

What is not being claimed.

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

Direct answers

Questions agents and evaluators ask.

Visible answers mirror the structured data on this page.

Where is the Delx MCP server card?

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.

Can an MCP client use Delx without a proprietary SDK?

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.

Are MCP tools and x402 APIs the same catalog?

No. They are related discovery and execution surfaces with explicit ownership. Individual capabilities declare which protocols they actually support.