mcp-registry/com.datahyena/signals · v1.0.0
Verdict. Datahyena Signals MCP server answered 99.87% of Glimind's liveness checks over 30 days, better than 27% of MCP servers, with 1067 ms median handshake and 8 outages in 90 days. Its agent-readiness grade is A (90/100) across 13 tools, costing an agent about 8,712 tokens to load. Checked every few minutes; no tool is ever called.
Data as of .
| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 99.87% | 27% of MCP servers |
| Median handshake latency | 1067 ms | 20% of MCP servers |
| p95 handshake latency | 3335 ms | — |
| Checks in 30 days | 4,883 | — |
| Outages, 90 days | 8 | — |
| Median recovery | 7 min | — |
| Agent-readiness score | 90/100 (A) | 69% of MCP servers |
| Tools | 13 | — |
| Tool-list size for an agent | ~8,712 tokens | 32% of MCP servers |
| Days observed | 29 | — |
As of 2026-10-26 20:40 UTC, the Datahyena Signals MCP server is up with a Glimind reliability score of 87/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 8 outages in 90 days, with a median recovery of 7 minutes.
Deduplicated, entity-resolved funding rounds, acquisitions, and exec moves as MCP tools.
Claude Code
claude mcp add --transport http datahyena-signals-mcp-server https://api.datahyena.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"datahyena-signals-mcp-server": {
"type": "http",
"url": "https://api.datahyena.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
3 tool definition(s) exceed ~1,200 tokens each (largest: hiring_signals, ~1,767).
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 ~2,668 tokens every session. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
In the last 30 days: 0 tool(s) removed and 13 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. How to fix →
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/com.datahyena/signals"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.datahyena/signals"}) over MCP.
hiring_signals ~1,767 tokensfunding_events ~1,470 tokensacquisitions ~1,231 tokensexec_moves ~1,085 tokenscompanies ~974 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%2Fcom.datahyena%2Fsignals?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.datahyena%2Fsignals?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.datahyena%2Fsignals.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.datahyena%2Fsignals.svg :target: https://glimind.com/server/mcp-registry%2Fcom.datahyena%2Fsignals?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:797525996124f6b7…, first seen 2026-10-23, included at leaf 51921 of 75,348. Version history · verify what your client received.
Compare: most reliable data servers · most reliable knowledge 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-26 20:40 UTC, the Datahyena Signals MCP server is up with a Glimind reliability score of 87/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 8 outages in 90 days, with a median recovery of 7 minutes.
Datahyena Signals MCP server advertises 13 tools, including acquisitions, add_to_watchlist, companies, company_hiring, company_timeline.
Point your MCP client at this streamable-http endpoint: https://api.datahyena.com/mcp
Glimind scanned all 13 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.