io.github.bajoski34/mcp-flutterwave vs io.github.codespar/mcp-stone
io.github.bajoski34/mcp-flutterwave is an MCP server published by bajoski34. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.codespar/mcp-stone is an MCP server published by codespar. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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 |  io.github.bajoski34/mcp-flutterwave |  io.github.codespar/mcp-stone |
|---|---|---|
| Official MCP Registry | Listed Version: 1.2.0 Downloads/month (npm): 1 220 Downloads/week (npm): 294 Forks (GitHub): 0 Stars (GitHub): 4 Not marked · First seen |
Listed Version: 0.2.2 Downloads/month (npm): 296 Downloads/week (npm): 37 Forks (GitHub): 51 Stars (GitHub): 273 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 | io.github.bajoski34/mcp-flutterwave | io.github.codespar/mcp-stone |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 4 (worse) | 273 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 51 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp-flutterwave) | On your machine (@codespar/mcp-stone) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | 1, secrets among them: 1 | 1, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/bajoski34/mcp-flutterwave | github.com/codespar/mcp-dev-latam |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
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
io.github.bajoski34/mcp-flutterwave
MCP Server to interact with Flutterwave APIs.
io.github.codespar/mcp-stone
MCP server for Stone — open banking, payments, Pix, transfers
How to run each
io.github.bajoski34/mcp-flutterwave As a local MCP server: npm package
claude mcp add --env "FLW_SECRET_KEY=<YOUR_FLW_SECRET_KEY>" --transport stdio mcp-flutterwave -- npx -y mcp-flutterwaveRequires: FLW_SECRET_KEY (secret)
io.github.codespar/mcp-stone As a local MCP server: npm package
claude mcp add --env "STONE_CLIENT_SECRET=<YOUR_STONE_CLIENT_SECRET>" --transport stdio mcp-stone -- npx -y @codespar/mcp-stoneRequires: STONE_CLIENT_SECRET (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only io.github.bajoski34/mcp-flutterwave asks for
FLW_SECRET_KEY (secret)
Only io.github.codespar/mcp-stone asks for
STONE_CLIENT_SECRET (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: io.github.bajoski34/mcp-flutterwave · What it can do: io.github.codespar/mcp-stone · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.