mcp-registry/io.github.openqfr-dev/openqfr · v0.1.0
As of 2026-10-27 03:10 UTC, the Openqfr Dev Openqfr MCP server is up with a Glimind reliability score of 85/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 131 outages in 90 days, with a median recovery of 8 minutes.
Search machine-readable quantitative strategy failure evidence before repeating failed research.
Point your MCP client at this streamable-http endpoint: https://openqfr.dev/mcp
3 of 3 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 →
5 parameter(s) across 2 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 →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 2 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.openqfr-dev%2Fopenqfr/fixes
{
"name": "qfr_get",
"description": "Retrieve one public QFR record by record ID.",
"inputSchema": {
"type": "object",
"required": [
"record_id"
],
"properties": {
"record_id": {
"type": "string",
"pattern": "^qfr:[0-9a-f]{24}$"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Get Quant Failure Record"
}{
"name": "qfr_search",
"description": "Search public quantitative strategy failure evidence before running a similar backtest.",
"inputSchema": {
"type": "object",
"properties": {
"limit": {
"type": "integer",
"maximum": 20,
"minimum": 1
},
"symbol": {
"type": "string",
"maxLength": 32
},
"generation": {
"type": "string",
"maxLength": 64
},
"failure_code": {
"type": "string",
"maxLength": 64
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Search Quant Failure Records"
}{
"name": "qfr_stats",
"description": "Return public record counts and the QFR schema version.",
"inputSchema": {
"type": "object",
"properties": {},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "OpenQFR Statistics"
}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.openqfr-dev/openqfr"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.openqfr-dev/openqfr"}) over MCP.
qfr_search ~109 tokensqfr_get ~67 tokensqfr_stats ~47 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.openqfr-dev%2Fopenqfr?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.openqfr-dev%2Fopenqfr?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.openqfr-dev%2Fopenqfr.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.openqfr-dev%2Fopenqfr.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.openqfr-dev%2Fopenqfr?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:c220e61324a740c6…, first seen 2026-10-17, included at leaf 6686 of 77,029. Version history · verify what your client received.
Compare: most reliable retrieval servers · most reliable search servers · most reliable data 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 03:10 UTC, the Openqfr Dev Openqfr MCP server is up with a Glimind reliability score of 85/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 131 outages in 90 days, with a median recovery of 8 minutes.
Openqfr Dev Openqfr MCP server advertises 3 tools, including qfr_get, qfr_search, qfr_stats.
Point your MCP client at this streamable-http endpoint: https://openqfr.dev/mcp
Glimind scanned all 3 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.