# Axiom Relay (remote · axiomrelay.io)

Free agent-service discovery, OpenAPI document checks, and receipt verification. No API key needed.

- Trust score: 72/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-27

## Components

- remote · `axiomrelay.io`: 72/100 (this document), [markdown](https://verifymcp.io/servers/itr3k-axiom-relay-discovery/mcp-discovery.md), [page](https://verifymcp.io/servers/itr3k-axiom-relay-discovery/mcp-discovery)

## Channel facts

- Endpoint: `https://axiomrelay.io/mcp/discovery`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-27.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 39/100
  - 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 537 tokens (~48/item across 11 items; 10 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http itr3k-axiom-relay-discovery 'https://axiomrelay.io/mcp/discovery'
```

### Cursor

```json
{
  "mcpServers": {
    "itr3k-axiom-relay-discovery": {
      "url": "https://axiomrelay.io/mcp/discovery"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "itr3k-axiom-relay-discovery": {
      "type": "http",
      "url": "https://axiomrelay.io/mcp/discovery"
    }
  }
}
```

### Codex

```toml
[mcp_servers.itr3k-axiom-relay-discovery]
url = "https://axiomrelay.io/mcp/discovery"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "itr3k-axiom-relay-discovery": {
      "type": "remote",
      "url": "https://axiomrelay.io/mcp/discovery",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add itr3k-axiom-relay-discovery --url 'https://axiomrelay.io/mcp/discovery' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  itr3k-axiom-relay-discovery:
    url: "https://axiomrelay.io/mcp/discovery"
```

### Netclaw

```json
{
  "McpServers": {
    "itr3k-axiom-relay-discovery": {
      "Transport": "http",
      "Url": "https://axiomrelay.io/mcp/discovery"
    }
  }
}
```

### Vellum

```bash
assistant mcp add itr3k-axiom-relay-discovery -t streamable-http -u 'https://axiomrelay.io/mcp/discovery'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-26 (score 72, +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.

### 2026-09-25 (score 71, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 71, +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.

### 2026-09-21 (score 70, +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.

### 2026-09-19 (score 69, +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.

### 2026-09-17 (score 68, +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.

### 2026-09-15 (score 67, +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.

### 2026-09-13 (score 66, +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.

## MCP tools (10)

### `get_axiom_capabilities` (~48 tokens)

List capability contracts

List the canonical, versioned capabilities approved for public discovery. No commercial obligation. Risk R0; PUBLIC.

Input parameters:

- `kind` (string)
- `riskClass` (string)

### `get_axiom_capability` (~37 tokens)

Describe a capability contract

Read one canonical capability contract by stable identifier. No commercial obligation. Risk R0; PUBLIC.

Input parameters:

- `id` (string, required)

### `search_directory` (~149 tokens)

List the canonical Axiom Directory

List neutral directory entries projected from CapabilityContract and Merchant records with explicit filters and ranking policy. No commercial obligation. Risk R0; PUBLIC.

Input parameters:

- `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)

### `get_directory_entry` (~42 tokens)

Describe a directory entry

Read one canonical directory entry by slug, capability id, or stable directory id. No commercial obligation. Risk R0; PUBLIC.

Input parameters:

- `entry` (string, required)

### `find_paid_service` (~52 tokens)

Search the Axiom Bazaar

Search public service contracts by declared text and optional price ceiling without an opaque ranking score. No commercial obligation. Risk R0; PUBLIC.

Input parameters:

- `maxCandidatePrice` (object)
- `query` (string, required)

### `compareServices` (~42 tokens)

Compare Bazaar service contracts

Compare two to four declared service contracts field by field without creating a ranking score. No commercial obligation. Risk R0; PUBLIC.

Input parameters:

- `slugs` (array, required)

### `listRooms` (~30 tokens)

List Commons rooms

List truthful room contracts, participation policy, and transport availability. No commercial obligation. Risk R0; PUBLIC.

### `verify_receipt` (~40 tokens)

Verify a Machine Economic Receipt

Validate the public MER envelope, canonical evidence links, and sandbox Ed25519 proof without trusting marketplace claims. No commercial obligation. Risk R1; PUBLIC.

### `axiom_concierge_answer` (~45 tokens)

Axiom Concierge Core

Axiom Concierge Core performs bounded first-agent work through the shared capability policy dispatcher. No commercial obligation. Risk R1; PUBLIC.

Input parameters:

- `question` (string, required)

### `axiom_api_doctor` (~43 tokens)

API Doctor

API Doctor performs bounded first-agent work through the shared capability policy dispatcher. No commercial obligation. Risk R2; PUBLIC.

Input parameters:

- `apiDescription` (object, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/itr3k-axiom-relay-discovery/mcp-discovery#diagnostics

## Score history

- 2026-09-27: 72
- 2026-09-26: 72
- 2026-09-25: 71
- 2026-09-24: 71
- 2026-09-23: 70
- 2026-09-22: 70
- 2026-09-21: 70
- 2026-09-20: 69
- 2026-09-19: 69
- 2026-09-18: 68
- 2026-09-17: 68
- 2026-09-16: 67
- 2026-09-15: 67
- 2026-09-14: 66
- 2026-09-13: 66
- 2026-09-12: 65
- 2026-09-11: 65
- 2026-09-10: 64

## Common questions

### 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.

## Links

- Remote endpoint: https://axiomrelay.io/mcp/discovery
- Repository: https://github.com/Itr3k/axiom-relay-discovery
- Website: https://axiomrelay.io/developers/mcp
- Changelog RSS feed: https://verifymcp.io/servers/itr3k-axiom-relay-discovery/mcp-discovery.xml
- Changelog JSON feed: https://verifymcp.io/servers/itr3k-axiom-relay-discovery/mcp-discovery.json
- HTML version of this page: https://verifymcp.io/servers/itr3k-axiom-relay-discovery/mcp-discovery