mcp-registry/bz.manda/manda · v1.0.0
Verdict. Manda MCP server answered 100% of Glimind's liveness checks over 30 days, better than 42% of MCP servers, with 693 ms median handshake and 2 outages in 90 days. Its agent-readiness grade is A (100/100) across 4 tools, costing an agent about 465 tokens to load. Checked every few minutes; no tool is ever called.
Data as of .
| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 100% | 42% of MCP servers |
| Median handshake latency | 693 ms | 35% of MCP servers |
| p95 handshake latency | 2987 ms | — |
| Checks in 30 days | 4,991 | — |
| Outages, 90 days | 2 | — |
| Median recovery | 6 min | — |
| Agent-readiness score | 100/100 (A) | 94% of MCP servers |
| Tools | 4 | — |
| Tool-list size for an agent | ~465 tokens | 90% of MCP servers |
| Days observed | 29 | — |
Compare: vs Pipe2 MCP server · vs Racecalendar F1 MCP server · vs Forum MCP server · vs Doc MCP server
As of 2026-10-27 02:42 UTC, the Manda MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 6 minutes.
Search Japan's M&A marketplace MANDA - public business-for-sale listings (read-only, no auth)
Claude Code
claude mcp add --transport http manda-mcp-server https://manda.bz/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"manda-mcp-server": {
"type": "http",
"url": "https://manda.bz/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
No problems found.
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/bz.manda/manda"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/bz.manda/manda"}) over MCP.
search_deals ~270 tokensget_deal ~99 tokenslist_industries ~51 tokenslist_areas ~45 tokensStatic 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:
[](https://glimind.com/server/mcp-registry%2Fbz.manda%2Fmanda?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fbz.manda%2Fmanda?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fbz.manda%2Fmanda.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fbz.manda%2Fmanda.svg :target: https://glimind.com/server/mcp-registry%2Fbz.manda%2Fmanda?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:9555760665c728ed…, first seen 2026-10-17, included at leaf 11935 of 76,891. Version history · verify what your client received.
Compare: most reliable data servers · most reliable search servers
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.
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"
}
}
}
As of 2026-10-27 02:42 UTC, the Manda MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 6 minutes.
Manda MCP server advertises 4 tools, including get_deal, list_areas, list_industries, search_deals.
Point your MCP client at this streamable-http endpoint: https://manda.bz/mcp
Glimind scanned all 4 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.
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.