mcp-registry/com.recognitium/recognitium · v1.0.0
As of 2026-10-22 18:22 UTC, the Recognitium MCP server is up (it requires sign-in) with a Glimind reliability score of 80/100 (grade B). Over the last 30 days it answered 99.1% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 361.6 hours.
A memory your AI can prove and the market of the present tense. SHA-256, verifiable offline.
Claude Code
claude mcp add --transport http recognitium-mcp-server https://api.recognitium.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"recognitium-mcp-server": {
"type": "http",
"url": "https://api.recognitium.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
11 of 11 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
11 parameter(s) across 6 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. 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 →
Requires authentication (Bearer); tool definitions could not be read anonymously.
If discovery should be public, allow initialize + tools/list without credentials and gate only tools/call. Directories and routers can then list your tools.
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 6 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.recognitium%2Frecognitium/fixes
{
"name": "check_silence",
"description": "Proof-of-absence: was the rail demonstrably alive over [from_ns, to_ns], so absence of a receipt is evidence of absence of an event? Only a 'covered' verdict proves absence; 'not_covered' suspends the presumption. Public, free.",
"inputSchema": {
"type": "object",
"required": [
"from_ns",
"to_ns"
],
"properties": {
"to_ns": {
"type": "integer"
},
"from_ns": {
"type": "integer"
},
"max_silence_ns": {
"type": "integer"
}
}
},
"annotations": {
"readOnlyHint": true
}
}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.recognitium/recognitium"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.recognitium/recognitium"}) over MCP.
memory_seal ~224 tokensmemory_verify ~210 tokenslineage_trace ~167 tokensprove_anteriority ~136 tokensseal_hash ~124 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.recognitium%2Frecognitium?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.recognitium%2Frecognitium?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.recognitium%2Frecognitium.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.recognitium%2Frecognitium.svg :target: https://glimind.com/server/mcp-registry%2Fcom.recognitium%2Frecognitium?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:c3f8fb386a84654a…, first seen 2026-10-17, included at leaf 146 of 47,653. Version history · verify what your client received.
Compare: most reliable data servers · most reliable security 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-22 18:22 UTC, the Recognitium MCP server is up (it requires sign-in) with a Glimind reliability score of 80/100 (grade B). Over the last 30 days it answered 99.1% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 361.6 hours.
Recognitium MCP server advertises 11 tools, including agent_cv, chain_tip, check_silence, lineage_trace, memory_history.
Point your MCP client at this streamable-http endpoint: https://api.recognitium.com/mcp
Glimind scanned all 11 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.