# Mercury402: Treasury/FRED financial data over x402 (npm · mercury402-mcp)

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

- Trust score: 81/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-06

## Components

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

## Channel facts

- Registry: `npm`
- Package: `mercury402-mcp`
- Version: `0.1.4`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-06.

- **Supply Chain Security**: 81/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 31 of 102 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to dudman1/mercury402).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 10 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 79/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 309 tokens (~154/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**: 37/100
  - Stability observed for 11 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 runs locally as an npm package, launched with npx -y mercury402-mcp. 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 dudman1-mercury402-mcp -- npx -y mercury402-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "dudman1-mercury402-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mercury402-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dudman1-mercury402-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mercury402-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add dudman1-mercury402-mcp -- npx -y mercury402-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dudman1-mercury402-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "mercury402-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dudman1-mercury402-mcp --command npx --arg -y --arg mercury402-mcp
```

### Hermes

```yaml
mcp_servers:
  dudman1-mercury402-mcp:
    command: "npx"
    args: ["-y", "mercury402-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "dudman1-mercury402-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "mercury402-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add dudman1-mercury402-mcp -t stdio -c npx -a -y mercury402-mcp
```

### Other

```json
{
  "mcpServers": {
    "dudman1-mercury402-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mercury402-mcp"
      ]
    }
  }
}
```

## 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 81, +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 80, +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 79, +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 78, +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 77, +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-26 (score 76)

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` (~227 tokens)

Call a Mercury402 endpoint

Call a Mercury402 endpoint on the live API. Without paid mode, endpoints return HTTP 402 and this tool returns the price and x402 payment instructions instead of data. With paid mode enabled (MERCURY402_PAYER_PRIVATE_KEY), it pays in USDC on Base (capped by MERCURY402_MAX_PRICE_USD) and returns the data. 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: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/dudman1-mercury402-mcp/mercury402-mcp#diagnostics

## Score history

- 2026-11-06: 81
- 2026-11-05: 81
- 2026-11-04: 80
- 2026-11-03: 80
- 2026-11-02: 79
- 2026-11-01: 79
- 2026-10-31: 78
- 2026-10-30: 78
- 2026-10-29: 77
- 2026-10-28: 77
- 2026-10-27: 76
- 2026-10-26: 76

## 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 npm package (mercury402-mcp).

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

Mercury402: Treasury/FRED financial data over x402 scores 81 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 6 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 309 tokens of context every time the server is loaded.

### 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 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

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

Mercury402: Treasury/FRED financial data over x402 declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Mercury402: Treasury/FRED financial data over x402 MCP server?

VerifyMCP ran 16 checks on Mercury402: Treasury/FRED financial data over x402, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/mercury402-mcp
- Socket report: https://socket.dev/npm/package/mercury402-mcp
- Repository: https://github.com/dudman1/mercury402
- Website: https://mercury402.com/
- Changelog RSS feed: https://verifymcp.io/servers/dudman1-mercury402-mcp/mercury402-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/dudman1-mercury402-mcp/mercury402-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/dudman1-mercury402-mcp/mercury402-mcp.json
- HTML version of this page: https://verifymcp.io/servers/dudman1-mercury402-mcp/mercury402-mcp