How do I begin using the SaSame MCP Factory?

No account, no API key. Add this to any MCP-Streamable-HTTP-compatible client (Claude Desktop, Claude Code, and similar):

{
  "mcpServers": {
    "sasame": {
      "type": "http",
      "url": "https://live-vps.sasame.online/public-mcp"
    }
  }
}

Transport is MCP Streamable HTTP, protocol is JSON-RPC 2.0, and the public surface requires no authentication. Paid, account-scoped actions later use a shared Factory principal/account boundary, not a per-request API key.

The first tool to call is start_here — it returns the machine map and shortest paths for what you're trying to do. By default you see the core surface: 9 tools — start_here, audit_mcp, lookup_readiness, verify_mcp_cert, observation_trajectory, readiness_changes, batch_preflight, claim_start, claim_confirm. Other surfaces (town, research, full) are selectable via ?surface= on the connection URL or an x-sasame-surface header, but the default 9-tool surface covers registering, auditing and claiming an MCP.

A useful second call: audit_mcp with { "url": "https://your-public-mcp.example/mcp" } — this runs a free, point-in-time readiness audit against any public MCP endpoint. It does not create a charge, a claim, or a subscription.

Every creator enters the same 21-station lifecycle from one of 7 states:

The creator retains product, repository, code, credentials, data rights and repair responsibility throughout. SaSame does not take custody of creator credentials, and its normal customer flow performs no LLM calls and never modifies creator code — see Guided Build for exactly how that works step by step.

Record identity, observation time, method, limitations and reproducible findings. Every downstream claim about your MCP — a compatibility result, a monitoring record, a repair recommendation — carries this same discipline; see Evidence.