ai.radixia/blog
REMOTE · MCP.RADIXIA.AI
Search and read the Radixia blog (enterprise AI, cloud, open source) via MCP.
Available components
Last scanned (16 hours ago)
Scores higher than 71% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Search and Retrieval
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security54
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 480 tokens (~60/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (11)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (2)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- 9 Nov 26 0
- Stability: 0.97 → pass security
- 8 Nov 26 0
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 4 Sept 26 0
- Stability: fail → pass ▲ security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://mcp.radixia.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=radixia.ai | CN=WE1,O=Google Trust Services,C=US | 6 Nov 2026 | 4 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 45e3d3c4b3dec2c10e1664b91bc4e63c |
| SANs: radixia.ai, mcp.radixia.ai, *.mcp.radixia.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.radixia.ai. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | DS published | 1814 | 8 | Verified |
| radixia.ai. | DS published | 2371 | 13 | Verified |
| mcp.radixia.ai. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.radixia.ai/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.radixia.ai/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
about_radixia ~31
Who is Radixia? Company profile: the four capabilities, leadership, Labs, ecosystem and contacts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_conference_agenda ~55
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.
| Name | Type | Req | Description |
|---|---|---|---|
| day | string | – | Conference day to filter |
No output schema declared.
No examples provided.
get_conference_session ~74
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.
| Name | Type | Req | Description |
|---|---|---|---|
| title | string | yes | Session title or a distinctive part of it, e.g. 'Opening Keynote' or 'TOP500' |
No output schema declared.
No examples provided.
get_post ~54
Read the full text of a Radixia blog post by its slug (get the slug from list_posts or search_posts).
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Post slug, e.g. 'there-is-no-magic-in-ai' |
No output schema declared.
No examples provided.
list_posts ~80
List the most recent posts on the Radixia blog (AI, serverless, open source, cloud). Returns title, slug, date, tags and excerpt for each.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | How many posts to return |
| tag | string | – | Filter by tag slug, e.g. 'ai', 'serverless', 'e-commerce' |
No output schema declared.
No examples provided.
list_tags ~24
List the topic tags used on the Radixia blog, with post counts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_conference_transcripts ~90
Full-text search across 147 auto-generated session transcripts from the technical conferences Radixia attends: keynotes, panels, vendor talks, research papers. Returns matching passages with session title, day/time/hall and recording timestamp. Quoted phrases must match exactly.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max passages to return |
| query | string | yes | Search terms; wrap exact phrases in double quotes |
No output schema declared.
No examples provided.
search_posts ~72
Full-text search across all Radixia blog posts (title, excerpt and body). Use this to find what Radixia has written about a topic, e.g. 'MCP', 'Bedrock', 'event driven'.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results |
| query | string | yes | Search terms |
No output schema declared.
No examples provided.
How do I install the ai.radixia/blog MCP server?
ai.radixia/blog is a hosted endpoint at https://mcp.radixia.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.radixia.ai
claude mcp add --transport http ai-radixia-blog 'https://mcp.radixia.ai/mcp'
What is the ai.radixia/blog MCP server?
ai.radixia/blog is an MCP server listed in the public MCP registry as ai.radixia/blog. Search and read the Radixia blog (enterprise AI, cloud, open source) via MCP. This page covers its hosted endpoint (https://mcp.radixia.ai/mcp).
Is the ai.radixia/blog MCP server safe to use?
ai.radixia/blog scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the ai.radixia/blog MCP server expose?
ai.radixia/blog exposes 8 tools: list_posts, search_posts, get_post, list_tags, search_conference_transcripts, and 3 more. Their descriptions and schemas cost roughly 480 tokens of context every time the server is loaded.
Does the ai.radixia/blog MCP server require authentication?
No. We connected to ai.radixia/blog without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ai.radixia/blog MCP server still maintained?
ai.radixia/blog is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the ai.radixia/blog MCP server?
VerifyMCP ran 11 checks on ai.radixia/blog, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about ai.radixia/blog: Authorization and HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.