FinTech Hodl MCP server

• Registry namecom.fintechhodl/intelverified in the MCP registry

The registry name sits under fintechhodl.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-28
• Tools16
• Server calls itselffintechhodl-intel
• Server version1.0.0
• Protocol version2025-06-18

On 2026-10-28 the server answered initialize and tools/list without a sign-in. First answer in 316 ms.

• Its tools do every use case we checked: compare Base DeFi yields against published risk scores; read plain-English risk reports before committing capital.
• Checked on 5 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 5 so far
• What an agent can do with it2 of 2 use cases
• Answeredmeasuring5 of the 7 daily checks it takes to print a share
• Median first answer264 ms
• Space in an agent's context≈ 4,334 tokensthe definitions of all its tools (16), which an agent carries on every turn
• Tool definitionsB · 83 of 100
• Typed results0 of 16 toolsdeclared outputSchema: results come typed, read once

• Not saying whether it only reads or can destroy: 16 of 16

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• search_opportunities

  Search and filter every tracked Base yield opportunity, with total risk and opportunity scores. Useful for finding candidates and their ids before buying a card, score, history or dependency graph. Free, at most 60 calls an hour per…

• get_yields

  Realized APY for Base vaults and lending markets: the APY depositors actually earned over 7 and 30 days, read from on-chain share prices, next to the quoted APY, with a verdict (matches, overstated, understated) and a risk score. Useful…

• get_lending_rates

  Lending rates on Base: supply APY for every tracked money market and lending vault (Aave, Morpho, Compound, Moonwell and others), quoted next to the APY lenders actually earned over 7 and 30 days, read on-chain, with a risk score. Useful…

• get_yield_farming

  Yield farming opportunities on Base: liquidity pools, concentrated liquidity (Aerodrome Slipstream) and auto-compounding vaults, ranked risk-adjusted, with quoted APY split into fees and token rewards, the sustainable APY once incentives…

• list_prices

  The list of paid routes with their prices. Free.

• get_opportunity_card

  Full risk card for one Base yield opportunity: 0-100 risk score with the main risks and their evidence, yield sources, sustainable APY, expected return, liquidity, dependencies and recent risk events. Useful before depositing into…

• get_opportunity_score

  Scoring breakdown for one opportunity: total risk, the eight risk dimensions with every factor and its input, sustainability, liquidity, slippage, position size and confidence. Useful for auditing or explaining a risk score. The id comes…

• get_history

  Daily history of one opportunity's APY, TVL and risk scores. Useful for checking whether a yield is stable or newly inflated, and for trend charts. The id comes from the free /api/v1/opportunities. Unknown ids answer 404 and invalid…

• get_dependency_graph

  What one opportunity depends on: protocols, stablecoins and their issuers, oracles, bridges and vault curators, as a graph. Useful for finding hidden shared exposure before combining positions. The id comes from the free…

• get_closure

  Everything an entity (protocol, asset, stablecoin, curator) depends on, transitively, as a graph. Useful for tracing what a protocol or stablecoin ultimately relies on. Entity ids appear in dependency graphs, for example…

• get_dependents

  Which tracked Base opportunities depend on an entity (protocol, stablecoin, oracle, curator), with their total TVL. Useful for sizing the impact of an exploit, depeg or oracle failure. Entity ids appear in dependency graphs, for example…

• get_yield_premium

  Why one opportunity pays more than a reference: the APY gap in percentage points, explained by risk dimensions, incentives and extra dependencies. Useful for judging whether a higher yield is worth its extra risk. The id comes from the…

• get_protocol_risk

  Risk profile of one protocol on Base: age, TVL history, audits, exploit history, governance (admin, timelock, multisig, upgradeability, pause) and the risk of its opportunities. Useful for due diligence on a protocol. Unknown ids answer…

• get_stablecoin_risk

  Peg and supply risk of one stablecoin on Base: price history, supply change, mechanism and the opportunities that hold it. Useful before holding or lending a stablecoin, or when a depeg is suspected. Unknown ids answer 404 and invalid…

• get_risk_events

  Recent risk events on Base DeFi: TVL drops, depegs, exploits, APY moves and Morpho vault setting changes, with severity. Useful for monitoring positions or screening protocols for recent trouble. Entity ids appear in dependency graphs…

• get_incidents

  Labelled incidents (exploits, oracle failures, depegs, TVL collapses) affecting Base protocols and stablecoins. Useful for a protocol or stablecoin track record before trusting it with funds. Entity ids appear in dependency graphs…