evo-talos Devkit vs PAPI: Persistent Adaptive Project Intelligence
evo-talos Devkit is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑23.
evo-talos Devkit is a plugin bundle for AI coding tools published by evolplus. No marketplace we read lists it any more. PAPI: Persistent Adaptive Project Intelligence is an MCP server published by getpapi. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-23. 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 |  PAPI: Persistent Adaptive Project Intelligence | |
|---|---|---|
| Community marketplace evolplus/talos | Removed on 2026-10-23 Version: 0.20.0 Forks (GitHub): 0 Stars (GitHub): 8 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.402.157 Downloads/month (npm): 1 274 Downloads/week (npm): 106 Forks (GitHub): 0 Stars (GitHub): 11 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 | evo-talos Devkitno longer listed · | PAPI: Persistent Adaptive Project Intelligence |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 8 | 11 |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | Not published | 2026-10-15 |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (mcp.getpapi.ai/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 33 | Not published |
| Parts of the bundle (differs) | 86 | 15 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/evolplus/talos | github.com/getpapi/papi |
| Changes in the last 7 days (differs) | 4 | 0 |
| First seen (differs) | 2026-10-18 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Not responding since 2026-10-23 |
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 evo-talos Devkit
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
A structured software development toolkit that helps Claude Code follow senior-engineer workflows. AI DevKit provides phase-based development lifecycle (requirements, design…
-
Verification-first engineering toolkit — 15 skills around a 5-phase spine (Investigate → Design → Implement → Verify → Ship), 8 specialist agents, interactive setup wizard…
-
Evidence-first Claude Code plugin for repeatable, spec-driven development workflows.
-
External tools integration skills for CLI utilities, APIs, and third-party services
-
End-to-end Claude tooling generator for existing codebases. Performs deep codebase analysis (languages, frameworks, conventions, complexity), walks you through an interactive…
-
Endor Labs workflow agents and setup for Claude Code.
What each says it does
evo-talos Devkit
End-to-end SDLC orchestration kit for Claude Code, including role agents, slash commands, skills, rules, and runtime hooks.
PAPI: Persistent Adaptive Project Intelligence
Adaptive plan/build/review cycles for AI coding assistants, persisted across sessions.
How to run each
evo-talos Devkit
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
PAPI: Persistent Adaptive Project Intelligence As a remote MCP server
claude mcp add --transport http papi https://mcp.getpapi.ai/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only PAPI: Persistent Adaptive Project Intelligence 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: evo-talos Devkit · What it can do: PAPI: Persistent Adaptive Project Intelligence · 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.