Protocol Change Feed MCP server
dev.changefeed/protocol-change-feedchangefeed.devstreamable-httpv0.1.0Scanned
DeFi governance votes, contract upgrades, and who controls any contract. Paid per call via x402.
5 tools: 4 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
4 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Protocol Change Feed MCP server can do
The Protocol Change Feed MCP server is published by changefeed.dev, a domain the MCP Registry verified. It has 5 tools. It can create or change data (4 tools: quick_check, protocol_changes, contract_check and protocol_digest), but cannot delete data. 1 tool only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 17, 2026, version 0.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
5 tools
Changes things 4Claude Code: ask
contract_checkLive 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 upgra…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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).
protocol_changesEverything 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 c…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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).
protocol_digestOne 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.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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).
quick_checkFree: counts of active and recent governance proposals and of contract upgrades or admin changes for one protocol, without the details.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
Only reads 1Show 1 read-only tool
list_protocolsEvery covered protocol: id, name, Snapshot spaces and watched contracts on Ethereum and Base.No findings
Why it is in this group
- The name "list_protocols" says "list": a word for reading.
Description, as the server wrote it Every covered protocol: id, name, Snapshot spaces and watched contracts on Ethereum and Base. Free.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 17, 2026, 15:19 UTC, unchanged since Nov 17, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 4
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://protocols.changefeed.dev/mcp: tools/list returned 5 tools to an anonymous client, including quick_check (write), protocol_changes (write), contract_check (write), protocol_digest (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http protocol-change-feed https://protocols.changefeed.dev/mcpclaude mcp add --transport http protocol-change-feed https://protocols.changefeed.dev/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__protocol-change-feed__list_protocols"
],
"ask": [
"mcp__protocol-change-feed__quick_check",
"mcp__protocol-change-feed__protocol_changes",
"mcp__protocol-change-feed__contract_check",
"mcp__protocol-change-feed__protocol_digest"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as protocol-change-feed. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/dev.changefeed/protocol-change-feed/verify?hash=4629662c3c0713c6efde4d9a325e3177dfe863dec844af6b478b28af69f87c6f" | jq -e '.changed == false'Pinned hash 4629662c3c07, from Nov 17, 2026, 02:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/dev.changefeed/protocol-change-feed/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/dev.changefeed/protocol-change-feed)Source: MCP Registry. Synced Nov 17, 2026, 02:17 UTC.
Protocol Change Feed MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Protocol Change Feed MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Protocol Change Feed MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Protocol Change Feed MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Protocol Change Feed MCP server have?
- 5 tools: 4 write, 1 read. quick_check, protocol_changes, contract_check, protocol_digest and list_protocols.
Does the Protocol Change Feed MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Protocol Change Feed MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Protocol Change Feed MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 17, 2026.