mcp-registry/ai.radixia/blog · v1.1.0
As of 2026-10-26 22:09 UTC, the Radixia Blog MCP server is degraded with a Glimind reliability score of 48/100 (grade D). Over the last 30 days it answered 90% of Glimind's liveness checks. It had 2620 outages in 90 days, with a median recovery of 5 minutes.
Search and read the Radixia blog (enterprise AI, cloud, open source) via MCP.
Point your MCP client at this streamable-http endpoint: https://mcp.radixia.ai/mcp
Reachable 90.0% of the time over the last 30 days; median recovery 5 min.
Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.
8 of 8 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 →
Handshake + tools/list takes ~10,901 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
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%2Fai.radixia%2Fblog/fixes
{
"name": "get_conference_agenda",
"description": "The program of the conference sessions currently indexed: session blocks with times, halls, types and speakers, plus the recorded research-paper talks. Optionally filter by day.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"day": {
"enum": [
"Tuesday",
"Wednesday",
"Thursday"
],
"type": "string",
"description": "Conference day to filter"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_conference_session",
"description": "Read the full auto-generated transcript of one conference session by (part of) its title. Use search_conference_transcripts or get_conference_agenda first to find session titles.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"title"
],
"properties": {
"title": {
"type": "string",
"minLength": 3,
"description": "Session title or a distinctive part of it, e.g. 'Opening Keynote' or 'TOP500'"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_post",
"description": "Read the full text of a Radixia blog post by its slug (get the slug from list_posts or search_posts).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"slug"
],
"properties": {
"slug": {
"type": "string",
"description": "Post slug, e.g. 'there-is-no-magic-in-ai'"
}
},
"additionalProperties": false
},
"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/ai.radixia/blog"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/ai.radixia/blog"}) over MCP.
search_conference_transcripts ~193 tokenssearch_posts ~144 tokensget_conference_session ~142 tokenslist_posts ~141 tokensget_conference_agenda ~129 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%2Fai.radixia%2Fblog?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fai.radixia%2Fblog?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.radixia%2Fblog.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.radixia%2Fblog.svg :target: https://glimind.com/server/mcp-registry%2Fai.radixia%2Fblog?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:132ce99f24cbdb14…, first seen 2026-10-20, included at leaf 32364 of 75,743. Version history · verify what your client received.
Compare: most reliable knowledge servers · most reliable retrieval servers · most reliable database servers · most reliable search 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 22:09 UTC, the Radixia Blog MCP server is degraded with a Glimind reliability score of 48/100 (grade D). Over the last 30 days it answered 90% of Glimind's liveness checks. It had 2620 outages in 90 days, with a median recovery of 5 minutes.
Radixia Blog MCP server advertises 11 tools, including about_radixia, get_conference_agenda, get_conference_session, get_isc2026_agenda, get_isc2026_session.
Point your MCP client at this streamable-http endpoint: https://mcp.radixia.ai/mcp
Glimind scanned all 8 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.