RWA Data MCP Server
REMOTE · RWA-DATA-MCP.DAVE-A-BEAR.WORKERS.DEV
Pay-per-call crypto data for agents: metrics, claims, custom briefs. USDC via x402.
Available components
Last scanned (10 hours ago)
Scores higher than 84% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Crypto and Web3
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1204 tokens (~133/item across 9 items; 9 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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
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.
- 4 Nov 26 0
- Stability: 0.97 → pass security
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 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.
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 5 Nov 2026 · Probed https://rwa-data-mcp.dave-a-bear.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=dave-a-bear.workers.dev | CN=YE2,O=Let's Encrypt,C=US | 4 Oct 2026 | 2 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5eb36fd30ffcc6462337e73c6d858c0e26f |
| SANs: *.dave-a-bear.workers.dev, dave-a-bear.workers.dev | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 rwa-data-mcp.dave-a-bear.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | 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://rwa-data-mcp.dave-a-bear.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://rwa-data-mcp.dave-a-bear.workers.dev/mcp | Inconclusive | 405 |
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 →
check_brief_status ~70
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.
| Name | Type | Req | Description |
|---|---|---|---|
| task_id | string | yes | The task_id returned by request_brief, e.g. task_abc123def456 |
No output schema declared.
No examples provided.
get_all_metrics ~137
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.
| Name | Type | Req | Description |
|---|---|---|---|
| payment_signature | string | – | Optional. Omit on the first call to receive the payment challenge. After sending the exact USDC amount on Solana mainnet to the pay_to wallet, call again with this set to the Solana transaction signa… |
No output schema declared.
No examples provided.
get_brief ~122
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.
| Name | Type | Req | Description |
|---|---|---|---|
| payment_signature | string | – | Optional. Omit on the first call to receive the payment challenge. After sending the exact USDC amount on Solana mainnet to the pay_to wallet, call again with this set to the Solana transaction signa… |
| topic | string | yes | Which brief to fetch |
No output schema declared.
No examples provided.
get_metric ~142
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Metric name, e.g. stablecoin_market_cap, rwa_total_value, agent_x402_volume_usd, top_yield_opportunities |
| payment_signature | string | – | Optional. Omit on the first call to receive the payment challenge. After sending the exact USDC amount on Solana mainnet to the pay_to wallet, call again with this set to the Solana transaction signa… |
No output schema declared.
No examples provided.
get_monitor_pegs ~123
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.
| Name | Type | Req | Description |
|---|---|---|---|
| payment_signature | string | – | Optional. Omit on the first call to receive the payment challenge. After sending the exact USDC amount on Solana mainnet to the pay_to wallet, call again with this set to the Solana transaction signa… |
No output schema declared.
No examples provided.
get_peg ~137
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.
| Name | Type | Req | Description |
|---|---|---|---|
| payment_signature | string | – | Optional. Omit on the first call to receive the payment challenge. After sending the exact USDC amount on Solana mainnet to the pay_to wallet, call again with this set to the Solana transaction signa… |
| symbol | string | yes | One of: usdt, usdc, usde, dai |
No output schema declared.
No examples provided.
get_price ~129
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Asset id, e.g. bitcoin, ethereum, solana, chainlink |
| payment_signature | string | – | Optional. Omit on the first call to receive the payment challenge. After sending the exact USDC amount on Solana mainnet to the pay_to wallet, call again with this set to the Solana transaction signa… |
No output schema declared.
No examples provided.
request_brief ~188
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.
| Name | Type | Req | Description |
|---|---|---|---|
| payment_signature | string | – | Optional. Omit on the first call to receive the payment challenge. After sending the exact USDC amount on Solana mainnet to the pay_to wallet, call again with this set to the Solana transaction signa… |
| topic | string | yes | Research topic, 10-200 characters, e.g. 'USDe depeg risk factors' |
No output schema declared.
No examples provided.
verify_claim ~156
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.
| Name | Type | Req | Description |
|---|---|---|---|
| claim | string | yes | The factual claim to verify, e.g. 'USDC market cap exceeded $70B in October 2026' |
| payment_signature | string | – | Optional. Omit on the first call to receive the payment challenge. After sending the exact USDC amount on Solana mainnet to the pay_to wallet, call again with this set to the Solana transaction signa… |
No output schema declared.
No examples provided.
How do I install the RWA Data MCP Server server?
RWA Data MCP Server is a hosted endpoint at https://rwa-data-mcp.dave-a-bear.workers.dev/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 · rwa-data-mcp.dave-a-bear.workers.dev
claude mcp add --transport http daveabear-rwa-data-mcp 'https://rwa-data-mcp.dave-a-bear.workers.dev/mcp'
What is the RWA Data MCP Server server?
RWA Data MCP Server is listed in the public MCP registry as io.github.daveabear/rwa-data-mcp. Pay-per-call crypto data for agents: metrics, claims, custom briefs. USDC via x402. This page covers its hosted endpoint (https://rwa-data-mcp.dave-a-bear.workers.dev/mcp).
Is the RWA Data MCP Server server safe to use?
RWA Data MCP Server scores 81 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 RWA Data MCP Server server expose?
RWA Data MCP Server exposes 9 tools: get_metric, get_peg, get_monitor_pegs, get_all_metrics, get_price, and 4 more. Their descriptions and schemas cost roughly 1,204 tokens of context every time the server is loaded.
Does the RWA Data MCP Server server require authentication?
No. We connected to RWA Data MCP Server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the RWA Data MCP Server server still maintained?
RWA Data MCP Server 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.