PageIndex MCP
NPM · @PAGEINDEX/MCP · 2 COMPONENTS
Reasoning-based RAG system for chatting with long PDFs. Supports local and online files.
Available components
Last scanned (1 hour ago)
Scores higher than 22% of npm servers
Category Documents and Files
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 Security69
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- Install-script check failed: the install command fetches or executes arbitrary code (inline_eval). An install hook runs on every machine, in CI, and on transitive installs, whether or not you ever run the server. View diagnostics → Fail
- 32 of 110 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to VectifyAI/pageindex-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
- Schema quality not yet verified: our sandbox run could not list this package's tools (it declared tools, or its tool listing failed outright), so the captured schema is incomplete.Unverified
Stability & Change Management0
- Stability not yet verified: one of the two schema captures we compare could not list the server's tools (the server declared tools, or its tool listing failed outright). Comparing them would report every tool as removed, or find nothing to compare at all.Unverified
Tool Coverage0
- Tool coverage not yet verified: our sandbox run could not list this package's tools (it declared tools, or its tool listing failed outright).Unverified
Tool Safety0
- Tool safety not yet verified: our sandbox run could not list this package's tools (it declared tools, or its tool listing failed outright).Unverified
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Unverified: 4 categories
Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 4 Nov 26 +6
- Known CVEs: unverified → fail ▼ security
- Dependency health: unverified → 0.88 ▲ functional
- 3 Nov 26 −6
- Known CVEs: fail → unverified ▼ security
- Dependency health: 0.88 → unverified ▼ functional
- Package version: 1.8.2 → 1.9.0 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 15 Oct 26 +3
- Tool safety: Tool safety not yet verified: our sandbox run could not list this package's tools (it declared tools, or its tool listing failed outright). security
- Stability: Stability not yet verified: one of the two schema captures we compare could not list the server's tools (the server declared tools, or its tool listing failed outright). Comparing them would report every tool as removed, or find nothing to compare at all. security
- MCP protocol: unverified → fail ▼ functional
- Schema quality: Schema quality not yet verified: our sandbox run could not list this package's tools (it declared tools, or its tool listing failed outright), so the captured schema is incomplete. functional
- Tool coverage: Tool coverage not yet verified: our sandbox run could not list this package's tools (it declared tools, or its tool listing failed outright). functional
- 12 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 11 Oct 26 −3
- Tool safety: Tool safety not yet verified: this package could not be installed in a clean environment, so we have no tool text to scan. security
- Stability: Stability not yet verified: this package could not be installed in a clean environment, so we have no schema to compare. security
- Capabilities: fail → unverified ▼ functional
- Security disclosure: fail → unverified ▼ functional
- Schema quality: Schema quality not yet verified: this package could not be installed in a clean environment, so we have no schema to assess. functional
- Tool coverage: Tool coverage not yet verified: this package could not be installed in a clean environment, so we have no tool definitions to assess. functional
- 2 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 1 Oct 26 48
- Security disclosure: fail → unverified ▼ 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/@pageindex/mcp@1.9.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | VectifyAI/pageindex-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/VectifyAI/pageindex-mcp/.github/workflows/release.yml@refs/heads/master |
| Rekor log index | 3657514856 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:dead3ecbe77fe34ffdf9ce696fa6be16e6480c9fab4ad9bd645887d9484e40a56f4b21ed0ff479d0f419bed917c9f87508969a43a677c564786096b4c |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| postinstall | dangerous | node -e "try { require('fs').existsSync('.git') && require('simple-git-hooks')() } catch(e) {}" |
Background: Why install scripts are a supply-chain risk →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 110 packages
| Packages resolved | 110 |
|---|---|
| Stale | 32 |
| 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 →
The sandbox run completed and this package exposed no tools.
How do I install the PageIndex MCP server?
PageIndex MCP runs locally as an npm package, launched with npx -y @pageindex/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pageindex/mcp
claude mcp add vectifyai-pageindex-mcp -- npx -y @pageindex/mcp
What is the PageIndex MCP server?
PageIndex MCP is listed in the public MCP registry as io.github.VectifyAI/pageindex-mcp. Reasoning-based RAG system for chatting with long PDFs. Supports local and online files. This page covers its npm package (@pageindex/mcp).
Is the PageIndex MCP server safe to use?
PageIndex MCP scores 43 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares an install script we flagged as high risk. Its build provenance is signed and verified. 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.
What tools does the PageIndex MCP server expose?
PageIndex MCP exposes no tools. We connected to it and read its tool list, and it was empty, so it offers an MCP client nothing to call.
Is the PageIndex MCP server still maintained?
PageIndex MCP 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 PageIndex MCP server under?
PageIndex MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.