API docs by Redocly

MasterDB hosted MCP endpoints (1.0.0)

Download OpenAPI specification:

URL: https://docs.masterdb.ai License: LicenseRef-MasterDB

The Model Context Protocol endpoints MasterDB hosts — where hosting cannot cost anything.

MasterDB hosts three MCP servers over the Streamable HTTP transport. Each is one endpoint that takes MCP's JSON-RPC messages; the tools, resources and prompts are discovered through MCP itself (tools/list), not described here. What this document fixes is the HTTP surface: the endpoint, how it authenticates, and how it refuses.

  • Public (mcp.masterdb.ai): the public verification reads only — verify a record you hold, a certificate, the key set, a projection, the log, the vocabularies. No credential and nothing billable; no search and no fetch.
  • Business (mcp.business.masterdb.ai): a business's own MCP client, signed in as a person of the business. Drafts are validated and prepared; publishing is never done here — the publish tool returns a link to the Business Portal's Save screen, where the person reviews the change and seals it with their passkey.

MasterDB never hosts a billable MCP server: production retrieval is only ever a request signed by the AI company's own key, from its own masterdb-mcp.

Sessions: the initialize answer carries an Mcp-Session-Id; send it on every later request of the conversation. A session is bound to the credential that opened it and ends after 30 minutes idle. There is no server-initiated stream: GET answers 405, and DELETE with the session id ends a session. Responses are JSON (enableJsonResponse).

MCP

The hosted Model Context Protocol endpoints.

The public MCP server

MCP over Streamable HTTP for the public verification reads: tools verify, certificate, keys, projection, spec, log_checkpoint, log_proof and vocabularies. No credential. Rate-limited per client address generously, so as never to block a checker. The client must accept both application/json and text/event-stream (406 otherwise).

Request Body schema: application/json
required

One JSON-RPC 2.0 message of the Model Context Protocol, or a batch of them.

One of
jsonrpc
required
any
Value: "2.0"
id
string or integer or null
method
string
object
object
object
property name*
additional property
any

Responses

Request samples

Content type
application/json
{
  • "jsonrpc": "2.0",
  • "id": 1,
  • "method": "initialize",
  • "params": {
    }
}

Response samples

Content type
application/json
{
  • "jsonrpc": "2.0",
  • "id": 1,
  • "result": {
    }
}

The business-side MCP server

MCP over Streamable HTTP for a business's own MCP client, signed in as a person of the business (the portal's own sign-in session). Tools: draft (create or edit a draft and validate it with every reason), publish (validate, show the change, and return the link to the Business Portal's Save screen, where the person seals with their passkey — the seal is never made here), status (drafts, publication state, where a record is live) and receipts_for_my_records (publish receipts and who is asking). Every call runs under the person's own grants in the portal API; this server can never seal, spend, change people, place or lift a block, or change keys. Rate-limited per person.

Authorizations:
identityPlatformBearer
Request Body schema: application/json
required

One JSON-RPC 2.0 message of the Model Context Protocol, or a batch of them.

One of
jsonrpc
required
any
Value: "2.0"
id
string or integer or null
method
string
object
object
object
property name*
additional property
any

Responses

Request samples

Content type
application/json
{
  • "jsonrpc": "2.0",
  • "id": 1,
  • "method": "initialize",
  • "params": {
    }
}

Response samples

Content type
application/json
{
  • "jsonrpc": "2.0",
  • "id": 1,
  • "result": {
    }
}