mcp-registry/io.github.edvyno/akari-crypto-intel · registry v1.3.1 · server reports v1.0.0
Also listed as github/edvyno/akari-x402-mcp, mcp-registry/io.github.edvyno/akari-x402
claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clientsAs of 2026-11-22 17:14 UTC, the Edvyno Akari Crypto Intel MCP server is up with a Glimind reliability score of 62/100 (grade C). Over the last 30 days it answered 93.7% of Glimind's liveness checks. It had 6 outages in 90 days, with a median recovery of 7 minutes.
x402-paid crypto intel: HL funding, TradingView TA, wallet verdicts, x402 audits. 35 tools.
Point your MCP client at this streamable-http endpoint: https://03s9tr085tfe5agke0tpqng34o.ingress.quanglong.org/mcp
Up 93.3% of the time over the 6 days we have observed; median recovery 7 min.
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.
35 of 35 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 →
2 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
2 parameter(s) across 1 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
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 →
6 tools share an identical description with another tool on this server.
Make each description say how the tool differs from its siblings, or the model will pick between them at random. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 1 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.edvyno%2Fakari-crypto-intel/fixes
{
"name": "akari_akash_deploy_kit",
"description": "Akash deployment kit — the exact SDL, boot-test and lease runbook we used to put a live container on Akash, including the four failure modes that cost us real attempts: deposits must be uact not uakt, the BME minimum mint is 10 ACT, akash 2.1.2 has no provider subcommand, and provider-services takes the node as an env var not a flag. Drop in your image and port, get a working manifest plus a verified proof URI from our own lease.",
"inputSchema": {
"type": "object",
"properties": {},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "akari_signal_execute",
"description": "Hyperliquid crypto trading signal — the funding+momentum confluence engine's current best setup as a complete signal: side, basis, entry parameters, leverage cap. Use when you want a ready trading signal, not raw data.",
"inputSchema": {
"type": "object",
"properties": {},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}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/io.github.edvyno/akari-crypto-intel"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.edvyno/akari-crypto-intel"}) over MCP.
akari_catalog_report_history ~171 tokensakari_hyperliquid_funding ~170 tokensakari_technical_analysis ~170 tokensakari_wallet_risk_verdict ~170 tokensakari_catalog_report ~169 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.
Shows whether the server is live and its agent-readiness score; it updates within the hour.
[](https://glimind.com/server/mcp-registry%2Fio.github.edvyno%2Fakari-crypto-intel?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.edvyno%2Fakari-crypto-intel?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fio.github.edvyno%2Fakari-crypto-intel.svg" alt="MCP server status"></a>
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:cf233880db5c61de…, first seen 2026-11-16, included at leaf 302375 of 384,710. Version history · verify what your client received.
Compare: most reliable data servers · most reliable retrieval servers · most reliable knowledge servers · most reliable finance servers · most reliable security 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?ref=install-server
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp?ref=install-server"
}
}
}
A free Glimind key lets your agent check whether a server works right now before it calls it, and switch to a live one when it doesn't. No signup, no card.
As of 2026-11-22 17:14 UTC, the Edvyno Akari Crypto Intel MCP server is up with a Glimind reliability score of 62/100 (grade C). Over the last 30 days it answered 93.7% of Glimind's liveness checks. It had 6 outages in 90 days, with a median recovery of 7 minutes.
Edvyno Akari Crypto Intel MCP server advertises 35 tools, including akari_akash_deploy_kit, akari_alpha_brief, akari_audit_plus, akari_batch, akari_board.
Point your MCP client at this streamable-http endpoint: https://03s9tr085tfe5agke0tpqng34o.ingress.quanglong.org/mcp
Glimind scanned all 35 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.