mcp-registry/ing.crank/crank · v3.4.9
As of 2026-10-20 15:07 UTC, the Crank MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 5 outages in 90 days, with a median recovery of 6 minutes.
Non-custodial DeFi tools for AI agents on Solana: swaps, perps, lending, staking, equities.
Claude Code
claude mcp add --transport http crank-mcp-server https://mcp.crank.ing/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"crank-mcp-server": {
"type": "http",
"url": "https://mcp.crank.ing/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
1149 parameter(s) across 196 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 →
196 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
1 tool(s) have parameters with no type (no type/enum/anyOf/$ref).
Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →
Loading this server's tool list costs an agent ~47,205 tokens before any work — more than 99% of MCP servers.
Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →
Handshake + tools/list takes ~2,401 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
In the last 30 days: 3 tool(s) removed and 16 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 196 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fing.crank%2Fcrank/fixes
{
"name": "set_portfolio_charter",
"description": "Write a new version of the wallet's portfolio charter (free control-plane write).\n\nCreates a new active version -- the prior version stays in history,\nnever deleted (versioned mandate, not an in-place overwrite).\nrisk_band is one of conservative|balanced|aggressive. banned_tokens\nmerge into AgentWallet.evaluate_trade as an ADDITIONAL deny source\nalongside WalletPolicy.banned_tokens -- an active WalletPolicy always\nwins when it is the stricter rule; a charter can never loosen an\nexisting policy, ",
"inputSchema": {
"type": "object",
"required": [
"wallet_address"
],
"properties": {
"cadence": {
"type": "string",
"default": ""
},
"caller_id": {
"type": "string",
"default": ""
},
"risk_band": {
"type": "string",
"default": ""
},
"objectives": {
"type": "string",
"default": ""
},
"banned_tokens": {
"anyOf": [
{
"type": "array",
"items": {}
},
{
"type": "null"
}
],
"default": null
},
"body_markdown": {
"type": "string",
"default": ""
},
"wallet_address": {
"type": "string"
},
"max_position_pct": {
"title": "Max Position Pct",
"default": null,
"type": "string"
},
"escalation_webhook": {
"type": "string",
"default": ""
},
"target_allocations": {
"anyOf": [
{
"type": "object",
"additionalProperties": true
},
{
"type": "null"
}
],
"default": null
},
"rotate_escalation_secret": {
"type": "boolean",
"default": false
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"openWorldHint": true,
"idempotentHint": false,
"destructiveHint": 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/ing.crank/crank"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/ing.crank/crank"}) over MCP.
place_perp_order ~515 tokensjupiter_swap ~485 tokensset_perp_tpsl ~483 tokensstrategy_hedge_create ~433 tokensstrategy_stoploss_create ~432 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%2Fing.crank%2Fcrank?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fing.crank%2Fcrank?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fing.crank%2Fcrank.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fing.crank%2Fcrank.svg :target: https://glimind.com/server/mcp-registry%2Fing.crank%2Fcrank?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:978f612a3a74201b…, first seen 2026-10-18, included at leaf 23073 of 33,561. Version history · verify what your client received.
Compare: most reliable wallet servers · most reliable data servers · most reliable ml servers · most reliable finance servers · most reliable communication 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-20 15:07 UTC, the Crank MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 5 outages in 90 days, with a median recovery of 6 minutes.
Crank MCP server advertises 196 tools, including approve_proposal, asset_classification, authorize_session_signer, backtest_strategy, bridge_in.
Point your MCP client at this streamable-http endpoint: https://mcp.crank.ing/mcp
Glimind scanned all 196 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.