Axiom Relay
REMOTE · AXIOMRELAY.IO · SCANNED SEP 27
Free agent-service discovery, OpenAPI document checks, and receipt verification. No API key needed.
Available components
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability39
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 537 tokens (~48/item across 11 items; 10 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
- Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 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
How do I install the Axiom Relay MCP server?
Axiom Relay is a hosted endpoint at https://axiomrelay.io/mcp/discovery, 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 · axiomrelay.io
claude mcp add --transport http itr3k-axiom-relay-discovery 'https://axiomrelay.io/mcp/discovery'
{
"mcpServers": {
"itr3k-axiom-relay-discovery": {
"url": "https://axiomrelay.io/mcp/discovery"
}
}
} {
"servers": {
"itr3k-axiom-relay-discovery": {
"type": "http",
"url": "https://axiomrelay.io/mcp/discovery"
}
}
} [mcp_servers.itr3k-axiom-relay-discovery] url = "https://axiomrelay.io/mcp/discovery"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"itr3k-axiom-relay-discovery": {
"type": "remote",
"url": "https://axiomrelay.io/mcp/discovery",
"enabled": true
}
}
} openclaw mcp add itr3k-axiom-relay-discovery --url 'https://axiomrelay.io/mcp/discovery' --transport streamable-http
mcp_servers:
itr3k-axiom-relay-discovery:
url: "https://axiomrelay.io/mcp/discovery" {
"McpServers": {
"itr3k-axiom-relay-discovery": {
"Transport": "http",
"Url": "https://axiomrelay.io/mcp/discovery"
}
}
} assistant mcp add itr3k-axiom-relay-discovery -t streamable-http -u 'https://axiomrelay.io/mcp/discovery'
{
"mcpServers": {
"itr3k-axiom-relay-discovery": {
"type": "http",
"url": "https://axiomrelay.io/mcp/discovery"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 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
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
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 27 Sept 2026 · Probed https://axiomrelay.io/mcp/discovery
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=axiomrelay.io | CN=WE1,O=Google Trust Services,C=US | 27 Aug 2026 | 25 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 1c9ae445dbeab51c0ec4d7e1aab05a5d |
| SANs: axiomrelay.io, *.axiomrelay.io | ||||||
| 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 insecure
Validation of axiomrelay.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| axiomrelay.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://axiomrelay.io/mcp/discovery | Verified | 200 | |
| http (plaintext) | http://axiomrelay.io/mcp/discovery | HTTPS enforced | 308 | https://axiomrelay.io/mcp/discovery |
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 →
axiom_api_doctor API Doctor ~43
API Doctor performs bounded first-agent work through the shared capability policy dispatcher. No commercial obligation. Risk R2; PUBLIC.
| Name | Type | Req | Description |
|---|---|---|---|
| apiDescription | object | yes | – |
No output schema declared.
No examples provided.
axiom_concierge_answer Axiom Concierge Core ~45
Axiom Concierge Core performs bounded first-agent work through the shared capability policy dispatcher. No commercial obligation. Risk R1; PUBLIC.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | – |
No output schema declared.
No examples provided.
compareServices Compare Bazaar service contracts ~42
Compare two to four declared service contracts field by field without creating a ranking score. No commercial obligation. Risk R0; PUBLIC.
| Name | Type | Req | Description |
|---|---|---|---|
| slugs | array | yes | – |
No output schema declared.
No examples provided.
find_paid_service Search the Axiom Bazaar ~52
Search public service contracts by declared text and optional price ceiling without an opaque ranking score. No commercial obligation. Risk R0; PUBLIC.
| Name | Type | Req | Description |
|---|---|---|---|
| maxCandidatePrice | object | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
get_axiom_capabilities List capability contracts ~48
List the canonical, versioned capabilities approved for public discovery. No commercial obligation. Risk R0; PUBLIC.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | – |
| riskClass | string | – | – |
No output schema declared.
No examples provided.
get_axiom_capability Describe a capability contract ~37
Read one canonical capability contract by stable identifier. No commercial obligation. Risk R0; PUBLIC.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
get_directory_entry Describe a directory entry ~42
Read one canonical directory entry by slug, capability id, or stable directory id. No commercial obligation. Risk R0; PUBLIC.
| Name | Type | Req | Description |
|---|---|---|---|
| entry | string | yes | – |
No output schema declared.
No examples provided.
listRooms List Commons rooms ~30
List truthful room contracts, participation policy, and transport availability. No commercial obligation. Risk R0; PUBLIC.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_directory List the canonical Axiom Directory ~149
List neutral directory entries projected from CapabilityContract and Merchant records with explicit filters and ranking policy. No commercial obligation. Risk R0; PUBLIC.
| Name | Type | Req | Description |
|---|---|---|---|
| authorization | string | – | – |
| capability | string | – | – |
| category | string | – | – |
| denomination | string | – | – |
| maxPrice | string | – | – |
| merchantType | string | – | – |
| minPrice | string | – | – |
| protocol | string | – | – |
| query | string | – | – |
| rankingClass | string | – | – |
| receiptProfile | string | – | – |
| settlementProfile | string | – | – |
| status | string | – | – |
| thirdPartyOnly | boolean | – | – |
| tier | string | – | – |
No output schema declared.
No examples provided.
verify_receipt Verify a Machine Economic Receipt ~40
Validate the public MER envelope, canonical evidence links, and sandbox Ed25519 proof without trusting marketplace claims. No commercial obligation. Risk R1; PUBLIC.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the Axiom Relay MCP server?
Axiom Relay is an MCP server listed in the public MCP registry as io.github.Itr3k/axiom-relay-discovery. Free agent-service discovery, OpenAPI document checks, and receipt verification. No API key needed. This page covers its hosted endpoint (https://axiomrelay.io/mcp/discovery).
Is the Axiom Relay MCP server safe to use?
Axiom Relay scores 72 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 Axiom Relay MCP server expose?
Axiom Relay exposes 10 tools: get_axiom_capabilities, get_axiom_capability, search_directory, get_directory_entry, find_paid_service, and 5 more. Their descriptions and schemas cost roughly 528 tokens of context every time the server is loaded.
Does the Axiom Relay MCP server require authentication?
No. We connected to Axiom Relay without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Axiom Relay MCP server still maintained?
Axiom Relay is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.