MCP

Agent tooling · same envelope as the API · $0 when idle

temsor runs one MCP remote server: com.temsor/api, listed in the official MCP registry. It exposes the same endpoints as api.temsor.com — business data (IBAN, phone and email validation) plus voice/call-ops agent tooling (call-search family) — as tools any MCP-capable agent can call. Try tools on the idle demo quota; sign up free when you need a key.

Temsor Portal is the HTTP control plane for approved access: email magic-link access, key management, and agent activity. Agents can run a dry-run with a deterministic eval gate; traces record pause, human handoff, and resume intent. Control-plane agent/traces routes are separate from MCP tools — MCP tools never place phone calls. Live calls happen only as a rate-limited “Call me” trial to your own mobile (available in selected countries) or on a line you have connected; no outbound calls to third parties. Idle $0.

Start free Docs Temsor Portal

Connect

Transport is streamable-http. The Authorization header is optional: without a key, calls run on a narrow per-IP demo quota so you can evaluate the tools first. Need a production key? Start free (email code, about 2 minutes), then create a key in Temsor Portal.

{
  "mcpServers": {
    "temsor": {
      "type": "streamable-http",
      "url": "https://api.temsor.com/mcp",
      "headers": {
        "Authorization": "Bearer fk_live_…"
      }
    }
  }
}

What you get back

One envelope on every call: { ok, data, meta }, or { ok:false, error:{ code, message } }.
Deterministic answers, most in single-digit milliseconds.
Tool descriptions are versioned; /v1/mcp/index lists the current surface.

Registry entry

Name com.temsor/api · endpoint https://api.temsor.com/mcp · namespace ownership proven at temsor.com/.well-known/mcp-registry-auth.

MCP is the agent tooling surface. Product overview stays on Docs; API catalogue under Docs → API catalog.