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.

Stablecoin reserve attestations

REMOTE · AGENTWARES-STABLECOIN.VERCEL.APP · 2 COMPONENTS · SCANNED SEP 21

Stablecoin reserve attestations as JSON: reserves, composition, attestor, on-chain supply, ratio.

+3 this week 72 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 Security63
Transport & Reachability100
Schema Quality & AI Usability70
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 486 tokens (~243/item across 2 items; 2 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 Management47
  • Stability observed for 14 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 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 Stablecoin reserve attestations MCP server?

Stablecoin reserve attestations is a hosted endpoint at https://agentwares-stablecoin.vercel.app/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.

remote · agentwares-stablecoin.vercel.app

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

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.

  • 20 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.

  • 18 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.

  • 15 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.

  • 13 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.

  • 11 Sept 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 218 → 243 functional
    • Server version: 0.1.2 → 0.1.3 functional
  • 10 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.

  • 8 Sept 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “stablecoin_reserves” rewrote its description, which is the text the model reads security
    • Stability: unverified → 0.03 functional
    • Server version: 0.1.0 → 0.1.2 functional
  • 7 Sept 26 66

    First indexed and scored.

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 21 Sept 2026 · Probed https://agentwares-stablecoin.vercel.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.vercel.app CN=WR1,O=Google Trust Services,C=US 29 Aug 2026 27 Nov 2026 RSA 2048 SHA256-RSA f7911168ffa7d0f4135e24792e7a52a8
SANs: *.vercel.app
CN=WR1,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7fd9e2c2d2048a0474b627a26d0868a7
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of agentwares-stablecoin.vercel.app. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
vercel.app. 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=63072000; includeSubDomains; preload
x-content-type-options nosniff
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://agentwares-stablecoin.vercel.app/mcp Verified 200
http (plaintext) http://agentwares-stablecoin.vercel.app/mcp HTTPS enforced 308 https://agentwares-stablecoin.vercel.app/mcp
MCP tools · 2 exposed · ~305 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
stablecoin_list_issuers ~55

Free. Lists every issuer in the registry with symbol, issuer, attestation type, attestor, cadence, source_url and which months are parsed. Call it first to pick a symbol for stablecoin_reserves.

Input schema present but exposes no named parameters.

NameTypeReqDescription
countnumberyes
issuersarrayyes
noticestringyes
price_usd_per_reserves_callnumberyes

No examples provided.

stablecoin_reserves ~250

Latest parsed reserve attestation for one stablecoin issuer as JSON: as_of date, total reserves, composition by asset category, attestor, source_url, current on-chain supply (DefiLlama) and the reserve ratio. Use it when an agent needs machine-readable backing data instead of reading the issuer's PDF. Pass symbol (USDC, USDT, ...) or issuer; period=YYYY-MM selects an earlier month. Issuers without a third-party attestation return supply only with confidence 'none'. Paid: $0.02 per call; without credit you get a PAYMENT_REQUIRED result. Set sample=true for a free example response.

NameTypeReqDescription
issuerstringIssuer name or registry id when the symbol is unknown, e.g. "circle" or "paxos"
periodstringReport month as YYYY-MM. Default: the newest parsed month. See history_available.
samplebooleanSet true to return an example response at no charge (sample mode). Default false.
symbolstringToken symbol, case-insensitive: USDC, USDT, PYUSD, RLUSD, ... (see stablecoin_list_issuers)
NameTypeReqDescription
as_ofstring|nullyes
attestation_typestringyes
attestorstring|nullyes
backingstringyes
cadencestringyes
checksyes
compositionarrayyes
confidencestringyes
currencystringyes
history_availablearrayyes
issued_onstring|nullyes
issuerstringyes
namestringyes
noticestringyes
onchain_supplyyes
pegstringyes
periodstring|nullyes
report_urlstring|nullyes
reserve_rationumber|nullyes
reserve_ratio_vs_onchain_supplynumber|nullyes
samplebooleanyes
source_urlstringyes
sourcesarrayyes
symbolstringyes
tokens_in_circulation_reportednumber|nullyes
total_reserves_usdnumber|nullyes

No examples provided.

Common questions

What is the Stablecoin reserve attestations MCP server?

Stablecoin reserve attestations is an MCP server listed in the public MCP registry as io.github.agentwares/stablecoin-attestations. Stablecoin reserve attestations as JSON: reserves, composition, attestor, on-chain supply, ratio. This page covers its hosted endpoint (https://agentwares-stablecoin.vercel.app/mcp).

Is the Stablecoin reserve attestations MCP server safe to use?

Stablecoin reserve attestations 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 Stablecoin reserve attestations MCP server expose?

Stablecoin reserve attestations exposes 2 tools: stablecoin_reserves, stablecoin_list_issuers. Their descriptions and schemas cost roughly 305 tokens of context every time the server is loaded.

Does the Stablecoin reserve attestations MCP server require authentication?

No. We connected to Stablecoin reserve attestations without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Stablecoin reserve attestations MCP server still maintained?

Stablecoin reserve attestations is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.