raptr-agent-finder vs nAIm — API Registry for Agents
raptr-agent-finder is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.
raptr-agent-finder is a plugin bundle for AI coding tools published by Wildhaven Homes LLC. No marketplace we read lists it any more. nAIm — API Registry for Agents is an MCP server published by AIAll-TARS. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  nAIm — API Registry for Agents | |
|---|---|---|
| Community marketplace kody-w/airaptr | Removed on 2026-10-15 Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.1.0 No figure published 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 | raptr-agent-finderno longer listed · | nAIm — API Registry for Agents |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 0 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (airaptr-api.azurewebsites.net/finder/mcp) | Remote server (mcp.naim.janis7ewski.org/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/kody-w/airaptr | github.com/aiall-tars/naim |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-13 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 6 days ago |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of raptr-agent-finder
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
rar-agent-finder io.github.kody-w/rar-agent-finder
Find a free, ready-made AI agent for a task in the public RAPP Agent Registry.
-
Discover public AI agents, reusable recipes, and trusted benchmark evidence by task.
-
AI agent directory — search and compare 120+ agents across 12 categories.
-
Search and fetch 40+ free AI agent prompts. A new one is added every day.
-
Discover open-source AI agents and get source-owned installation instructions through MCP.
-
DartzDabz AI agent tool directory
Read-only search of 2,189 AI agent tools (MCP servers, x402 APIs) with daily automated trust scores.
What each says it does
raptr-agent-finder
Find a free, ready-made AI agent for a task in the open agent registry (RAR) (about 1,700 agents).
nAIm — API Registry for Agents
316 AI APIs searchable by shared failure domain, freshness and agent-sourced ratings.
How to run each
raptr-agent-finder
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
nAIm — API Registry for Agents As a remote MCP server
claude mcp add --transport http naim https://mcp.naim.janis7ewski.org/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only nAIm — API Registry for Agents 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: raptr-agent-finder · What it can do: nAIm — API Registry for Agents · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.