# 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.

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

## Components

- remote · `rwa-data-mcp.dave-a-bear.workers.dev`: 81/100 (this document), [markdown](https://verifymcp.io/servers/daveabear-rwa-data-mcp/rwa-data-mcp.md), [page](https://verifymcp.io/servers/daveabear-rwa-data-mcp/rwa-data-mcp)

## Channel facts

- Endpoint: `https://rwa-data-mcp.dave-a-bear.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

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. 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-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 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 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.

### Claude

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

### Cursor

```json
{
  "mcpServers": {
    "daveabear-rwa-data-mcp": {
      "url": "https://rwa-data-mcp.dave-a-bear.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "daveabear-rwa-data-mcp": {
      "type": "http",
      "url": "https://rwa-data-mcp.dave-a-bear.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.daveabear-rwa-data-mcp]
url = "https://rwa-data-mcp.dave-a-bear.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "daveabear-rwa-data-mcp": {
      "type": "remote",
      "url": "https://rwa-data-mcp.dave-a-bear.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add daveabear-rwa-data-mcp --url 'https://rwa-data-mcp.dave-a-bear.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  daveabear-rwa-data-mcp:
    url: "https://rwa-data-mcp.dave-a-bear.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "daveabear-rwa-data-mcp": {
      "Transport": "http",
      "Url": "https://rwa-data-mcp.dave-a-bear.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add daveabear-rwa-data-mcp -t streamable-http -u 'https://rwa-data-mcp.dave-a-bear.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "daveabear-rwa-data-mcp": {
      "type": "http",
      "url": "https://rwa-data-mcp.dave-a-bear.workers.dev/mcp"
    }
  }
}
```

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

## 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-04 (score 81, 0)

- [security] Stability: 0.97 → pass

### 2026-11-03 (score 81, +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.

### 2026-11-01 (score 80, +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.

### 2026-10-30 (score 79, +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.

### 2026-10-28 (score 78, +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.

### 2026-10-26 (score 77, +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.

### 2026-10-24 (score 76, +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.

### 2026-10-22 (score 75, +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.

## MCP tools (9)

### `get_metric` (~142 tokens)

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.

Input parameters:

- `name` (string, required): 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…

### `get_peg` (~137 tokens)

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.

Input parameters:

- `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, required): One of: usdt, usdc, usde, dai

### `get_monitor_pegs` (~123 tokens)

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.

Input parameters:

- `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…

### `get_all_metrics` (~137 tokens)

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.

Input parameters:

- `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…

### `get_price` (~129 tokens)

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.

Input parameters:

- `id` (string, required): 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…

### `verify_claim` (~156 tokens)

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.

Input parameters:

- `claim` (string, required): 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…

### `get_brief` (~122 tokens)

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.

Input parameters:

- `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, required): Which brief to fetch

### `request_brief` (~188 tokens)

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.

Input parameters:

- `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, required): Research topic, 10-200 characters, e.g. 'USDe depeg risk factors'

### `check_brief_status` (~70 tokens)

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.

Input parameters:

- `task_id` (string, required): The task_id returned by request_brief, e.g. task_abc123def456

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/daveabear-rwa-data-mcp/rwa-data-mcp#diagnostics

## Score history

- 2026-11-05: 81
- 2026-11-04: 81
- 2026-11-03: 81
- 2026-11-02: 80
- 2026-11-01: 80
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 78
- 2026-10-28: 78
- 2026-10-27: 77
- 2026-10-26: 77
- 2026-10-25: 76
- 2026-10-24: 76
- 2026-10-23: 75
- 2026-10-22: 75
- 2026-10-21: 74
- 2026-10-20: 74
- 2026-10-19: 74
- 2026-10-18: 73
- 2026-10-17: 73
- 2026-10-16: 72
- 2026-10-15: 72
- 2026-10-14: 71
- 2026-10-13: 71
- 2026-10-12: 70
- 2026-10-11: 70
- 2026-10-10: 69
- 2026-10-06: 68
- 2026-10-05: 67

## Common questions

### 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.

## Links

- Remote endpoint: https://rwa-data-mcp.dave-a-bear.workers.dev/mcp
- Changelog RSS feed: https://verifymcp.io/servers/daveabear-rwa-data-mcp/rwa-data-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/daveabear-rwa-data-mcp/rwa-data-mcp.json
- HTML version of this page: https://verifymcp.io/servers/daveabear-rwa-data-mcp/rwa-data-mcp