# Mercury402: Treasury/FRED financial data over x402 (remote · mcp.mercury402.com)

Treasury/FRED financial data over x402: pay-per-call US yields, macro and forex in USDC on Base

- Trust score: 70/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.mercury402.com`: 70/100 (this document), [markdown](https://verifymcp.io/servers/dudman1-mercury402-mcp/mcp.md), [page](https://verifymcp.io/servers/dudman1-mercury402-mcp/mcp)
- npm · `mercury402-mcp`: 81/100, [markdown](https://verifymcp.io/servers/dudman1-mercury402-mcp/mercury402-mcp.md), [page](https://verifymcp.io/servers/dudman1-mercury402-mcp/mercury402-mcp)

## Channel facts

- Endpoint: `https://mcp.mercury402.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.4`

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

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 1 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 is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 79/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 303 tokens (~151/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 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 Mercury402: Treasury/FRED financial data over x402 MCP server?

Mercury402: Treasury/FRED financial data over x402 is a hosted endpoint at https://mcp.mercury402.com/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.

### Claude

```bash
claude mcp add --transport http dudman1-mercury402-mcp 'https://mcp.mercury402.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dudman1-mercury402-mcp": {
      "url": "https://mcp.mercury402.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dudman1-mercury402-mcp": {
      "type": "http",
      "url": "https://mcp.mercury402.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dudman1-mercury402-mcp]
url = "https://mcp.mercury402.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dudman1-mercury402-mcp": {
      "type": "remote",
      "url": "https://mcp.mercury402.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dudman1-mercury402-mcp --url 'https://mcp.mercury402.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dudman1-mercury402-mcp:
    url: "https://mcp.mercury402.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dudman1-mercury402-mcp": {
      "Transport": "http",
      "Url": "https://mcp.mercury402.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dudman1-mercury402-mcp -t streamable-http -u 'https://mcp.mercury402.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dudman1-mercury402-mcp": {
      "type": "http",
      "url": "https://mcp.mercury402.com/mcp"
    }
  }
}
```

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-11-05 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 65, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-26 (score 65)

First indexed and scored.

## MCP tools (2)

### `list_endpoints` (~82 tokens)

List Mercury402 endpoints

List Mercury402 financial data endpoints (78 total) with path, method, category, description, price in USD (paid per call in USDC on Base via x402) and accepted parameters. Free; makes no network calls.

Input parameters:

- `category` (string): Only return this category
- `search` (string): Case-insensitive substring match on path or description

### `get_endpoint_data` (~221 tokens)

Call a Mercury402 endpoint

Call a Mercury402 endpoint on the live API. This hosted endpoint is discovery-only: endpoints return HTTP 402 and this tool returns the price and x402 payment instructions instead of data. Pay with your own x402 client, or run mercury402-mcp locally (npx -y mercury402-mcp) with your own wallet. Use list_endpoints first to find paths and parameters. Path params can be inline ("/v1/fred/UNRATE") or passed in params ("/v1/fred/{series_id}" + {"series_id":"UNRATE"}). Other params go to the query string (GET) or JSON body (POST).

Input parameters:

- `params` (object): Path, query (GET) or body (POST) parameters
- `path` (string, required): Endpoint path, e.g. "/v1/treasury/yield-curve/daily-snapshot" or "/v1/fred/UNRATE"
- `pay` (boolean): Paid mode only: set false to just get the price quote without paying. Default true.

## Diagnostics

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

## Score history

- 2026-11-05: 70
- 2026-11-04: 69
- 2026-11-03: 69
- 2026-11-02: 68
- 2026-11-01: 68
- 2026-10-31: 67
- 2026-10-30: 67
- 2026-10-29: 66
- 2026-10-28: 66
- 2026-10-27: 65
- 2026-10-26: 65

## Common questions

### What is the Mercury402: Treasury/FRED financial data over x402 MCP server?

Mercury402: Treasury/FRED financial data over x402 is an MCP server listed in the public MCP registry as io.github.dudman1/mercury402-mcp. Treasury/FRED financial data over x402: pay-per-call US yields, macro and forex in USDC on Base. This page covers its hosted endpoint (https://mcp.mercury402.com/mcp).

### Is the Mercury402: Treasury/FRED financial data over x402 MCP server safe to use?

Mercury402: Treasury/FRED financial data over x402 scores 70 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 Mercury402: Treasury/FRED financial data over x402 MCP server expose?

Mercury402: Treasury/FRED financial data over x402 exposes 2 tools: list_endpoints, get_endpoint_data. Their descriptions and schemas cost roughly 303 tokens of context every time the server is loaded.

### Does the Mercury402: Treasury/FRED financial data over x402 MCP server require authentication?

No. We connected to Mercury402: Treasury/FRED financial data over x402 without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Mercury402: Treasury/FRED financial data over x402 MCP server still maintained?

Mercury402: Treasury/FRED financial data over x402 is still listed as active in the MCP registry. We last reached this channel on 5 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 Mercury402: Treasury/FRED financial data over x402 MCP server?

VerifyMCP ran 12 checks on Mercury402: Treasury/FRED financial data over x402, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Mercury402: Treasury/FRED financial data over x402: Authorization. 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.

## Links

- Remote endpoint: https://mcp.mercury402.com/mcp
- Repository: https://github.com/dudman1/mercury402
- Website: https://mercury402.com/
- Changelog RSS feed: https://verifymcp.io/servers/dudman1-mercury402-mcp/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/dudman1-mercury402-mcp/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/dudman1-mercury402-mcp/mcp.json
- HTML version of this page: https://verifymcp.io/servers/dudman1-mercury402-mcp/mcp