FinTech Hodl Base DeFi risk intel
REMOTE · INTEL.FINTECHHODL.COM
Risk scores, dependencies and risk events for Base DeFi yields. Pay per call in USDC via x402.
Available components
Last scanned (22 hours ago)
Scores higher than 44% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Crypto and Web3
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 16 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2863 tokens (~178/item across 16 items; 16 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 Management30
- Stability observed for 9 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 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 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
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 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 2 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.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 26 Oct 26 +54
- HSTS header: unverified → fail ▼ security
- HTTPS: pass → unverified ▼ security
- Injection markers: unverified → pass ▲ security
- TLS certificate: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 16 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 100 functional
- 25 Oct 26 4
First indexed and scored.
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 4 Nov 2026 · Probed https://intel.fintechhodl.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=fintechhodl.com | CN=YE2,O=Let's Encrypt,C=US | 24 Oct 2026 | 22 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6735dcb658e6360130f977392fbaba5bc7c |
| SANs: *.fintechhodl.com, fintechhodl.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of intel.fintechhodl.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| fintechhodl.com. | 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 |
|---|---|
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://intel.fintechhodl.com/mcp | Verified | 200 | |
| http (plaintext) | http://intel.fintechhodl.com/mcp | Inconclusive | 405 |
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 →
get_closure ~146
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 protocol:morpho-blue. Unknown ids answer 404 and invalid arguments 400 before any payment; 503 while data refreshes; charged only for a 200. Price: $0.01 USDC on Base (x402), charged only for a successful answer.
| Name | Type | Req | Description |
|---|---|---|---|
| entity | string | yes | Entity id: protocol:<slug>, stablecoin:<id>, oracle:<name>, curator:<name> or issuer:<name>, as found in dependency graphs. |
No output schema declared.
No examples provided.
get_dependency_graph ~143
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 /api/v1/opportunities. Unknown ids answer 404 and invalid arguments 400 before any payment; 503 while data refreshes; charged only for a 200. Price: $0.01 USDC on Base (x402), charged only for a successful answer. In this MCP server, ids come from search_opportunities.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Opportunity id, as returned by the free /api/v1/opportunities route. |
No output schema declared.
No examples provided.
get_dependents ~149
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 protocol:morpho-blue. Unknown ids answer 404 and invalid arguments 400 before any payment; 503 while data refreshes; charged only for a 200. Price: $0.01 USDC on Base (x402), charged only for a successful answer.
| Name | Type | Req | Description |
|---|---|---|---|
| entity | string | yes | Entity id: protocol:<slug>, stablecoin:<id>, oracle:<name>, curator:<name> or issuer:<name>, as found in dependency graphs. |
No output schema declared.
No examples provided.
get_history ~151
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 arguments 400 before any payment; 503 while data refreshes; charged only for a 200. Price: $0.01 USDC on Base (x402), charged only for a successful answer. In this MCP server, ids come from search_opportunities.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Look-back in days (default 30). |
| id | string | yes | Opportunity id, as returned by the free /api/v1/opportunities route. |
No output schema declared.
No examples provided.
get_incidents ~137
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. Unknown ids answer 404 and invalid arguments 400 before any payment; 503 while data refreshes; charged only for a 200. Price: $0.02 USDC on Base (x402), charged only for a successful answer.
| Name | Type | Req | Description |
|---|---|---|---|
| entity | string | – | Only incidents for this entity (optional). |
| limit | integer | – | At most this many incidents (default 100). |
No output schema declared.
No examples provided.
get_lending_rates ~280
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 for choosing where to lend USDC, ETH or stablecoins. Ids work with every other route. 404 for unknown paths and 400 for invalid arguments, before any payment; 503 while data refreshes; charged only for a 200. Price: $0.01 USDC on Base (x402), charged only for a successful answer.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | – | Token symbol, e.g. USDC or WETH. |
| limit | integer | – | How many items (default 20). |
| min_apy | number | – | Minimum quoted APY, percent. |
| realized_only | boolean | – | Only opportunities with a realized on-chain APY. |
| risk_max | number | – | Maximum risk score (0-100, lower is lower modelled risk). |
| sort | string | – | Order: risk_adjusted (default) ranks by opportunity score; realized_apy by the 30-day realized APY; sustainable_apy by the APY expected once incentives fade. |
| stable_only | boolean | – | Only stablecoin principal. |
No output schema declared.
No examples provided.
get_opportunity_card ~199
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, recommending or comparing a Base yield. The id comes from the free /api/v1/opportunities. Unknown ids answer 404 and invalid arguments 400 before any payment; 503 while data refreshes; charged only for a 200. Price: $0.01 USDC on Base (x402), charged only for a successful answer. In this MCP server, ids come from search_opportunities.
| Name | Type | Req | Description |
|---|---|---|---|
| capital | number | – | Capital in USD for the expected-return figures (default 10000). |
| duration | integer | – | Holding period in days for the expected-return figures (default 365). |
| id | string | yes | Opportunity id, as returned by the free /api/v1/opportunities route. |
No output schema declared.
No examples provided.
get_opportunity_score ~188
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 from the free /api/v1/opportunities. Unknown ids answer 404 and invalid arguments 400 before any payment; 503 while data refreshes; charged only for a 200. Price: $0.01 USDC on Base (x402), charged only for a successful answer. In this MCP server, ids come from search_opportunities.
| Name | Type | Req | Description |
|---|---|---|---|
| capital | number | – | Capital in USD for the expected-return figures (default 10000). |
| duration | integer | – | Holding period in days for the expected-return figures (default 365). |
| id | string | yes | Opportunity id, as returned by the free /api/v1/opportunities route. |
No output schema declared.
No examples provided.
get_protocol_risk ~122
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 404 and invalid arguments 400 before any payment; 503 while data refreshes; charged only for a 200. Price: $0.02 USDC on Base (x402), charged only for a successful answer.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | DeFiLlama protocol slug. |
No output schema declared.
No examples provided.
get_risk_events ~167
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. Unknown ids answer 404 and invalid arguments 400 before any payment; 503 while data refreshes; charged only for a 200. Price: $0.02 USDC on Base (x402), charged only for a successful answer.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Look-back in days (default 7). |
| entity | string | – | Only events for this entity (optional). |
| limit | integer | – | At most this many events (default 100). |
| severity | string | – | Lowest severity to include (default low). |
No output schema declared.
No examples provided.
get_stablecoin_risk ~113
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 arguments 400 before any payment; 503 while data refreshes; charged only for a 200. Price: $0.02 USDC on Base (x402), charged only for a successful answer.
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | yes | Stablecoin symbol. |
No output schema declared.
No examples provided.
get_yield_farming ~313
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 fade, TVL, a risk score, and realized APY where measured. Useful for picking farms worth their risk. Ids work with every other route. 404 for unknown paths and 400 for invalid arguments, before any payment; 503 while data refreshes; charged only for a 200. Price: $0.01 USDC on Base (x402), charged only for a successful answer.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | – | Token symbol, e.g. USDC or WETH. |
| limit | integer | – | How many items (default 20). |
| min_apy | number | – | Minimum quoted APY, percent. |
| realized_only | boolean | – | Only opportunities with a realized on-chain APY. |
| risk_max | number | – | Maximum risk score (0-100, lower is lower modelled risk). |
| sort | string | – | Order: risk_adjusted (default) ranks by opportunity score; realized_apy by the 30-day realized APY; sustainable_apy by the APY expected once incentives fade. |
| stable_only | boolean | – | Only stablecoin principal. |
| type | string | – | lp, stable_lp (stablecoin pairs), concentrated (concentrated liquidity) or vault (auto-compounding vaults). |
No output schema declared.
No examples provided.
get_yield_premium ~171
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 free /api/v1/opportunities. Unknown ids answer 404 and invalid arguments 400 before any payment; 503 while data refreshes; charged only for a 200. Price: $0.01 USDC on Base (x402), charged only for a successful answer. In this MCP server, ids come from search_opportunities.
| Name | Type | Req | Description |
|---|---|---|---|
| benchmark | string | – | Reference opportunity id (optional); by default a low-risk lending market on the same asset. |
| id | string | yes | Opportunity id, as returned by the free /api/v1/opportunities route. |
No output schema declared.
No examples provided.
get_yields ~293
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 for finding the best yields on Base and spotting advertised yields that are not being paid. Ids work with every other route. 404 for unknown paths and 400 for invalid arguments, before any payment; 503 while data refreshes; charged only for a 200. Price: $0.01 USDC on Base (x402), charged only for a successful answer.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | – | Token symbol, e.g. USDC or WETH. |
| limit | integer | – | How many items (default 20). |
| min_apy | number | – | Minimum quoted APY, percent. |
| realized_only | boolean | – | Only opportunities with a realized on-chain APY. |
| risk_max | number | – | Maximum risk score (0-100, lower is lower modelled risk). |
| sort | string | – | Order: risk_adjusted (default) ranks by opportunity score; realized_apy by the 30-day realized APY; sustainable_apy by the APY expected once incentives fade. |
| stable_only | boolean | – | Only stablecoin principal. |
| type | string | – | Opportunity type. |
No output schema declared.
No examples provided.
list_prices ~19
The list of paid routes with their prices. Free.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_opportunities ~272
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 client. Free; at most 60 calls an hour per client.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | – | Token symbol the opportunity holds. |
| capital | number | – | Capital in USD for the expected-return figures (default 10000). |
| duration | integer | – | Holding period in days for the expected-return figures (default 365). |
| include_direct | boolean | – | Also list plain token holdings. |
| limit | integer | – | At most this many results (default 20). |
| management | string | – | Passive (hold), active (needs rebalancing) or any (default). |
| min_apy | number | – | Lowest APY to include, in percent. |
| q | string | – | Search words over protocol, market and asset names (letters, digits, spaces, dots, dashes, underscores; at most 60). |
| risk_max | number | – | Highest total risk score to include (0-100, lower is lower modelled risk). |
| stable_only | boolean | – | Only opportunities whose principal is a stablecoin. |
| type | string | – | Opportunity type. |
No output schema declared.
No examples provided.
How do I install the FinTech Hodl Base DeFi risk intel MCP server?
FinTech Hodl Base DeFi risk intel is a hosted endpoint at https://intel.fintechhodl.com/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 · intel.fintechhodl.com
claude mcp add --transport http com-fintechhodl-intel 'https://intel.fintechhodl.com/mcp'
What is the FinTech Hodl Base DeFi risk intel MCP server?
FinTech Hodl Base DeFi risk intel is an MCP server listed in the public MCP registry as com.fintechhodl/intel. Risk scores, dependencies and risk events for Base DeFi yields. Pay per call in USDC via x402. This page covers its hosted endpoint (https://intel.fintechhodl.com/mcp).
Is the FinTech Hodl Base DeFi risk intel MCP server safe to use?
FinTech Hodl Base DeFi risk intel scores 63 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 FinTech Hodl Base DeFi risk intel MCP server expose?
FinTech Hodl Base DeFi risk intel exposes 16 tools: search_opportunities, get_yields, get_lending_rates, get_yield_farming, list_prices, and 11 more. Their descriptions and schemas cost roughly 2,863 tokens of context every time the server is loaded.
Does the FinTech Hodl Base DeFi risk intel MCP server require authentication?
No. We connected to FinTech Hodl Base DeFi risk intel without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the FinTech Hodl Base DeFi risk intel MCP server still maintained?
FinTech Hodl Base DeFi risk intel is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.