mcp-registry/io.github.rarasai/raras · v0.1.0
As of 2026-10-26 17:10 UTC, the Rarasai Raras MCP server is up with a Glimind reliability score of 96/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 2 minutes.
Disease Twin — Brazil's rare-disease knowledge graph (10,468) over MCP. Source-grounded, PT-BR.
Point your MCP client at this streamable-http endpoint: https://raras.org/api/mcp
39 parameter(s) across 18 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 →
10 of 20 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 →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 18 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.rarasai%2Fraras/fixes
{
"name": "find_active_trials",
"description": "Trials ativos com filtro Brazil.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"orphaCode"
],
"properties": {
"limit": {
"type": "integer",
"default": 15,
"maximum": 30,
"minimum": 1
},
"orphaCode": {
"type": "string",
"pattern": "^\\d+$"
},
"in_brazil_only": {
"type": "boolean",
"default": false
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Ensaios clínicos ativos"
}{
"name": "find_diseases_by_phenotypes",
"description": "Match por IDs HPO. Use para diagnóstico diferencial.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"hpo_ids"
],
"properties": {
"limit": {
"type": "integer",
"default": 10,
"maximum": 30,
"minimum": 1
},
"hpo_ids": {
"type": "array",
"items": {
"type": "string",
"pattern": "^HP:\\d+$"
},
"maxItems": 20,
"minItems": 1
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Buscar doenças por fenótipos"
}{
"name": "find_papers_for_disease",
"description": "Literatura relacionada a uma doença via embeddings (:SEMANTIC_MATCH, fallback vetorial).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"orphaCode"
],
"properties": {
"limit": {
"type": "integer",
"default": 10,
"maximum": 30,
"minimum": 1
},
"min_score": {
"type": "number",
"default": 0.8,
"maximum": 1,
"minimum": 0
},
"orphaCode": {
"type": "string",
"pattern": "^\\d+$"
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Papers de uma doença"
}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/io.github.rarasai/raras"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.rarasai/raras"}) over MCP.
explain_relation ~194 tokensget_literature_relations ~159 tokenssearch_phenotypes ~152 tokensanalyze_clinical_case ~135 tokensget_hypotheses ~135 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%2Fio.github.rarasai%2Fraras?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.rarasai%2Fraras?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.rarasai%2Fraras.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.rarasai%2Fraras.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.rarasai%2Fraras?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:5edadacc9c43a9de…, first seen 2026-10-17, included at leaf 15060 of 74,339. Version history · verify what your client received.
Compare: most reliable knowledge servers · most reliable search servers · most reliable data servers · most reliable ml servers · most reliable database 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 17:10 UTC, the Rarasai Raras MCP server is up with a Glimind reliability score of 96/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 2 minutes.
Rarasai Raras MCP server advertises 27 tools, including analyze_clinical_case, explain_relation, find_active_trials, find_diseases_by_phenotypes, find_papers_for_disease.
Point your MCP client at this streamable-http endpoint: https://raras.org/api/mcp
Glimind scanned all 20 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.