_ registry / mcp streamable-http · checked 1h ago

basis-protocol

https://basisprotocol.xyz

Registry code: da09ff31442268ea

api record

Verifiable risk intelligence for on-chain finance.

endpoint
https://basisprotocol.xyz/mcp
protocol
streamable-http ·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 basis-protocol live?
Yes — it answered the hub's last check (checked 1h ago). It answered 98% of checks over the last 30 days.
Is basis-protocol free to use?
Yes — the hub reached it with no key and no payment.
What tools does basis-protocol have?
7 tools: receipt_verify, score_history, basis_data, basis_answer, entity_read, get_methodology, get_stablecoin_scores.
Is basis-protocol 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
98%

90 days 98.3%· all time 98.3%

latency
186ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 348 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • get stablecoin integrity scores
  • monitor stablecoin pegs
  • check stablecoin transaction risk
  • get wallet risk profile
  • get defi yields and incidents
takes → gives
text → data
tools
3 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 7 tools
2 open 5 never probed 2 of 7 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_methodology reads open 24h ago

    The Basis methodology. mode="summary" (default): index list, versions, component counts. mode="full": the complete SII formula, weights and component specifications (large).

    mcp-tool

    {
      "type": "object",
      "title": "get_methodologyArguments",
      "properties": {
        "mode": {
          "type": "string",
          "title": "Mode",
          "default": "summary"
        }
      }
    }
    arguments 11 lines
  • get_stablecoin_scores reads open 24h ago

    Current SII scores (0-100) for scored stablecoins. Use before any decision involving stablecoins. Parameters: limit: max coins returned (default 25, max 500) fields: columns to return per coin (default id, symbol, name, issuer, score, grade, confidence, stale, computed_at); name "categories" for category scores sort_by: "score_desc" (default), "score_asc", or "symbol" One coin's detail: entity_read(query).

    mcp-tool

    {
      "type": "object",
      "title": "get_stablecoin_scoresArguments",
      "properties": {
        "limit": {
          "type": "integer",
          "title": "Limit",
          "default": 25
        },
        "fields": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "title": "Fields",
          "default": null
        },
        "sort_by": {
          "type": "string",
          "title": "Sort By",
          "default": "score_desc"
        }
      }
    }
    arguments 24 lines
  • receipt_verify unknown never probed

    Verify a receipt or citation hash from an envelope (basis_answer, entity_read). Resolves it against the attestation tables and returns what it attests to, or that it is unknown. ``source`` optionally restricts the table.

    mcp-tool

    {
      "type": "object",
      "title": "receipt_verifyArguments",
      "required": [
        "hash"
      ],
      "properties": {
        "hash": {
          "type": "string",
          "title": "Hash"
        },
        "source": {
          "type": "string",
          "title": "Source",
          "default": null
        }
      }
    }
    arguments 18 lines
  • score_history unknown never probed

    Daily SII score history for a stablecoin: a list of {date, score, grade} only. Parameters: coin: symbol, slug or contract address (resolved like entity_read) days: lookback window, 1-365 (default 30)

    mcp-tool

    {
      "type": "object",
      "title": "score_historyArguments",
      "required": [
        "coin"
      ],
      "properties": {
        "coin": {
          "type": "string",
          "title": "Coin"
        },
        "days": {
          "type": "integer",
          "title": "Days",
          "default": 30
        }
      }
    }
    arguments 18 lines
  • basis_data unknown never probed

    Market, governance and risk data in one tool. Pick a kind: liquidity_depth (entity=coin id), yield_data (entity=protocol, optional), governance_activity (entity=protocol slug; window=days, 90), bridge_flows (entity=bridge id, optional), exchange_health (entity=exchange id, optional), volatility (entity=asset id), incidents (entity=entity id, optional), peg_monitor (summary of latest deviation + status per coin; detail=true with entity returns that coin's 5-minute series, window=hours, 24), venue_shift (entity=operator slug, optional), asset_footprint (entity=token or symbol), divergence (capital-flow vs quality signals; severity=notable|alert|critical, limit=20, window=hours 24), treasury_events (entity=wallet, optional), riskiest_wallets (limit=20), scoring_backlog (limit=20). Responses are capped near 12 KB; an unknown kind returns the list of kinds.

    mcp-tool

    {
      "type": "object",
      "title": "basis_dataArguments",
      "required": [
        "kind"
      ],
      "properties": {
        "kind": {
          "type": "string",
          "title": "Kind"
        },
        "limit": {
          "type": "integer",
          "title": "Limit",
          "default": null
        },
        "detail": {
          "type": "boolean",
          "title": "Detail",
          "default": false
        },
        "entity": {
          "type": "string",
          "title": "Entity",
          "default": null
        },
        "window": {
          "type": "integer",
          "title": "Window",
          "default": null
        },
        "severity": {
          "type": "string",
          "title": "Severity",
          "default": null
        }
      }
    }
    arguments 38 lines
  • basis_answer reads unknown never probed

    Ask the Basis Agent a question about attested risk state. Answers cite attestation hashes; ungroundable queries are refused. Never recommends positions or forecasts. Pass your hub API key (x-api-key header or ?apikey=) to attribute reads. Multi-turn: pass the envelope's session_id back as session_id. Parameters: query: The question (max 4000 chars). session_id: Session UUID from a previous envelope (optional).

    mcp-tool

    {
      "type": "object",
      "title": "basis_answerArguments",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "title": "Query"
        },
        "session_id": {
          "type": "string",
          "title": "Session Id",
          "default": null
        }
      }
    }
    arguments 18 lines
  • entity_read unknown 24h ago

    Look up any entity by symbol, slug, contract/wallet address, operator or vault name. Returns {entity_type, id, score, grade, confidence, receipt_hash, links}. When nothing resolves returns {match: null, did_you_mean: [up to 5 candidates]} rather than an error.

    mcp-tool

    {
      "type": "object",
      "title": "entity_readArguments",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "title": "Query"
        }
      }
    }
    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 da09ff31442268ea.

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