PAPI: Persistent Adaptive Project Intelligence
NPM · @PAPI-AI/SERVER · 2 COMPONENTS
Adaptive plan/build/review cycles for AI coding assistants, persisted across sessions.
Available components
Last scanned (3 hours ago)
Scores higher than 13% of npm servers
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 33 of 104 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency35
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (Elastic-2.0) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 1 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
- Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: this package installed, but its server did not start, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 0
- Package version: 0.402.157 → 0.402.220 functional
- 4 Nov 26 0
- Package version: 0.402.157 → 0.402.220 functional
- 3 Nov 26 0
- Package version: 0.402.157 → 0.402.220 functional
- 1 Nov 26 0
- Package version: 0.402.157 → 0.402.208 functional
- 30 Oct 26 −43
- Malware scan: pass → unverified ▼ security
- Stability: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess. functional
- Package version: 0.402.157 → 0.402.208 functional
- Package version: 0.402.157 → 0.402.206 functional
- 17 Oct 26 +1
- Package version: 0.7.73 → 0.402.157 functional
- 16 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 15 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Stability: 0.87 → fail ▼ security
- Schema quality: 22614 → 27746 ▼ functional
- Package version: 0.402.35 → 0.402.157 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@papi-ai/server@0.402.220
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 104 packages
| Packages resolved | 104 |
|---|---|
| Stale | 33 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.
How do I install the PAPI: Persistent Adaptive Project Intelligence MCP server?
PAPI: Persistent Adaptive Project Intelligence runs locally as an npm package, launched with npx -y @papi-ai/server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @papi-ai/server
claude mcp add getpapi-papi -- npx -y @papi-ai/server
What is the PAPI: Persistent Adaptive Project Intelligence MCP server?
PAPI: Persistent Adaptive Project Intelligence is an MCP server listed in the public MCP registry as io.github.getpapi/papi. Adaptive plan/build/review cycles for AI coding assistants, persisted across sessions. This page covers its npm package (@papi-ai/server).
Is the PAPI: Persistent Adaptive Project Intelligence MCP server safe to use?
PAPI: Persistent Adaptive Project Intelligence scores 36 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
Is the PAPI: Persistent Adaptive Project Intelligence MCP server still maintained?
PAPI: Persistent Adaptive Project Intelligence is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the PAPI: Persistent Adaptive Project Intelligence MCP server under?
PAPI: Persistent Adaptive Project Intelligence declares the Elastic-2.0 licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.