_ registry / mcp streamable-http · checked 56m ago

protocol-change-feed

https://protocols.changefeed.dev

Registry code: 4da99e5ceb598112

api record

Protocol Change Feed for AI agents: governance proposals and votes (Snapshot), proxy upgrades and admin changes for major DeFi protocols and stablecoins on Ethereum and Base, and a live check of who can upgrade or control any contract. Free protocol list and quick check; full answers paid per call with x402 (USDC on Base); no account or API key.

endpoint
https://protocols.changefeed.dev/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 protocol-change-feed live?
Yes — it answered the hub's last check (checked 56m ago). It answered 100% of checks over the last 30 days.
Is protocol-change-feed free to use?
Yes — the hub reached it with no key and no payment.
What tools does protocol-change-feed have?
5 tools: protocol_changes, protocol_digest, contract_check, quick_check, list_protocols.
Is protocol-change-feed 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
479ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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 1 other origin: 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
7

distinct

settlements
19

last 2026-11-17

received on chain
0.17 USDC

shared-payto

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

  • list_protocols open 56m ago

    Every covered protocol: id, name, Snapshot spaces and watched contracts on Ethereum and Base. Free.

    mcp-tool

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

    Everything that changed in one protocol over a window: Snapshot proposals with live vote tallies, quorum and end time; proxy upgrades and admin changes with transactions; and the current implementation and admin of each watched contract. Costs $0.005 (x402, USDC).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "protocol"
      ],
      "properties": {
        "days": {
          "type": "integer",
          "maximum": 90,
          "minimum": 1,
          "description": "Look-back window in days (default 30, max 90)"
        },
        "protocol": {
          "type": "string",
          "description": "Protocol id from /v1/protocols, e.g. aave, uniswap, lido, usdc"
        }
      }
    }
    arguments 19 lines
  • protocol_digest unknown never probed

    One call across every watched protocol: governance votes open now, proposals decided in the window with the winning choice, and every contract upgrade or admin change. Costs $0.02 (x402, USDC).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "days": {
          "type": "integer",
          "maximum": 30,
          "minimum": 1,
          "description": "Look-back window in days (default 7, max 30)"
        }
      }
    }
    arguments 12 lines
  • contract_check unknown 56m ago

    Live check of any contract on Ethereum or Base before you interact with it: is it an upgradeable proxy (EIP-1967, beacon, ZeppelinOS), its current implementation, and whether upgrades and owner() are controlled by a single key, a Safe multisig (m-of-n) or a timelock. Adds the upgrade history when the contract is one this feed watches. Costs $0.005 (x402, USDC).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "chain",
        "address"
      ],
      "properties": {
        "chain": {
          "type": "string",
          "description": "Chain: ethereum, base"
        },
        "address": {
          "type": "string",
          "description": "Contract address, 0x followed by 40 hex characters"
        }
      }
    }
    arguments 18 lines
  • quick_check unknown 56m ago

    Free: counts of active and recent governance proposals and of contract upgrades or admin changes for one protocol, without the details. About 20 calls a minute per client.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "protocol"
      ],
      "properties": {
        "days": {
          "type": "integer",
          "maximum": 90,
          "minimum": 1,
          "description": "Look-back window in days (default 30, max 90)"
        },
        "protocol": {
          "type": "string",
          "description": "Protocol id from /v1/protocols, e.g. aave, uniswap, lido, usdc"
        }
      }
    }
    arguments 19 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 4da99e5ceb598112.

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

_ also on changefeed.dev 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.