_ registry / mcp http-sse · checked 2h ago

defi-signals

https://x402-defi-signals.onrender.com

Registry code: e356d7ffa248f280

api record

Paid market-data API for AI agents (x402 / USDC on Base): cross-venue perpetual funding rates with an arbitrage spread signal, outlier-cleaned DeFi yields, and a low-cost market snapshot.

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

endpoint
https://x402-defi-signals.onrender.com/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 defi-signals live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is defi-signals free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does defi-signals have?
5 tools: get_daily_signals, list_pricing, get_market_snapshot, get_top_yields, get_funding_rates.
Is defi-signals 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 99.4%· all time 97.3%

latency
515ms

last good check

priced tools
3

of 5 tools

_ answered our checks, 90 days 534 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • get perpetual funding rates across venues
  • find top defi yields
  • get a crypto market snapshot
  • get a daily market signal
takes → gives
text → data
tools
5 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address also stands behind 3 other origins: the chain figures are the gateway's, not this listing's alone. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
17

distinct

settlements
39

last 2026-11-06

received on chain
0.149 USDC

shared-payto

_ what it can do 5 tools
3 paid1 open 1 never probed 4 of 5 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.

  • get_market_snapshot reads 0.002 USDC paid 9h ago

    Paid ($0.002): BTC/ETH/SOL spot prices, 24h change, Crypto Fear & Greed index.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • get_top_yields reads 0.01 USDC paid 9h ago

    Paid ($0.01): top DeFi yields per chain from DefiLlama — TVL-filtered, outlier-cleaned, with apy_base_pct (base yield without reward tokens).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "chain": {
          "type": "string",
          "default": "Base",
          "description": "Chain name, e.g. Base, Ethereum, Arbitrum"
        },
        "limit": {
          "type": "number",
          "default": 10,
          "maximum": 25,
          "description": "Max number of pools"
        },
        "max_apy_pct": {
          "type": "number",
          "default": 300,
          "description": "Outlier cap: pools above this APY are excluded"
        },
        "min_tvl_usd": {
          "type": "number",
          "default": 1000000,
          "description": "Minimum pool TVL in USD"
        }
      }
    }
    arguments 27 lines
  • get_funding_rates reads 0.005 USDC paid 9h ago

    Paid ($0.005): cross-venue perpetual funding rates (OKX, Kraken Futures, dYdX) with per-venue annualized rates and spread_annualized_pp as a funding-arbitrage signal.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "symbol": {
          "type": "string",
          "default": "BTC",
          "description": "Token symbol, e.g. BTC, ETH, SOL"
        }
      }
    }
    arguments 11 lines
  • list_pricing reads open 6h ago

    Free: list all DeFi Signals tools with prices (USDC on Base, x402).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • get_daily_signals reads unknown never probed

    Paid ($0.05, PREMIUM): one-call daily signal — market regime (Fear & Greed + price action), Base yields with 1d/7d APY deltas from proprietary history, best cross-venue funding-arbitrage setup, ranked top_opportunities.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 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 e356d7ffa248f280.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/e356d7ffa248f280/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/e356d7ffa248f280/badge.svg)](https://brick.blue/agent/e356d7ffa248f280?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
90%

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.