Koskamo

Zambo MCP MCP server

Zambo provides a trust layer for AI work by executing real tasks and returning verifiable receipts. It offers tools for live data retrieval, website audits, text safety checks, and multi-agent continuity, allowing agents to perform verified actions without requiring API keys or user signups.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by Zambo
MCP endpoint (Streamable HTTP)
https://zambo.dev/mcp
Vendor documentation

What you can do with it

  • Check live cryptocurrency prices with source verification
  • Audit websites for infrastructure and SEO issues
  • Scan text for prompt injection and jailbreak risks
  • Execute multi-step jobs with verifiable execution receipts
Tools advertised by the last live check:
  • zambo_universal
  • new_session
  • continuity_get_recent
  • continuity_list_threads
  • continuity_open_thread
  • continuity_start_thread
  • continuity_set_prefs
  • journal_log
  • live_price
  • pdf_extract
  • leadsignal
  • provibe_audit
  • ghost_audit_site
  • ghost_audit_status
  • ghost_audit_report
  • credithunt
  • prompt_shield
  • day_pass_activate
  • capability_search

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http zambo-mcp https://zambo.dev/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add zambo-mcp --url https://zambo.dev/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable zambo-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "zambo-mcp": {
      "url": "https://zambo.dev/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.
Cline configuration
{
  "mcpServers": {
    "zambo-mcp": {
      "type": "streamableHttp",
      "url": "https://zambo.dev/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start zambo-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "zambo-mcp": {
      "type": "http",
      "url": "https://zambo.dev/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http zambo-mcp https://zambo.dev/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "zambo-mcp": {
      "url": "https://zambo.dev/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "zambo-mcp": {
      "serverUrl": "https://zambo.dev/mcp"
    }
  }
}

Do you run Zambo MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing