MCP server
Your AI can query Continuum. The record — register-verified entities, cited facts, approved relationships — is exposed over the Model Context Protocol, so Claude and any MCP-capable agent can answer from it with sources attached.
Connect
Endpoint: https://continuumalternatives.com/api/mcp (Streamable HTTP) · auth via an API key from /account/api as a Bearer header.
Claude (claude.ai / Claude Desktop custom connector)
URL: https://continuumalternatives.com/api/mcp Header: Authorization: Bearer ca_live_...
Generic MCP client (TypeScript SDK)
import { Client } from "@modelcontextprotocol/sdk/client/index.js";
import { StreamableHTTPClientTransport } from "@modelcontextprotocol/sdk/client/streamableHttp.js";
const transport = new StreamableHTTPClientTransport(
new URL("https://continuumalternatives.com/api/mcp"),
{ requestInit: { headers: { Authorization: "Bearer ca_live_..." } } },
);
const client = new Client({ name: "my-agent", version: "1.0.0" });
await client.connect(transport);
const result = await client.callTool({ name: "search_entities", arguments: { query: "uljanik" } });Tools
search_entities
Parameters: query (text) · kind? · country? (ISO-2)
Matching active entities with slug, kind, country, tags, profile URL.
get_entity
Parameters: slug
Full profile: identity, tags, approved classifications, stats, steward statement.
get_timeline
Parameters: slug · since? (YYYY-MM-DD)
Approved facts in date order, EACH with source name + URL.
list_facts
Parameters: channel? · asset_class? · country? · since? · limit? (≤200)
Newest approved facts across the record, entity + source attached.
get_coverage
Parameters: —
The taxonomy coverage table — which asset classes carry real entity/signal depth.
my_watchlist
Parameters: —
The key owner's watched entities with latest activity (scoped to YOUR key).
Same limits and coverage as the REST API (60 req/min/key, read-only, approved data only — see /docs/api). Tool outputs always carry source names and URLs, so your agent can cite what it read.