Preview. The MCP endpoint runs at https://api.agentcontinuity.net/mcp; nothing is for sale. It is listed in the official MCP Registry as net.agentcontinuity/memory.

MCP integration

MCP server

What is implemented

endpoint: https://api.agentcontinuity.net/mcp (planned; not live)
transport: Streamable HTTP. POST carries one JSON-RPC 2.0 message per request and returns application/json. GET returns 405 because there is no server-initiated stream. The server is stateless and issues no Mcp-Session-Id.
protocol versions: 2025-11-25, 2025-06-18, 2025-03-26, negotiated through initialize. An unsupported MCP-Protocol-Version header is rejected with 400.
methods: initialize, notifications/initialized, ping, tools/list, tools/call
authentication: Authorization: Bearer <api key> on tools/call. initialize, tools/list and the get_pricing tool need no key.
browser origins: Requests that carry an Origin header are refused (DNS-rebinding protection). Agents call server-to-server.

Not implemented

The 2026-07-28 stateless revision (server/discover, per-request _meta).
Resources, prompts, sampling, elicitation and SSE streams.
MCP OAuth authorization. API keys are used instead; the MCP spec makes authorization optional.
The stdio transport (no local package is published).

Tools

There is one tool for each operation in capabilities. Each tool's inputSchema is the JSON Schema of the same parameter model the REST API validates. Write tools take an optional idempotency_key argument. Annotations set readOnlyHint, destructiveHint and idempotentHint.

A tool result carries structuredContent (the same JSON as the REST response) and the same JSON as text in content[0]. An operation failure is a tool result with isError: true, and its structuredContent holds the standard error envelope. Protocol faults, such as an unknown tool or bad JSON, are JSON-RPC errors.

Example

POST /mcp
Accept: application/json, text/event-stream
Content-Type: application/json
Authorization: Bearer ac_3f9a0c1d2e4b_...

{"jsonrpc": "2.0", "id": 7, "method": "tools/call",
 "params": {"name": "save_memory",
            "arguments": {"workspace_id": "6f1c2a4e-1b9d-4a51-9a4e-2f0f5d3c8b10",
                          "key": "session-state", "content": "resume at shard 7",
                          "idempotency_key": "save-41"}}}

200 OK
{"jsonrpc": "2.0", "id": 7, "result": {
   "content": [{"type": "text", "text": "{\"memory_id\": \"…\", \"version\": 1, …}"}],
   "structuredContent": {"memory_id": "…", "key": "session-state", "version": 1,
                         "content_sha256": "…", "created": true, …},
   "isError": false}}

Client configuration (once deployed)

{
  "mcpServers": {
    "agentcontinuity": {
      "type": "http",
      "url": "https://api.agentcontinuity.net/mcp",
      "headers": {"Authorization": "Bearer ${AGENTCONTINUITY_API_KEY}"}
    }
  }
}

Registry and directory status

Listed in the official MCP Registry as net.agentcontinuity/memory (version 0.1.0, namespace verified through this domain). Verified clients: the official MCP Python SDK (2.3.0, Streamable HTTP), curl, and Python standard-library JSON-RPC calls. No other directory listing, compatibility certification or endorsement is claimed. Working calls: examples.