Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Rates by 402rates

REMOTE · API.402RATES.COM · SCANNED SEP 27

Source-backed treasury data, settlement costs. Free instrument records and history.

Available components

+4 this week 73 Trust /100
Trust breakdown (7 categories)

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 Security57
Transport & Reachability100
Schema Quality & AI Usability78
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1241 tokens (~112/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • 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 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 11 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
Install

How do I install the Rates by 402rates MCP server?

Rates by 402rates is a hosted endpoint at https://api.402rates.com/mcp/rates, 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 · api.402rates.com

# add to Claude Code
claude mcp add --transport http com-402rates-rates 'https://api.402rates.com/mcp/rates'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-402rates-rates": {
      "url": "https://api.402rates.com/mcp/rates"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-402rates-rates": {
      "type": "http",
      "url": "https://api.402rates.com/mcp/rates"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-402rates-rates]
url = "https://api.402rates.com/mcp/rates"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-402rates-rates": {
      "type": "remote",
      "url": "https://api.402rates.com/mcp/rates",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-402rates-rates --url 'https://api.402rates.com/mcp/rates' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-402rates-rates:
    url: "https://api.402rates.com/mcp/rates"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-402rates-rates": {
      "Transport": "http",
      "Url": "https://api.402rates.com/mcp/rates"
    }
  }
}
# add to Vellum
assistant mcp add com-402rates-rates -t streamable-http -u 'https://api.402rates.com/mcp/rates'
// mcp.json
{
  "mcpServers": {
    "com-402rates-rates": {
      "type": "http",
      "url": "https://api.402rates.com/mcp/rates"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 27 Sept 26 +1

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

  • 25 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 23 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 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.

  • 18 Sept 26 +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.

  • 16 Sept 26 +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.

  • 14 Sept 26 +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.

  • 13 Sept 26 0
    • Schema quality: 1002 → 1241 ▼ functional
    • Server version: 0.1.0 → 0.2.0 functional
    • New tool “compare_rwa_benchmark” functional
    • New tool “list_rwa_updates” functional
Diagnostics

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://api.402rates.com/mcp/rates

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.402rates.com CN=YE1,O=Let's Encrypt,C=US 25 Sept 2026 24 Dec 2026 ECDSA 256 ECDSA-SHA384 624a9e6d66478572bca38229ca0b69ba829
SANs: api.402rates.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.402rates.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
402rates.com. 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.402rates.com/mcp/rates Verified 200
http (plaintext) http://api.402rates.com/mcp/rates HTTPS enforced 308 https://api.402rates.com/mcp/rates
MCP tools · 11 exposed · ~1,241 tokens

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 →

Tool Tokens
cheapest_settlement_chain ~109

Returns only the single cheapest chain for a USDC transfer right now, its total transaction fee in USD, the scope of that figure and how long it stays valid. Free and deliberately minimal: no per-chain table, no runner-up, no fee components and no source provenance. The paid tool compare_settlement_costs returns the full comparison with every input disclosed.

NameTypeReqDescription
chainsstring–comma-separated subset of base, polygon, arbitrum, ethereum, xdc. Defaults to all five.

No output schema declared.

No examples provided.

compare_rwa_benchmark ~146

Free arithmetic comparison of a saved measured USD instrument response and caller-supplied US Treasury total-return index levels with identical dates. Simple actual/365; 28-32 days. Input provenance is not verified. Spot rates, unmatched windows, quoted yields and other currencies are not comparable. The spread does not establish fees or causality.

NameTypeReqDescription
benchmarkobject–kind us_treasury_total_return_index, currency USD, start_date/end_date, positive start_value/end_value, HTTPS source_url and retrieved_at date. Caller declarations only.
snapshotobject–Saved single-instrument response, schema_version 0.5.0, with a measured USD return.

No output schema declared.

No examples provided.

compare_rwa_snapshots ~137

Free comparison of two supplied 402rates Treasury snapshots: yield, issuer divergence, source identifiers, calculation windows and data availability. Reports numeric threshold crossings without assigning economic significance. No new data access, authentication of snapshots, historical reconstruction or automatic monitoring. Examples are synthetic.

NameTypeReqDescription
afterobject–Later saved response. Input origin is not independently authenticated.
beforeobject–Earlier saved yields, single instrument or complete instrument response; schema_version 0.5.0.
threshold_bpsnumber–Absolute change in issuer_vs_basis_bps to flag, default 5; zero flags only nonzero changes.

No output schema declared.

No examples provided.

compare_settlement_costs ~130

Measured USDC transfer costs on Base, Polygon, Arbitrum, Ethereum and XDC: simulated gas, current token prices, fresh chain heads and applicable rollup L1 fees. Inputs and block references accompany each figure. Cheapest first; unmeasurable chains are excluded, not estimated. Business/professional use only. Terms: https://402rates.com/data-terms/ Price: 0.01 USDC per call over x402.

NameTypeReqDescription
chainsstring–comma-separated subset of base, polygon, arbitrum, ethereum, xdc. Defaults to all five.

No output schema declared.

No examples provided.

get_manifest ~54

Free OpenAPI manifest for Rates by 402rates. Contains this product and shared service information only.

NameTypeReqDescription
base_urlstring–absolute origin to render into the manifest's servers block. Defaults to the configured public base URL.

No output schema declared.

No examples provided.

get_rwa_history ~191

Returns free normalized observations for one tracked instrument, one reconstructible recorder source and one inclusive date window. Every point carries value, date, source id, revision and source-time versus read-time dating. Omit source_id to list the instrument's audited sources. The five current-only issuer series return HISTORY_SOURCE_RESERVED with the data-use URL, never an empty gap. Shares the instrument view's three-ticker rolling-hour breadth limit.

NameTypeReqDescription
date_fromstring–inclusive first observation date in YYYY-MM-DD form; required with source_id
date_tostring–inclusive last observation date in YYYY-MM-DD form; required with source_id
source_idstring–one source id belonging to ticker. Omit it to list that instrument's sources without observations.
tickerstring–tracked instrument ticker, case-insensitive. Omit it to list tickers and audited history sources.

No output schema declared.

No examples provided.

get_rwa_instrument ~116

Returns the free frozen-contract state view for one tracked tokenized treasury: identity, Open Treasury Yield Basis result or explicit unavailable reason, issuer-term evidence cells, verified deployments and evidence dates. Three distinct tickers are free per caller in a rolling hour; repeats stay free, and the fourth returns BREADTH_LIMIT with the paid complete-snapshot path. An omitted ticker returns only the known ticker list.

NameTypeReqDescription
tickerstring–tracked instrument ticker, case-insensitive. Omit it to receive the complete known ticker list.

No output schema declared.

No examples provided.

get_rwa_instruments ~107

Complete evidence snapshot for 13 tokenized treasury funds: yield or gap, measured size, subscription/redemption minimums, fees, settlement, access conditions, chain conflicts, quotes, URLs and dates. Same records as the free instrument view. Internal use with attribution included; continuous access, change notices and customer-facing use are separate. Business/professional use only. Terms: https://402rates.com/data-terms/ Price: 5 USDC per call over x402.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_rwa_yields ~127

Realised 30-day yields for 13 tokenized treasury funds under the Open Treasury Yield Basis. Measured rows use NAV, price or verified passive-holder balances, with observations, sources and dates. Issuer figures and differences appear where available. Quoted and unavailable rows stay explicit; free coverage lists funds and gaps. Business/professional use only. Terms: https://402rates.com/data-terms/ Price: 0.03 USDC per call over x402.

NameTypeReqDescription
instrumentsstring–comma-separated instrument tickers or ids; omitted means all tracked instruments

No output schema declared.

No examples provided.

list_capabilities ~31

Free capability and MCP tool catalogue for Rates by 402rates. Contains this product and shared service information only.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_rwa_updates ~93

Free cursor-based change notices for Treasury yields, terms, source evidence and availability. Capture every fifteen minutes; 90-day retention. Notices contain field names and state digests. Full before/after records use the existing instrument access limits. No reconstruction before the first baseline.

NameTypeReqDescription
cursorstring–next_cursor from an earlier response; an expired cursor requires a fresh baseline.
limitnumber–limit

No output schema declared.

No examples provided.

Common questions

What is the Rates by 402rates MCP server?

Rates by 402rates is an MCP server listed in the public MCP registry as com.402rates/rates. Source-backed treasury data, settlement costs. Free instrument records and history. This page covers its hosted endpoint (https://api.402rates.com/mcp/rates).

Is the Rates by 402rates MCP server safe to use?

Rates by 402rates scores 73 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 Rates by 402rates MCP server expose?

Rates by 402rates exposes 11 tools: list_rwa_updates, compare_rwa_benchmark, compare_rwa_snapshots, list_capabilities, get_manifest, and 6 more. Their descriptions and schemas cost roughly 1,241 tokens of context every time the server is loaded.

Does the Rates by 402rates MCP server require authentication?

No. We connected to Rates by 402rates without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Rates by 402rates MCP server still maintained?

Rates by 402rates 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.