Vaaya vs Reclaim Protocol Builder
Vaaya is an MCP server published by vaaya.ai. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). Reclaim Protocol Builder is an MCP server published by reclaimprotocol. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-11. 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 |   Vaaya |  Reclaim Protocol Builder |
|---|---|---|
| Official MCP Registry | Listed Version: 0.6.8 Downloads/month (npm): 421 Downloads/week (npm): 94 Forks (GitHub): 8 Stars (GitHub): 44 Not marked · First seen |
Listed Version: 0.1.46 No figure published Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.1.45 Downloads/month (npm): 2 243 Downloads/week (npm): 1 516 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 | Vaaya | Reclaim Protocol Builder |
|---|---|---|
| Marketplaces that list it | 2 | 2 |
| Stars (GitHub) (differs) | 44 | No figure on GitHub |
| Forks (GitHub) (differs) | 8 | No figure on GitHub |
| Last release (differs) | Not published | 2026-11-10 |
| Where it runs (differs) | Remote server (vaaya.ai/mcp) | On your machine (@reclaimprotocol/agent) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 1 | Not published |
| Parts of the bundle (differs) | 4 | Not a bundle |
| Licence | MIT | MIT |
| Repository (differs) | github.com/vaaya-ai/vaaya-mcp | github.com/reclaimprotocol/developer-tools |
| Changes in the last 7 days (differs) | 0 | 6 |
| First seen (differs) | 2026-10-11 | 2026-10-12 |
| Endpoint at the last check (differs) | Status out of date: last check 43 h ago returned HTTP 401 | no remote endpoint we check |
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
Vaaya
Paid APIs and tokenized shares for agents. Prepaid funding, including authorized Instinct checkout.
Reclaim Protocol Builder
Integrate source-account verification into products. Find, build, test, and maintain providers.
How to run each
Vaaya As a remote MCP server
claude mcp add --transport http vaaya https://vaaya.ai/mcpReclaim Protocol Builder As a local MCP server: npm package
claude mcp add --transport stdio builder -- npx -y @reclaimprotocol/agentCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Vaaya 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
Neither one's marketplaces publish the settings it asks for.
What it can do: Vaaya · What it can do: Reclaim Protocol Builder · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. 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.