Tokenized Stocks & Agent Data (x402)
REMOTE · X402-ACCELEROMETER-FEED.FLY.DEV · SCANNED OCT 12
x402-paid data for agents: tokenized stocks on Base, Solana token verdicts, AI-progress readings
Available components
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the Tokenized Stocks & Agent Data (x402) MCP server?
Tokenized Stocks & Agent Data (x402) is a hosted endpoint at https://x402-accelerometer-feed.fly.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 · x402-accelerometer-feed.fly.dev
claude mcp add --transport http dev-fly-x402-accelerometer-feed-tokenized-stocks 'https://x402-accelerometer-feed.fly.dev/mcp'
{
"mcpServers": {
"dev-fly-x402-accelerometer-feed-tokenized-stocks": {
"url": "https://x402-accelerometer-feed.fly.dev/mcp"
}
}
} {
"servers": {
"dev-fly-x402-accelerometer-feed-tokenized-stocks": {
"type": "http",
"url": "https://x402-accelerometer-feed.fly.dev/mcp"
}
}
} [mcp_servers.dev-fly-x402-accelerometer-feed-tokenized-stocks] url = "https://x402-accelerometer-feed.fly.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-fly-x402-accelerometer-feed-tokenized-stocks": {
"type": "remote",
"url": "https://x402-accelerometer-feed.fly.dev/mcp",
"enabled": true
}
}
} openclaw mcp add dev-fly-x402-accelerometer-feed-tokenized-stocks --url 'https://x402-accelerometer-feed.fly.dev/mcp' --transport streamable-http
mcp_servers:
dev-fly-x402-accelerometer-feed-tokenized-stocks:
url: "https://x402-accelerometer-feed.fly.dev/mcp" {
"McpServers": {
"dev-fly-x402-accelerometer-feed-tokenized-stocks": {
"Transport": "http",
"Url": "https://x402-accelerometer-feed.fly.dev/mcp"
}
}
} assistant mcp add dev-fly-x402-accelerometer-feed-tokenized-stocks -t streamable-http -u 'https://x402-accelerometer-feed.fly.dev/mcp'
{
"mcpServers": {
"dev-fly-x402-accelerometer-feed-tokenized-stocks": {
"type": "http",
"url": "https://x402-accelerometer-feed.fly.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 12 Oct 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.73 → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 10 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 73. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 63. That category is still filling its 30-day observation window: 17 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.
- 5 Oct 26 +1
- HSTS header: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 12 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.57 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 4 Oct 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.50 → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 3 Oct 26 +1
- Injection markers: unverified → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 12 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.50 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 2 Oct 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: 0.43 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 30 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 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 12 Oct 2026 · Probed https://x402-accelerometer-feed.fly.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.fly.dev | CN=YE1,O=Let's Encrypt,C=US | 21 Aug 2026 | 19 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 688c4daf5300c51e0a5c1f6837a3a67a868 |
| SANs: *.fly.dev | ||||||
| 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 x402-accelerometer-feed.fly.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| fly.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://x402-accelerometer-feed.fly.dev/mcp | Unreachable | ||
| http (plaintext) | http://x402-accelerometer-feed.fly.dev/mcp | HTTPS enforced | 301 | https://x402-accelerometer-feed.fly.dev/mcp |
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 →
ai_progress_as_of ~165
Use this when you need AI progress as it stood on a past date: the reading of the same 129 series (benchmarks, compute, AGI prediction-market odds, model pricing, AI stocks, energy, space, robotics, research output) taken on YYYY-MM-DD. Dated ids are listed free at /. Same per-series shape as /ai-progress/latest, so you can diff dates yourself; /ai-progress/what-changed does the diff for you. Unknown id -> 404. Costs $0.005 (USDC on Base or Solana, x402). HTTP twin: https://x402-accelerometer-feed.fly.dev/ai-progress/as-of/{id}
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | reading date YYYY-MM-DD, from the free menu |
No output schema declared.
No examples provided.
ai_progress_latest ~154
Use this when you need the current state of AI progress in one call: the latest reading of 129 public series (frontier benchmark scores GPQA/HLE/ARC-AGI/METR, Epoch compute trends, AGI odds on Polymarket/Manifold/Kalshi, model pricing, AI stocks and crypto, energy, space, robotics, biomed, research output). One JSON row per series: latest and previous value with dates, % change, signal quality, source URL. Free 3-row sample at /preview. Costs $0.005 (USDC on Base or Solana, x402). HTTP twin: https://x402-accelerometer-feed.fly.dev/ai-progress/latest
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ai_progress_what_changed ~157
Use this when the question is what moved in AI progress between two dates: the acceleration between two readings of 129 series (benchmarks, compute, AGI odds, model pricing, AI stocks and crypto, energy, space, robotics, research output). Per series: from/to value and date, absolute and % change, and whether a new observation landed. Dates are YYYY-MM-DD ids from the free menu at /. Costs $0.01 (USDC on Base or Solana, x402). HTTP twin: https://x402-accelerometer-feed.fly.dev/ai-progress/what-changed/{from}/{to}
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | earlier reading id |
| to | string | yes | later reading id |
No output schema declared.
No examples provided.
boundary ~32
Free. Machine-readable limits per product: sources, freshness, cache, rate limits, failure modes and what is NOT verified.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
health ~19
Free. Liveness and the settled-call counters per route.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
menu ~33
Free. Every product this server sells, with price, chains, when to use each, and the HTTP URL. Start here.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
receipt ~36
Free. Look up a signed delivery receipt by id (returned with every paid call) and its verification key.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
same_stock ~204
Use this when you need the same stock from every issuer on Base in one call: send a ticker (NVDA, AAPL, TSLA) and get, per issuer — ST0x (wtNVDA) and Coinbase tokenized stocks (NVDAc, B20) — the genuine contract verified against the issuer's own registry, live price, premium/discount vs the real share in bps, pool depth and 24h volume, the ST0x-vs-Coinbase spread, any direct cross-issuer pool, and every impostor token using the same symbol. xStocks flagged as not on Base. Costs $0.05 (USDC on Base or Solana, x402). HTTP twin: https://x402-accelerometer-feed.fly.dev/tokenized-equities/same-stock/{ticker}
| Name | Type | Req | Description |
|---|---|---|---|
| ticker | string | yes | stock ticker (NVDA), ST0x symbol (wtNVDA) or Coinbase symbol (NVDAc) |
No output schema declared.
No examples provided.
solana_token_verdict ~184
Use this when an agent or a human asks 'is this Solana token safe, a joke, or a rug?': send one mint address, get a graded verdict (BASED / MID / COOKED / RADIOACTIVE), a one-liner, a short roast, and the facts behind the grade: price, liquidity, 24h volume, FDV, pair age, holder count, top-10 concentration, mint and freeze authority, LP lock, rugcheck risk flags, launchpad. Grade is rule-based and reproducible from the facts. Entertainment, not trading advice. Costs $0.02 (USDC on Base or Solana, x402). HTTP twin: https://x402-accelerometer-feed.fly.dev/solana/token-verdict/{mint}
| Name | Type | Req | Description |
|---|---|---|---|
| mint | string | yes | Solana token mint address (base58) |
No output schema declared.
No examples provided.
st0x_premium ~202
Use this when the question is whether an ST0x tokenized stock on Base trades above or below the real share: send a ticker (NVDA, wtAAPL, FGI) and get the premium/discount in basis points from the deepest USDC pool (live) and the last Raindex fill vs the exchange quote, corrected for the ERC-4626 wrapper rate, with market session, age of every leg, pool depth, any cross-issuer pool (wtNVDA vs Coinbase NVDAc), and a one-sentence read. Unknown ticker -> 404, no charge. Costs $0.02 (USDC on Base or Solana, x402). HTTP twin: https://x402-accelerometer-feed.fly.dev/tokenized-equities/st0x/premium/{ticker}
| Name | Type | Req | Description |
|---|---|---|---|
| ticker | string | yes | stock ticker (NVDA), ST0x symbol (wtNVDA) or Coinbase symbol (NVDAc) |
No output schema declared.
No examples provided.
st0x_pulse ~144
Use this when you want to know what is actually trading in tokenized stocks on Base right now: the last 24 hours on ST0x's own DEX (Raindex) per token — USDC volume, trade count, last on-chain price and time — plus each token's issued vault supply and ERC-4626 wrapper rate, sorted by volume, with platform totals. Read straight from the public subgraphs and RPC; refreshed every 5 minutes. Costs $0.01 (USDC on Base or Solana, x402). HTTP twin: https://x402-accelerometer-feed.fly.dev/tokenized-equities/st0x/pulse
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
st0x_registry ~169
Use this when you need to resolve a stock ticker to its ST0x on-chain token, or check whether a contract is a genuine ST0x tokenized share: the complete issuer registry for all 54-56 names on each of four chains (Base, Ethereum, HyperEVM, Robinhood Chain) — wrapped (wtNVDA, ERC-4626) and unwrapped (tNVDA, ERC-20) addresses, the ERC-1155 receipt vault, ISIN, TradingView symbol, listed flag. Versioned from the issuer's own registry; refreshed hourly. Costs $0.001 (USDC on Base or Solana, x402). HTTP twin: https://x402-accelerometer-feed.fly.dev/tokenized-equities/st0x/registry
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the Tokenized Stocks & Agent Data (x402) MCP server?
Tokenized Stocks & Agent Data (x402) is an MCP server listed in the public MCP registry as dev.fly.x402-accelerometer-feed/tokenized-stocks-agent-data. x402-paid data for agents: tokenized stocks on Base, Solana token verdicts, AI-progress readings. This page covers its hosted endpoint (https://x402-accelerometer-feed.fly.dev/mcp).
Is the Tokenized Stocks & Agent Data (x402) MCP server safe to use?
Tokenized Stocks & Agent Data (x402) scores 74 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 Tokenized Stocks & Agent Data (x402) MCP server expose?
Tokenized Stocks & Agent Data (x402) exposes 12 tools: menu, boundary, health, receipt, same_stock, and 7 more. Their descriptions and schemas cost roughly 1,499 tokens of context every time the server is loaded.
Does the Tokenized Stocks & Agent Data (x402) MCP server require authentication?
Its publisher declares no required credentials for Tokenized Stocks & Agent Data (x402). We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Tokenized Stocks & Agent Data (x402) MCP server still maintained?
Tokenized Stocks & Agent Data (x402) is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 10 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.