Skip to content

RWA Data MCP Server

io.github.daveabear/rwa-data-mcpdaveabearstreamable-httpv1.1.0Scanned

Pay-per-call crypto data for agents: metrics, claims, custom briefs. USDC via x402.

9 tools: 2 change things and 7 only read.

Tools: 0 delete, 0 irreversible, 2 write, 7 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the RWA Data MCP Server can do

The RWA Data MCP Server is published by the GitHub account daveabear. It has 9 tools. It can create or change data (2 tools: verify_claim and request_brief), but cannot delete data. 7 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 20, 2026, version 1.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

9 tools

Changes things 2Claude Code: ask
  • request_briefOrder a custom research brief on your topic ($1.50 USDC per brief).1 finding

    Why it is in this group

    • The name "request_brief" says "request": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "request_brief" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true}; The name "request_brief" says "request": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Order a custom research brief on your topic ($1.50 USDC per brief). Topics must be in our lanes: stablecoins, RWA/tokenization, DeFi, the AI agent economy, crypto markets. The brief is researched on demand (up to ~60 min); use check_brief_status to poll for it (polling is free). First call (no payment_signature) returns the payment challenge; pay the exact USDC on Solana, then call again with payment_signature.

    Annotations the server declares

    • readOnlyHint: true
  • verify_claimVerify a factual crypto-markets claim against a sourced, dated claims cache: confirmed / refuted / unverifiable, with evidence and sources ($0.10 USDC per call).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Verify a factual crypto-markets claim against a sourced, dated claims cache: confirmed / refuted / unverifiable, with evidence and sources ($0.10 USDC per call). First call (no payment_signature) returns the payment challenge; pay the exact USDC on Solana, then call again with payment_signature.

    Annotations the server declares

    • readOnlyHint: true
Only reads 7Show 7 read-only tools
  • check_brief_statusCheck the status of a custom brief task (FREE — polling never costs).No findings

    Why it is in this group

    • The name "check_brief_status" says "status": a word for reading.
    Description, as the server wrote it
    Check the status of a custom brief task (FREE — polling never costs). Returns queued/working/done/failed; when done, includes the brief markdown and sources.

    Annotations the server declares

    • readOnlyHint: true
  • get_all_metricsEvery tracked metric in one call: stablecoin, RWA, DeFi, L2, prediction-market, and agent-economy metrics, each with source, date, and confidence ($0.01 USDC per call).No findings

    Why it is in this group

    • The name "get_all_metrics" says "get": a word for reading.
    Description, as the server wrote it
    Every tracked metric in one call: stablecoin, RWA, DeFi, L2, prediction-market, and agent-economy metrics, each with source, date, and confidence ($0.01 USDC per call). First call (no payment_signature) returns the payment challenge; pay the exact USDC on Solana, then call again with payment_signature.

    Annotations the server declares

    • readOnlyHint: true
  • get_briefStructured market brief: total + breakdown, insights, risks ($0.25 USDC per call).No findings

    Why it is in this group

    • The name "get_brief" says "get": a word for reading.
    Description, as the server wrote it
    Structured market brief: total + breakdown, insights, risks ($0.25 USDC per call). First call (no payment_signature) returns the payment challenge; pay the exact USDC on Solana, then call again with payment_signature.

    Annotations the server declares

    • readOnlyHint: true
  • get_metricGet one verified stablecoin/RWA market metric ($0.01 USDC per call).No findings

    Why it is in this group

    • The name "get_metric" says "get": a word for reading.
    Description, as the server wrote it
    Get one verified stablecoin/RWA market metric ($0.01 USDC per call). First call (no payment_signature) returns the payment challenge; pay the exact USDC on Solana, then call again with payment_signature.

    Annotations the server declares

    • readOnlyHint: true
  • get_monitor_pegsAll four tracked stablecoin pegs (usdt, usdc, usde, dai) in one call ($0.01 USDC per call).No findings

    Why it is in this group

    • The name "get_monitor_pegs" says "get": a word for reading.
    Description, as the server wrote it
    All four tracked stablecoin pegs (usdt, usdc, usde, dai) in one call ($0.01 USDC per call). First call (no payment_signature) returns the payment challenge; pay the exact USDC on Solana, then call again with payment_signature.

    Annotations the server declares

    • readOnlyHint: true
  • get_pegStablecoin peg status: live price and deviation in basis points from $1.00 ($0.01 USDC per call).No findings

    Why it is in this group

    • The name "get_peg" says "get": a word for reading.
    Description, as the server wrote it
    Stablecoin peg status: live price and deviation in basis points from $1.00 ($0.01 USDC per call). First call (no payment_signature) returns the payment challenge; pay the exact USDC on Solana, then call again with payment_signature.

    Annotations the server declares

    • readOnlyHint: true
  • get_pricePoint-in-time asset price with source proof ($0.01 USDC per call).No findings

    Why it is in this group

    • The name "get_price" says "get": a word for reading.
    Description, as the server wrote it
    Point-in-time asset price with source proof ($0.01 USDC per call). First call (no payment_signature) returns the payment challenge; pay the exact USDC on Solana, then call again with payment_signature.

    Annotations the server declares

    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:03 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://rwa-data-mcp.dave-a-bear.workers.dev/mcp: tools/list returned 9 tools to an anonymous client, including verify_claim (write), request_brief (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "request_brief" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true}; The name "request_brief" says "request": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http rwa-data https://rwa-data-mcp.dave-a-bear.workers.dev/mcp
claude mcp add --transport http rwa-data https://rwa-data-mcp.dave-a-bear.workers.dev/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__rwa-data__get_metric",
      "mcp__rwa-data__get_peg",
      "mcp__rwa-data__get_monitor_pegs",
      "mcp__rwa-data__get_all_metrics",
      "mcp__rwa-data__get_price",
      "mcp__rwa-data__get_brief",
      "mcp__rwa-data__check_brief_status"
    ],
    "ask": [
      "mcp__rwa-data__verify_claim",
      "mcp__rwa-data__request_brief"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as rwa-data. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.daveabear/rwa-data-mcp/verify?hash=32633c152561c795ec7f66c73370e7455c4f635773674f24f0bcec94f8de6470" | jq -e '.changed == false'

Pinned hash 32633c152561, from Nov 20, 2026, 20:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.daveabear/rwa-data-mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.daveabear/rwa-data-mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.daveabear/rwa-data-mcp.svg)](https://radar.anlyon.com/servers/io.github.daveabear/rwa-data-mcp)

Source: MCP Registry. Synced Oct 21, 2026, 18:31 UTC.

RWA Data MCP Server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the RWA Data MCP Server safe?

No scan can promise that. What its definitions show: 9 tools, 2 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the RWA Data MCP Server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the RWA Data MCP Server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the RWA Data MCP Server have?

9 tools: 2 write, 7 read. verify_claim, request_brief, get_metric, get_peg, get_monitor_pegs, get_all_metrics, get_price, get_brief and 1 more.

Does the RWA Data MCP Server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the RWA Data MCP Server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the RWA Data MCP Server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.