stakechain MCP server
io.github.Abstract36/stakechainAbstract36streamable-httpv0.3.0Scanned
Live Base staking/lending yields (APY, TVL, vaults) as MCP tools; x402 pay-per-request tier
5 tools: 2 change things and 3 only read.
- Reads private data · 1
- Reads text others write · 0
- Can send data out · 0
- No findings
Sign-in required, no OAuth metadata. Remote posture
Anlyon alternative
2 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the stakechain MCP server can do
The stakechain MCP server is published by the GitHub account Abstract36. It has 5 tools. It can create or change data (2 tools: market_profile and yield_history), but cannot delete data. 3 tools only read.
1 tool reads private data (list_lending_vaults).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its tools changed once since Anlyon Radar first saw them.
Last scanned Oct 30, 2026, version 0.3.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 2Claude Code: ask
market_profileWhat to weigh besides the rate: size, how long the market has run, rate stability, how much of the APY is lending interest rather than incentives that can stop, the curator's cut, …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 What to weigh besides the rate: size, how long the market has run, rate stability, how much of the APY is lending interest rather than incentives that can stop, the curator's cut, and how concentrated the deposits are. Returns every input alongside a score and the weights used, so the number can be recomputed rather than taken on faith.
yield_historyRate history for one market: daily APY/TVL plus min, median, max and volatility.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 Rate history for one market: daily APY/TVL plus min, median, max and volatility. Answers whether today's APY is typical for this market or a spike — a current rate on its own cannot tell you that.
Only reads 3Show 3 read-only tools
best_yieldGet the single highest-APY pool on Base for a given asset symbol (junk-farm filters built in).No findings
Why it is in this group
- The description's first verb is "get": a word for reading.
Description, as the server wrote it Get the single highest-APY pool on Base for a given asset symbol (junk-farm filters built in).
list_base_yieldsList current staking/lending yield opportunities on Base (APY, TVL, project).No findings
Why it is in this group
- The name "list_base_yields" says "list": a word for reading.
Description, as the server wrote it List current staking/lending yield opportunities on Base (APY, TVL, project). Optional filters.
list_lending_vaultsList curated lending markets on Base — Morpho ERC-4626 vaults and Aave V3 reserves: address, asset, APY, TVL.Reads private dataNo findings
Why it is in this group
- The name "list_lending_vaults" says "list": a word for reading.
What it can reach
- private-dataThe name "list_lending_vaults" says "list" and "vault": it reads secrets.
- private-dataThe description's first sentence says "list" and "vault": it reads secrets.
Description, as the server wrote it List curated lending markets on Base — Morpho ERC-4626 vaults and Aave V3 reserves: address, asset, APY, TVL.
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 untrusted-input or outbound.
- Reads private data1
- 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 19, 2026, 17:24 UTC, unchanged since Nov 12, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 410
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- 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
The probe stopped: initialize answered HTTP 410.
Posture changes
- Nov 12, 2026
- HTTP status of an anonymous initialize: 200 to 410
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 4 to 0
- Protocol version: 2025-06-18 to none
- Nov 5, 2026
- Tools that change things, listed without credentials: 0 to 4
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.
PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 410; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 4 -> 0 (and 1 more).View diff
- HTTP status of an anonymous initialize: 200 to 410
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 4 to 0
- Protocol version: 2025-06-18 to none
PostureRemote posture changed. Tools that change things, listed without credentials: 0 -> 4.View diff
- Tools that change things, listed without credentials: 0 to 4
Tools2 added, 1 changed.+2 added~1 changedView diff
- Added:market_profileChanges things
- Added:yield_historyChanges things
- Changed:list_lending_vaultsOnly readsdescription
Install
Pinned to version 0.3.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http stakechain https://stakechain-api.vercel.app/mcpclaude mcp add --transport http stakechain https://stakechain-api.vercel.app/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__stakechain__list_base_yields",
"mcp__stakechain__best_yield",
"mcp__stakechain__list_lending_vaults"
],
"ask": [
"mcp__stakechain__market_profile",
"mcp__stakechain__yield_history"
],
"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 stakechain. Review it before you use it.
Capability tags behind 1 rule
- mcp__stakechain__list_lending_vaults private-data
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/io.github.Abstract36/stakechain/verify?hash=bf23fa267031bb9ca64aa26daf288b82abde2eea9c03dd78f66b0181e2bd9fe3" | jq -e '.changed == false'Pinned hash bf23fa267031, from Oct 30, 2026, 19:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.Abstract36/stakechain/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.Abstract36/stakechain)Source: MCP Registry · repository. Synced Nov 6, 2026, 22:17 UTC.
stakechain MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the stakechain MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, 2 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 stakechain MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the stakechain 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 stakechain MCP server have?
- 5 tools: 2 write, 3 read. market_profile, yield_history, list_base_yields, best_yield and list_lending_vaults.
Does the stakechain MCP server need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the stakechain MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the stakechain MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Oct 30, 2026. Every change is on this page and in its Atom feed.