onchain-stock-data
Registry code: 55e54982df76eacc
Pay-per-request onchain data for tokenized US equities (xStocks on Solana): DEX liquidity vs underlying, holder concentration, IPO calendar, plus a weekly Claude equity portfolio with auto-scored, evidence-linked catalyst verdicts. No API keys.
from a public catalogue that lists it, not from the operator
- endpoint
- https://osd-coral.vercel.app/api/mcp
- protocol
- http-sse ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is onchain-stock-data live?
- Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
- Is onchain-stock-data free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does onchain-stock-data have?
- 4 tools: signal_get, scoreboard_get, portfolio_get, catalysts_list.
- Is onchain-stock-data safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.3%· all time 99.3%
last good check
of 4 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- used for
- get dated catalysts for tokenized equities
- get ai-selected equity portfolio
- get directional signals for a ticker
- get catalyst scoreboard
- takes → gives
- data → data
- tools
- 4 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
scoreboard_get reads open 2h ago
Free scoreboard: hit/partial/miss tally of the Physical-AI dated catalysts, overall and per article.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": {} }arguments 5 linesportfolio_get reads open 2h ago
Current Claude-selected equity portfolio (weights, thesis, catalyst target dates) for the US or JP book.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "market": { "enum": [ "us", "jp" ], "type": "string", "default": "us" } } }arguments 14 linescatalysts_list reads open 2h ago
Dated numeric catalysts sorted by target_date (ascending). Filter by date range, ticker, or theme (series).
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "to": { "type": "string", "description": "YYYY-MM-DD upper bound on target_date" }, "from": { "type": "string", "description": "YYYY-MM-DD lower bound on target_date" }, "limit": { "type": "integer", "default": 20, "maximum": 100, "minimum": 1 }, "theme": { "type": "string", "description": "series label, e.g. physical-ai" }, "ticker": { "type": "string" } } }arguments 27 linessignal_get reads unknown never probed
Pre-generated directional signals for a ticker or theme. This is the resource with a paid x402 testnet twin (see `payment`); the values here are read-only committed data.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "theme": { "type": "string", "description": "scope label, e.g. AI-infra, JP-rates" }, "ticker": { "type": "string" } } }arguments 13 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id55e54982df76eacc.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/55e54982df76eacc/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/55e54982df76eacc?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.