mcp-registry/com.fintechhodl/intel · v1.0.0
As of 2026-10-27 02:15 UTC, the Fintechhodl Intel MCP server is up with a Glimind reliability score of 73/100 (grade C). Over the last 30 days it answered 96% of Glimind's liveness checks.
Risk scores, dependencies and risk events for Base DeFi yields. Pay per call in USDC via x402.
Point your MCP client at this streamable-http endpoint: https://intel.fintechhodl.com/mcp
16 of 16 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
Reachable 96.0% of the time over the last 30 days.
Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.fintechhodl%2Fintel/fixes
{
"name": "get_closure",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"entity"
],
"properties": {
"entity": {
"type": "string",
"pattern": "^[A-Za-z0-9:._#+-]{1,120}$",
"examples": [
"protocol:morpho-blue",
"protocol:aave-v3"
],
"description": "Entity id: protocol:<slug>, stablecoin:<id>, oracle:<name>, curator:<name> or issuer:<name>, as found in dependency graphs."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_dependency_graph",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"id"
],
"properties": {
"id": {
"type": "string",
"pattern": "^[A-Za-z0-9:._#+-]{1,120}$",
"examples": [
"e0672197-9f3e-4414-bca5-e6b4c90aa469"
],
"description": "Opportunity id, as returned by the free /api/v1/opportunities route."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_dependents",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"entity"
],
"properties": {
"entity": {
"type": "string",
"pattern": "^[A-Za-z0-9:._#+-]{1,120}$",
"examples": [
"protocol:morpho-blue",
"protocol:aave-v3"
],
"description": "Entity id: protocol:<slug>, stablecoin:<id>, oracle:<name>, curator:<name> or issuer:<name>, as found in dependency graphs."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.fintechhodl/intel"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.fintechhodl/intel"}) over MCP.
search_opportunities ~533 tokensget_yield_farming ~481 tokensget_yields ~465 tokensget_lending_rates ~426 tokensget_opportunity_card ~323 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.fintechhodl%2Fintel?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.fintechhodl%2Fintel?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.fintechhodl%2Fintel.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.fintechhodl%2Fintel.svg :target: https://glimind.com/server/mcp-registry%2Fcom.fintechhodl%2Fintel?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:7b8765aa41af60b8…, first seen 2026-10-26, included at leaf 71938 of 76,802. Version history · verify what your client received.
Compare: most reliable knowledge servers · most reliable data servers · most reliable search servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-27 02:15 UTC, the Fintechhodl Intel MCP server is up with a Glimind reliability score of 73/100 (grade C). Over the last 30 days it answered 96% of Glimind's liveness checks.
Fintechhodl Intel MCP server advertises 16 tools, including get_closure, get_dependency_graph, get_dependents, get_history, get_incidents.
Point your MCP client at this streamable-http endpoint: https://intel.fintechhodl.com/mcp
Glimind scanned all 16 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.