mcp-registry/io.github.rebelartists/fortfi-treasury-mcp · v1.0.0
As of 2026-10-21 07:12 UTC, the Rebelartists Fortfi Treasury MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 4 outages in 90 days, with a median recovery of 10 minutes.
Policy-gated MCP treasury for AI agents — x402 subscribe, 50+ tools, multi-chain.
Claude Code
claude mcp add --transport http rebelartists-fortfi-treasury-mcp-server https://fortfiapp.com/api/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"rebelartists-fortfi-treasury-mcp-server": {
"type": "http",
"url": "https://fortfiapp.com/api/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
133 of 133 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 →
133 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 →
102 parameter(s) across 49 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 →
37 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 →
Loading this server's tool list costs an agent ~23,085 tokens before any work — more than 95% 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 →
Negotiates MCP 2024-11-05. Structured output, tool output schemas and elicitation arrived in 2025-06-18.
Upgrade the MCP SDK and negotiate 2025-06-18 or newer. 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 →
In the last 30 days: 0 tool(s) removed and 4 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. 49 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.rebelartists%2Ffortfi-treasury-mcp/fixes
{
"name": "accept_cosigner_invite",
"description": "Accept a pending co-signer invite. After accepting, you will be able to approve/reject pending actions for that account.",
"inputSchema": {
"type": "object",
"required": [
"inviteId"
],
"properties": {
"inviteId": {
"type": "string",
"description": "Invite id from list_incoming_cosigner_invites"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "add_recipient",
"description": "Add a payout address to the allowlist. Human developer key (frtfi_hu_* + DA): added with 24h cooldown (no Assist passkey). Agent key (frtfi_ag_*): GOVERN — funding-wallet signature required; then approved immediately.",
"inputSchema": {
"type": "object",
"required": [
"address",
"chainId"
],
"properties": {
"address": {
"type": "string",
"description": "Wallet address (0x… or Solana base58)"
},
"chainId": {
"type": "string",
"description": "FortFi chain id (e.g. hyperliquid-mainnet). Omit when fromWalletId is set — network is inferred from that wallet."
},
"nickname": {
"type": "string",
"description": "Optional display name"
},
"challengeId": {
"type": "string",
"description": "Agent GOVERN: challengeId from the first call"
},
"fromWalletId": {
"type": "string",
"description": "Optional source wallet id (list_wallets). Sets allowlist network to that wallet's chain — use for HL sends without passing chainId."
},
"walletSignature": {
"type": "string",
"description": "Agent GOVERN: funding-wallet signature"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "approve_cosigner_action",
"description": "Approve a pending action as co-signer. Use with list_pending_cosigner_approvals.",
"inputSchema": {
"type": "object",
"required": [
"pendingApprovalId"
],
"properties": {
"pendingApprovalId": {
"type": "string"
}
},
"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.rebelartists/fortfi-treasury-mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.rebelartists/fortfi-treasury-mcp"}) over MCP.
propose_hyperliquid_perp_open ~461 tokenscreate_checkout_session ~450 tokensscreen_hyperliquid_markets ~441 tokensget_hyperliquid_cross_section ~439 tokensrank_tokens ~415 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%2Fio.github.rebelartists%2Ffortfi-treasury-mcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.rebelartists%2Ffortfi-treasury-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.rebelartists%2Ffortfi-treasury-mcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.rebelartists%2Ffortfi-treasury-mcp.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.rebelartists%2Ffortfi-treasury-mcp?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:c2fd75b1153dd533…, first seen 2026-10-20, included at leaf 31192 of 38,200. Version history · verify what your client received.
Compare: most reliable security servers · most reliable finance servers · most reliable other servers · most reliable blockchain servers · most reliable payments 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-21 07:12 UTC, the Rebelartists Fortfi Treasury MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 4 outages in 90 days, with a median recovery of 10 minutes.
Rebelartists Fortfi Treasury MCP server advertises 133 tools, including accept_cosigner_invite, add_recipient, approve_cosigner_action, approve_recipient, cancel_governance_change.
Point your MCP client at this streamable-http endpoint: https://fortfiapp.com/api/mcp
Glimind scanned all 133 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.