Is the Zambo MCP server down?

mcp-registry/dev.zambo/zambo · v4.0.0

Also listed as npm/zambo-ai

healthy
Last checked 2026-10-18 01:06 UTC · handshake 382ms

As of 2026-10-18 01:06 UTC, the Zambo MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 7 minutes.

uptime (30d checks)
100%
checks observed
2,773
outages (90d)
1
tools
35

Trust Layer for AI work. Give your AI hands. Every run returns a verifiable receipt. No key needed.

Install Zambo MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http zambo-mcp-server https://zambo.dev/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "zambo-mcp-server": {
      "type": "http",
      "url": "https://zambo.dev/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: B (81/100)

B (81/100): 0 error(s), 4 warning(s) across 35 tool(s); ~15,332 tokens of tool definitions.
Scores higher than 37% of 15,343 MCP servers Glimind has audited.
Its tool list costs an agent ~15,332 tokens per session — more than 90% of servers.
81 → 81 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions72
Safety hints100
Token cost49
Client compatibility100
Protocol100
Reliability85
Stability20

What to fix (5)

1 tool definition(s) exceed ~1,200 tokens each (largest: handover, ~1,512).

Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~912 tokens every session.

Tools: handover · saves ~912 tokens/session

37 parameter(s) across 9 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call.

Tools: handover, handover_accept, handover_list, handover_status, memory_recall and 4 more

Loading this server's tool list costs an agent ~15,332 tokens before any work — more than 90% of MCP servers.

Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request.

Handshake + tools/list takes ~1,660 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

In the last 30 days: 0 tool(s) removed and 109 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts.

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/dev.zambo/zambo"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/dev.zambo/zambo"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.zambo%2Fzambo.svg)](https://glimind.com/server/mcp-registry%2Fdev.zambo%2Fzambo?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fdev.zambo%2Fzambo?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.zambo%2Fzambo.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.zambo%2Fzambo.svg
   :target: https://glimind.com/server/mcp-registry%2Fdev.zambo%2Fzambo?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:aa1193e7aa5e2e05…, first seen 2026-10-18, included at leaf 19426 of 19,458. Version history · verify what your client received.

Tools (35)

Compare: most reliable productivity servers · most reliable search servers · most reliable communication servers · most reliable knowledge servers · most reliable security servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Zambo MCP server down right now?

As of 2026-10-18 01:06 UTC, the Zambo MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 7 minutes.

How many tools does Zambo MCP server provide?

Zambo MCP server advertises 35 tools, including activity_today, capability_search, continuity_get_recent, continuity_list_threads, continuity_open_thread.

How do I install Zambo MCP server?

Point your MCP client at this streamable-http endpoint: https://zambo.dev/mcp

Is the Zambo MCP server safe to connect to an AI agent?

Glimind scanned all 35 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Zambo MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.