DFM · The Fund Management OS vs AiFinPay
DFM · The Fund Management OS is an MCP server published by DFM-Finance. Marketplaces we read that list it: 1 (Official MCP Registry). AiFinPay is an MCP server published by daochild. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-28. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |   DFM · The Fund Management OS |  AiFinPay |
|---|---|---|
| Official MCP Registry | Listed Version: 0.2.2314 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 2.2.2 Downloads/month (npm): 2 538 Downloads/week (npm): 466 Forks (GitHub): 2 Stars (GitHub): 3 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 2.12.2 Downloads/month (npm): 2 538 Downloads/week (npm): 466 Forks (GitHub): 2 Stars (GitHub): 3 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | DFM · The Fund Management OS | AiFinPay |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 0 (worse) | 3 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 2 (better) |
| Last release (differs) | 2026-10-27 (better) | 2026-10-22 (worse) |
| Where it runs (differs) | On your machine (@dfm-fi/agent) | Remote server or your machine |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | 3, secrets among them: 1 | 3, secrets among them: 1 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/dfm-finance/dfm-agent | github.com/aifinpay/sdk |
| Changes in the last 7 days (differs) | 19 | 1 |
| First seen (differs) | 2026-10-20 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 6 h ago |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
DFM · The Fund Management OS
Launch, deposit into, rebalance and redeem onchain funds on Solana mainnet.
AiFinPay
Pay for any HTTP API in stablecoins on Polygon and Solana with one MCP call.
How to run each
DFM · The Fund Management OS As a local MCP server: npm package
claude mcp add --env "DFM_API_KEY=<YOUR_DFM_API_KEY>" --transport stdio dfm-agent -- npx -y @dfm-fi/agentRequires: DFM_API_KEY (secret)
AiFinPay As a remote MCP server
claude mcp add --transport http aifinpay https://mcp.aifinpay.io/mcpRequires: AIFINPAY_AGENT_SECRET (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only AiFinPay has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only DFM · The Fund Management OS asks for
DFM_AGENT_WRITE_ENABLEDDFM_API_KEY (secret)DFM_MCP_CONFIRM_REQUIRED
Only AiFinPay asks for
AIFINPAY_AGENT_SECRET (secret)AIFINPAY_BASE_URLAIFINPAY_MAX_USD
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: DFM · The Fund Management OS · What it can do: AiFinPay · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.