FortFi Treasury MCP
warningsfortfiapp.com
Policy-gated MCP treasury for AI agents — x402 subscribe, 50+ tools, multi-chain.
https://fortfiapp.com/api/mcpWebsiteNo authMCP 2024-11-05v1.0.0last checked 3 Sep 2026spoke MCP on 3 of 3 checks (30 days)initialize in 290 msWill my client connect?
Decided from what the probe found at the endpoint, and from what each client's own documentation says it can complete. Every row carries the day that documentation was read.
✓Claude CodeConnects
The endpoint answers an anonymous handshake, so no credential is needed.
claude mcp add --transport http fortfi-treasury-mcp https://fortfiapp.com/api/mcpClaude Code docs · read on 2026-08-30
✓Claude (claude.ai & Desktop)Connects
The endpoint answers an anonymous handshake, so no credential is needed.
Settings → Connectors → Add custom connector, then paste https://fortfiapp.com/api/mcp.
Claude (claude.ai & Desktop) docs · read on 2026-08-30
✓ChatGPTConnects
The endpoint answers an anonymous handshake, so no credential is needed.
Settings → Apps → Advanced settings → Developer mode, then create a connector pointing at https://fortfiapp.com/api/mcp.
ChatGPT docs · read on 2026-08-30
✓CursorConnects
The endpoint answers an anonymous handshake, so no credential is needed.
{
"mcpServers": {
"fortfi-treasury-mcp": {
"url": "https://fortfiapp.com/api/mcp"
}
}
}Cursor docs · read on 2026-08-30
✓VS Code (Copilot)Connects
The endpoint answers an anonymous handshake, so no credential is needed.
{
"servers": {
"fortfi-treasury-mcp": {
"type": "http",
"url": "https://fortfiapp.com/api/mcp"
}
}
}VS Code (Copilot) docs · read on 2026-08-30
How to authenticate
Checked against the endpoint by our probe on 3 Sep 2026. These are the capabilities the server advertises, not a prediction about any particular client.
| Scheme | No auth |
|---|---|
| Protected-resource metadata | ✕Not found Without it a client has to guess where the authorization server lives. |
| Anonymous access | Handshake succeeds; 111 tools listable |
| Credentials demanded in prose | ✕list_activity_report, list_pending_cosigner_approvals, propose_transfer, pay_payment_request_x402, create_vault_credential These tools are listed anonymously and their own descriptions ask for an account or key, but no challenge is issued — so a client has nothing to act on and the refusal arrives as a tool error. |
What the probe found
5 of the 111 tools listed anonymously say in their own descriptions that they need an account or a key (list_activity_report, list_pending_cosigner_approvals, propose_transfer, pay_payment_request_x402, create_vault_credential), but the endpoint issued no WWW-Authenticate challenge. The requirement is stated only in prose, so a call reaches the tool and comes back as a tool error instead of an authorization step.
A cross-origin preflight came back without Access-Control-Allow-Origin, so the endpoint is reachable from native clients only — code running in a web page is stopped by the browser before a request is ever sent.
Tools
Contract history
No contract recorded yet — the server has not answered an anonymous connection.
Run this server? A verified owner can publish snapshots with their own credentials, and the contract history starts here, marked owner-reported.
mcpi-cli publish https://fortfiapp.com/api/mcpGet alerted when this contract changes
Depend on this server? Leave an email. No contract is on record here yet, so alerts can only start once one is published — and alerts are being built; signing up is what tells us to hurry.
Prefer a feed reader? This page's contract changes are also an Atom feed.
Own this server?
Sign in to claim this listing by proving control of its host.
Status badge
Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.
[](https://mcpi.app/servers/fortfi-treasury-mcp)