AINumbers Fintech Intelligence Suite MCP server
online · 100% uptimeco.ainumbers/tools·v0.4.46·2 stars763 MCP tools across 1233 fintech tools: ChainGraph AP2 decisions, execution_hash. Zero PII.
not scanned yet
2 stars
Reviews
Write oneNobody has reviewed AINumbers Fintech Intelligence Suite yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
AINumbers Fintech Intelligence Suite tools
Tool list not cached yet. `describe` through the gateway fetches it live.
How AINumbers Fintech Intelligence Suite compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 75/100
- higher than 45% of 48,255 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 497 ms
- faster than 30% of 30,031 servers
- GitHub stars
- 2
- more than 75% of 28,688 servers
Release history: 16 versions in the registry since 2026-07-26, latest 2026-11-02, typically several a day.
Install AINumbers Fintech Intelligence Suite in Claude Code, Cursor or VS Code
claude mcp add --transport http tools https://mcp.ainumbers.co/mcp
What the publisher says
From the AINumbers Fintech Intelligence Suite repository's README, as published. We do not edit it. Read it on GitHub
AINumbers MCP Apps Server
An agent calling a fintech tool by name has no way to know if the tool actually ran the math it claims to have run. This server closes that gap for the AINumbers.co suite: every tool call is deterministic, zero PII, and served straight from the suite's own single-file HTML, not a paraphrase of it.
An MCP Apps (SEP-1865) server that exposes the AINumbers.co fintech tool suite to any MCP host, including Claude, ChatGPT, M365 Copilot, VS Code, and Cursor.
Quick start
# Claude: Settings -> Connectors -> Add custom connector
https://mcp.ainumbers.co/mcp
# Inspector
npx @modelcontextprotocol/inspector # then Streamable HTTP -> the URL aboveNo auth, no API key, no account. Production runs on Cloudflare Workers (/healthz reports runtime: cloudflare-workers), so there are no cold starts. Cursor and other Open Plugins directories pick this repo up automatically via the root .mcp.json, which declares the same endpoint.
Live endpoint: https://mcp.ainumbers.co/mcp (streamable HTTP) · Docs: ainumbers.co/mcp.html · Registry: co.ainumbers/tools on the Official MCP Registry
Run your own (org-hosted)
Fork this repo and deploy the button above to run the same server inside your own Cloudflare account: no auth to add, no build step at deploy time, the Worker boots straight from the data/ and kernels/ already committed here.
Two edits to wrangler.jsonc before that first deploy will succeed on a fresh account:
- routes points at mcp.ainumbers.co, a zone this fork doesn't own. Rename name and either delete routes (ship on the free workers.dev subdomain) or point it at a zone in your own account.
- queues / workflows feed an internal analytics loop and are guarded in code (if (env.EVENTSQUEUE), if (env.RENEWALWATCH_WORKFLOW)) — the MCP handshake and every tool call work without them. Queues need a Workers Paid plan; drop both blocks to stay free-tier.
Everything else, including the ASSETS binding serving the committed tool data, works unmodified. Full write-up (WAF rate-limit recipe, re-vendor cadence, conformance-attestation offer): ainumbers.co/mcp.html#deploy-your-own.
Tools
Read-only MCP tools — count intentionally not hardcoded here (it drifted stale the last time it was). See data/counts.json for the live figure; never hand-type this number, scripts/surface-parity.mjs and the site repo's count-drift gate both check against it. The flagship widgets below render as interactive widgets, the rest are ChainGraph compute nodes plus a handful of catalog and discovery utility tools: listainumberstools, findtool, findchain, buildworkflowlinks, runchain, verifyexecutionhash, buildchaingraph, emitchaingraphartifact, buildsessionreceipt.
Every tool declares readOnlyHint: true. No account, no auth, zero PII, nothing mutates state.
The flagship widgets
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
AINumbers Fintech Intelligence Suite: common questions
- Is AINumbers Fintech Intelligence Suite MCP server safe?
- Mostly: it is graded B (75/100). Read the AINumbers Fintech Intelligence Suite safety report
- How do I install AINumbers Fintech Intelligence Suite?
- It runs remotely at mcp.ainumbers.co. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does AINumbers Fintech Intelligence Suite need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is AINumbers Fintech Intelligence Suite maintained?
- The last commit was 41 days ago (2026-09-24). The latest release is v0.4.46.
- Is AINumbers Fintech Intelligence Suite up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does AINumbers Fintech Intelligence Suite compare with other MCP servers?
- safety score 75/100 (higher than 45% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 497 ms (faster than 30% of 30,031 servers). Full comparison.