mcp-registry/org.crivum/crivum · v1
As of 2026-10-27 08:06 UTC, the Crivum 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.
Score academic and professional writing against published criteria with three reference models.
Point your MCP client at this streamable-http endpoint: https://crivum.org/mcp
4 of 4 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 →
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 →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Forg.crivum%2Fcrivum/fixes
{
"name": "get_criteria",
"description": "Return Crivum's public rubric by work type, the tier ladder, the thresholds, the minimum score for a citable record and what Crivum accepts and refuses, each with a version number. No API key required. Use before calling evaluate_text, or to show a user what a score decomposes into. Gatilho em português: \"quais são os critérios da Crivum\".",
"inputSchema": {
"type": "object",
"properties": {},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Read Crivum's public scoring criteria"
}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/org.crivum/crivum"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/org.crivum/crivum"}) over MCP.
evaluate_text ~363 tokensverify_record ~281 tokensscreen_text ~220 tokensget_criteria ~128 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%2Forg.crivum%2Fcrivum?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Forg.crivum%2Fcrivum?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Forg.crivum%2Fcrivum.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Forg.crivum%2Fcrivum.svg :target: https://glimind.com/server/mcp-registry%2Forg.crivum%2Fcrivum?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:b27744514f9febc8…, first seen 2026-10-17, included at leaf 3252 of 78,220. Version history · verify what your client received.
Compare: most reliable knowledge servers · most reliable productivity 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 08:06 UTC, the Crivum 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.
Crivum MCP server advertises 4 tools, including evaluate_text, get_criteria, screen_text, verify_record.
Point your MCP client at this streamable-http endpoint: https://crivum.org/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.