_ registry / mcp http-sse · checked 3m ago

RedStone Price Oracle

https://redstone.finance

Registry code: 42a7415e786367c1

api record

Real-time and historical cryptocurrency price data from RedStone oracle infrastructure. 1,300+ assets, 110+ chains, no API key required. Powered by 50+ DEX and 30+ CEX sources with $4.943B Total Value Secured.

from a public catalogue that lists it, not from the operator

endpoint
https://mcp.redstone.finance/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 it live, free and safe measured by this hub
Is RedStone Price Oracle live?
Yes — it answered the hub's last check (checked 3m ago). It answered 100% of checks over the last 30 days.
Is RedStone Price Oracle free to use?
Yes — the hub reached it with no key and no payment.
What tools does RedStone Price Oracle have?
6 tools: start_agent_red, list_supported_tokens, get_detailed_price, get_price_change, get_price, get_prices.
Is RedStone Price Oracle 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.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
83ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 107 checks · signed record
  • unknown → live
_ what it is for
topic
crypto & onchain prices & market data
used for
  • get a crypto token price
  • get prices for several tokens
  • get 24 hour price change
  • get price breakdown by source
  • list supported tokens
takes → gives
text → data
tools
6 reads
_ usage and payments 30 days

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.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 6 tools
6 never probed 0 of 6 classified

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.

  • start_agent_red reads unknown never probed

    The entry point for using the RedStone Price Oracle. Call this when the user says "hello", "hi", "start", "redstone start", or asks what you can do. It introduces all tools and suggests a natural flow for market analysis.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • list_supported_tokens reads unknown 7h ago

    Returns the top 15 most popular cryptocurrency tokens currently supported by RedStone with active data sources. Proactively guides the user to check their prices or trends.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • get_detailed_price reads unknown 7h ago

    Get the latest USD price with a full breakdown of data from individual sources/exchanges. Proactively analyze if there is high variance between exchanges.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "symbol"
  ],
  "properties": {
    "symbol": {
      "type": "string",
      "description": "Cryptocurrency symbol"
    }
  }
}
    arguments 13 lines
  • get_price_change reads unknown 7h ago

    Calculate the percentage change for a token over the last 24 hours. Proactively suggests checking sources if the change is significant (>5%).

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "symbol"
  ],
  "properties": {
    "symbol": {
      "type": "string",
      "description": "Cryptocurrency symbol"
    }
  }
}
    arguments 13 lines
  • get_price reads unknown 5h ago

    Fetch the most recent USD price for a cryptocurrency (e.g., BTC, ETH, AR). Use this for simple price checks. The response includes a summary and suggests follow-up actions like detailed source breakdown or 24h trend analysis.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "symbol"
  ],
  "properties": {
    "symbol": {
      "type": "string",
      "description": "Target cryptocurrency symbol (e.g., ETH, BTC, LINK)"
    }
  }
}
    arguments 13 lines
  • get_prices reads unknown 5h ago

    Fetch latest USD prices for a list of tokens. Proactively suggests analyzing changes for the tokens with the highest volatility.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "symbols"
  ],
  "properties": {
    "symbols": {
      "type": "string",
      "description": "Comma-separated list (e.g. \"ETH,BTC,LINK,AR\")"
    }
  }
}
    arguments 13 lines
_ try it through the hub, ceiling 0

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.

_ is this your agent? claim it: badge, payouts, history

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.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. 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.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 42a7415e786367c1.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/42a7415e786367c1/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/42a7415e786367c1/badge.svg)](https://brick.blue/agent/42a7415e786367c1?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.

_ how we know
card completeness
100%

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.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
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.