Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.Abstract36/stakechain

REMOTE · STAKECHAIN-API.VERCEL.APP · 2 COMPONENTS

Live Base staking/lending yields (APY, TVL, vaults) as MCP tools; x402 pay-per-request tier

+2 this week 69 Trust /100

Last scanned (42 minutes ago)

Scores higher than 54% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability68
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1476 tokens (~246/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 0
    • Tool “list_base_yields” rewrote its description, which is the text the model reads security
    • Tool “list_lending_vaults” rewrote its description, which is the text the model reads security
  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 −1
    • Tool “yield_history” rewrote its description, which is the text the model reads security
    • Tool “list_lending_vaults” rewrote its description, which is the text the model reads security
    • Tool “best_yield” rewrote its description, which is the text the model reads security
    • Tool “list_base_yields” rewrote its description, which is the text the model reads security
    • Tool “market_profile” rewrote its description, which is the text the model reads security
    • Schema quality: pass → fail ▼ functional
    • Schema quality: good → excellent functional
    • New tool “build_deposit” functional
  • 30 Oct 26 +1
    • Tool “list_lending_vaults” rewrote its description, which is the text the model reads security
    • Schema quality: 59 → 78 ▼ functional
    • New tool “market_profile” functional
    • New tool “yield_history” functional
  • 29 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 28 Oct 26 67

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://stakechain-api.vercel.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.vercel.app CN=WR1,O=Google Trust Services,C=US 31 Oct 2026 29 Jan 2027 RSA 2048 SHA256-RSA 9c5f0e6a35c955e113044c86848e4cd5
SANs: *.vercel.app
CN=WR1,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7fd9e2c2d2048a0474b627a26d0868a7
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of stakechain-api.vercel.app. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
vercel.app. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://stakechain-api.vercel.app/mcp Verified 200
http (plaintext) http://stakechain-api.vercel.app/mcp HTTPS enforced 308 https://stakechain-api.vercel.app/mcp
MCP tools · 6 exposed · ~1,476 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
best_yield ~175

The single highest-APY pool on Base for one asset, with junk-farm filters applied (minimum TVL, APY ceiling, no impermanent-loss exposure). Use this for a direct 'where is the best rate for X' question when one answer is wanted rather than a list. Use something else when: you want to compare several options (`list_base_yields`); you intend to deposit (`list_lending_vaults` returns the address). Important: it ranks by rate alone. A high answer here is a starting point, not a verdict — follow it with `market_profile` for the curator's cut and whether the money can be withdrawn, and `yield_history` for whether the rate has held.

NameTypeReqDescription
assetstringyesAsset symbol, e.g. ETH, USDC, cbBTC

No output schema declared.

No examples provided.

build_deposit ~270

Turns a chosen market into signed-ready calldata: an ordered list of transactions to deposit into it or leave it, across Morpho vaults, Aave reserves, Moonwell markets and this project's staking pools — three different protocol interfaces behind one call. The approve step is included only when the current allowance does not already cover the amount, read on-chain at request time. Use this once a market has been chosen and the decision is made. Use something else when: still choosing (`list_lending_vaults`, `best_yield`); weighing whether to go ahead (`market_profile`, `yield_history`). Nothing is signed or sent — the caller holds the keys. Simulate before sending. `amount: "all"` on a withdrawal exits by share rather than by figure, so interest accruing between the call and the block is not left behind.

NameTypeReqDescription
actionstring–Defaults to deposit
amountstringyesWhole asset units, e.g. '25.5' — or 'all' to exit a position completely
fromstringyesThe address that will sign and hold the position
poolstringyesMarket id from list_lending_vaults, e.g. 'sparkusdc', 'aave-usdc', 'mUSDC'

No output schema declared.

No examples provided.

list_base_yields ~294

Survey staking and lending opportunities on Base: APY, TVL, project and asset for each. Use this for breadth — browsing the market, answering 'what is available', or filtering a wide set. It covers pools this server cannot deposit into as well as ones it can. Use something else when: you want one asset's single best option (`best_yield`); you intend to deposit and need a contract address (`list_lending_vaults`); you are judging one market rather than comparing many (`market_profile`). Every row says where its number came from: `source` is `onchain` (read from the protocol's contracts at `block`, so the figure can be re-derived), `morpho-api`, or `defillama` — a third-party snapshot that carries no Moonwell USDC market at all and understates Aave's Base reserve. Ranks by TVL unless sortByApy is set. Four-digit emission farms are filtered out by default. Returns market data, not a recommendation; any row's `pool` id can be passed to `yield_history`.

NameTypeReqDescription
assetstring–Filter by asset symbol, e.g. ETH, USDC
minTvlnumber–Minimum TVL in USD
sortByApyboolean–Sort by APY descending
stableboolean–Only stablecoin pools

No output schema declared.

No examples provided.

list_lending_vaults ~201

The Base lending shelf an agent can act on: Morpho ERC-4626 vaults, Aave V3 reserves, Moonwell markets and this project's own staking pools, each with the contract address to deposit into (`depositTo`), the asset's address and decimals, and a `risk` block (fee, age, concentration, utilisation, incentive share). Use this whenever a deposit might follow, or when you need a market id to pass to `market_profile` or `yield_history`. Use `list_base_yields` instead when surveying the wider market, including pools that cannot be deposited into here. Rates for Aave and Moonwell are read from their own contracts, so markets missing from aggregator snapshots appear here. Each row carries `source` and `block`: an `onchain` row can be re-read at that block and checked, a `morpho-api` row comes from Morpho's own GraphQL.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

market_profile ~344

Risk profile for one market, for the moment before capital is committed. Use this when a specific market has been chosen and the question is whether to go ahead. It is the one tool that answers 'what else should I know besides the rate'. Use something else when: you are still choosing between markets (`list_base_yields`, `best_yield`); you only want to know whether the rate moved (`yield_history`); you need the deposit address (`list_lending_vaults`). Prerequisite: the market must be on this server's shelf — a vault, reserve or pool from `list_lending_vaults`. Arbitrary pool ids from `list_base_yields` will not resolve. Returns `score` (0-100) and `band` ('solid', 'fair', 'thin' or 'fragile'), plus a `signals` object holding the six inputs behind it: size (TVL), track_record (days running), stability (APY volatility from daily snapshots), yield_quality (share of the APY that is borrower interest rather than incentives that can stop), cost (the curator's percentage cut) and diversification (share sitting in the largest position). Each signal carries its raw value and its sub-score, and `method.weights` gives the weighting, so the score can be recomputed. A signal lacking data reports score null and is excluded from the weighting rather than guessed at. Pair with `yield_history` for an unusually high rate. Describes what has happened, not what will.

NameTypeReqDescription
poolstringyesVault symbol, address, or protocol-asset (e.g. sparkusdc, aave-usdc)

No output schema declared.

No examples provided.

yield_history ~192

Daily APY and TVL history for one market, with min, median, max and volatility over the window. Use this for one question only: has this rate held, or did it appear yesterday? Call it before acting on any unusually high rate. Use something else when: you want the other risk factors — fee, size, utilisation, concentration — which are in `market_profile`; you are still choosing a market (`list_base_yields` or `best_yield`). Prerequisite: a market id from one of the list tools. Check `observations` before concluding anything — a market added recently has few snapshots, and a short series is not evidence of stability.

NameTypeReqDescription
daysnumber–Look-back window in days, default 30
poolstringyesMarket id: a pool id from list_base_yields, or vault:<address> from list_lending_vaults

No output schema declared.

No examples provided.

Install

How do I install the io.github.Abstract36/stakechain MCP server?

io.github.Abstract36/stakechain is a hosted endpoint at https://stakechain-api.vercel.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · stakechain-api.vercel.app

# add to Claude Code
claude mcp add --transport http abstract36-stakechain 'https://stakechain-api.vercel.app/mcp'
Common questions

What is the io.github.Abstract36/stakechain MCP server?

io.github.Abstract36/stakechain is an MCP server listed in the public MCP registry as io.github.Abstract36/stakechain. Live Base staking/lending yields (APY, TVL, vaults) as MCP tools; x402 pay-per-request tier. This page covers its hosted endpoint (https://stakechain-api.vercel.app/mcp).

Is the io.github.Abstract36/stakechain MCP server safe to use?

io.github.Abstract36/stakechain scores 69 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.Abstract36/stakechain MCP server expose?

io.github.Abstract36/stakechain exposes 6 tools: list_base_yields, best_yield, list_lending_vaults, market_profile, yield_history, build_deposit. Their descriptions and schemas cost roughly 1,476 tokens of context every time the server is loaded.

Does the io.github.Abstract36/stakechain MCP server require authentication?

No. We connected to io.github.Abstract36/stakechain without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.Abstract36/stakechain MCP server still maintained?

io.github.Abstract36/stakechain is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.