_ registry / mcp + a2a http-sse · checked 1h ago

FeedOracle Stablecoin Risk

https://feedoracle.io

Registry code: 440464d4dabe1e09

api record

XRPLOracle - 31 XRP Ledger tools: payments, DEX, AMM, hooks, NFTs, validators, DIDs.

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

endpoint
https://feedoracle.io/mcp/risk/sse
door code
b8a6ee8462c85974
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 FeedOracle Stablecoin Risk live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is FeedOracle Stablecoin Risk free to use?
Yes — the hub reached it with no key and no payment.
What tools does FeedOracle Stablecoin Risk have?
13 tools: cross_chain_data, supply_flow, custody_data, peg_status, holder_data, peg_history, redemption_data, compare, ….
Is FeedOracle Stablecoin Risk 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
99.3%

90 days 99.4%· all time 99.6%

latency
316ms

last good check

priced tools
0

of 13 tools

_ answered our checks, 90 days 972 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
crypto & onchain
used for
  • compare stablecoin risks
  • get stablecoin cross-chain data
  • check stablecoin peg status
  • get stablecoin redemption terms
  • list supported stablecoins
takes → gives
text → data
tools
13 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

_ what it can do 13 tools
4 open 9 never probed 4 of 13 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.

  • ping reads open 4h ago

    Server connectivity test. Returns engine version and status.

    mcp-tool

    {
  "type": "object",
  "title": "pingArguments",
  "properties": {}
}
    arguments 5 lines
  • leaderboard reads open 16h ago

    Stablecoin risk leaderboard. Ranked by risk score (lowest = safest). Args: limit: Number of results (default 10, max 20)

    mcp-tool

    {
  "type": "object",
  "title": "leaderboardArguments",
  "properties": {
    "limit": {
      "type": "integer",
      "title": "Limit",
      "default": 10
    }
  }
}
    arguments 11 lines
  • supported_tokens reads open 16h ago

    List all supported stablecoins with coverage info.

    mcp-tool

    {
  "type": "object",
  "title": "supported_tokensArguments",
  "properties": {}
}
    arguments 5 lines
  • methodology reads open 1h ago

    Explain scoring methodology. Signal weights, verdict thresholds, data sources.

    mcp-tool

    {
  "type": "object",
  "title": "methodologyArguments",
  "properties": {}
}
    arguments 5 lines
  • cross_chain_data reads unknown 4h ago

    Cross-chain distribution. Chain count, bridge exposure, primary chain.

    mcp-tool

    {
  "type": "object",
  "title": "cross_chain_dataArguments",
  "required": [
    "symbol"
  ],
  "properties": {
    "symbol": {
      "type": "string",
      "title": "Symbol"
    }
  }
}
    arguments 13 lines
  • supply_flow reads unknown 4h ago

    Mint/burn flow analysis. Shows 7d supply changes and direction.

    mcp-tool

    {
  "type": "object",
  "title": "supply_flowArguments",
  "required": [
    "symbol"
  ],
  "properties": {
    "symbol": {
      "type": "string",
      "title": "Symbol"
    }
  }
}
    arguments 13 lines
  • custody_data reads unknown 22h ago

    Custodian profile. Shows custodians, SIFI status, attestation freshness.

    mcp-tool

    {
  "type": "object",
  "title": "custody_dataArguments",
  "required": [
    "symbol"
  ],
  "properties": {
    "symbol": {
      "type": "string",
      "title": "Symbol"
    }
  }
}
    arguments 13 lines
  • peg_status reads unknown 16h ago

    Quick peg check for a stablecoin. Shows current price and deviation.

    mcp-tool

    {
  "type": "object",
  "title": "peg_statusArguments",
  "required": [
    "symbol"
  ],
  "properties": {
    "symbol": {
      "type": "string",
      "title": "Symbol"
    }
  }
}
    arguments 13 lines
  • holder_data reads unknown 22h ago

    Holder concentration metrics. Top holder %, HHI index, whale count.

    mcp-tool

    {
  "type": "object",
  "title": "holder_dataArguments",
  "required": [
    "symbol"
  ],
  "properties": {
    "symbol": {
      "type": "string",
      "title": "Symbol"
    }
  }
}
    arguments 13 lines
  • peg_history reads unknown 22h ago

    30-day peg history. Shows max deviation, depeg events, trend.

    mcp-tool

    {
  "type": "object",
  "title": "peg_historyArguments",
  "required": [
    "symbol"
  ],
  "properties": {
    "symbol": {
      "type": "string",
      "title": "Symbol"
    }
  }
}
    arguments 13 lines
  • redemption_data reads unknown 8h ago

    Redemption terms. Settlement time, minimums, fees, institutional restrictions.

    mcp-tool

    {
  "type": "object",
  "title": "redemption_dataArguments",
  "required": [
    "symbol"
  ],
  "properties": {
    "symbol": {
      "type": "string",
      "title": "Symbol"
    }
  }
}
    arguments 13 lines
  • compare reads unknown 8h ago

    Side-by-side comparison of up to 5 stablecoins. Args: symbols: Comma-separated string (e.g. USDC,USDT,DAI) or list of symbols use_case: Context (settlement, collateral, treasury, payment)

    mcp-tool

    {
  "type": "object",
  "title": "compareArguments",
  "required": [
    "symbols"
  ],
  "properties": {
    "symbols": {
      "type": "string",
      "title": "symbols"
    },
    "use_case": {
      "type": "string",
      "title": "Use Case",
      "default": "settlement"
    }
  }
}
    arguments 18 lines
  • risk_assessment reads unknown 8h ago

    Full 7-signal risk report for a stablecoin. Args: symbol: Token symbol (e.g. USDC, USDT, DAI) chain: Chain filter or aggregate (default: aggregate) use_case: Context for hint generation (settlement, collateral, treasury, payment) Returns: Complete risk assessment with score, verdict, signals, and operational hint.

    mcp-tool

    {
  "type": "object",
  "title": "risk_assessmentArguments",
  "required": [
    "symbol"
  ],
  "properties": {
    "chain": {
      "type": "string",
      "title": "Chain",
      "default": "aggregate"
    },
    "symbol": {
      "type": "string",
      "title": "Symbol"
    },
    "use_case": {
      "type": "string",
      "title": "Use Case",
      "default": "settlement"
    }
  }
}
    arguments 23 lines
_ try it over mcp 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 440464d4dabe1e09.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/440464d4dabe1e09/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/440464d4dabe1e09/badge.svg)](https://brick.blue/agent/440464d4dabe1e09?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 knowoff the mcp door
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.

_ also on feedoracle.io 1 entry

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.