Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

PageIndex MCP

NPM · @PAGEINDEX/MCP · 2 COMPONENTS · SCANNED SEP 20

Reasoning-based RAG system for chatting with long PDFs. Supports local and online files.

Available components

mcpb · pageindex-mcp-1.8.2.mcpb 27 npm · @pageindex/mcp 60
0 this week 60 Trust /100
Trust breakdown (7 categories)

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 Security86
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • 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
  • 34 of 113 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 56 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: this package declared that it provides tools, but our sandbox run could not list them, so the captured schema is incomplete.Unverified
Stability & Change Management87
  • Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage0
  • Tool coverage not yet verified: this package declared that it provides tools, but our sandbox run could not list them.Unverified
Tool Safety0
  • Tool safety not yet verified: this package declared that it provides tools, but our sandbox run could not list them.Unverified
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail

Unverified: 3 categories

Categories scored 0 because our sandbox run of this package 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 →

Install

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

# add to Claude Code
claude mcp add vectifyai-pageindex-mcp -- npx -y @pageindex/mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "vectifyai-pageindex-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@pageindex/mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "vectifyai-pageindex-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@pageindex/mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add vectifyai-pageindex-mcp -- npx -y @pageindex/mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "vectifyai-pageindex-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pageindex/mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add vectifyai-pageindex-mcp --command npx --arg -y --arg @pageindex/mcp
# ~/.hermes/config.yaml
mcp_servers:
  vectifyai-pageindex-mcp:
    command: "npx"
    args: ["-y", "@pageindex/mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "vectifyai-pageindex-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pageindex/mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add vectifyai-pageindex-mcp -t stdio -c npx -a -y @pageindex/mcp
// mcp.json
{
  "mcpServers": {
    "vectifyai-pageindex-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@pageindex/mcp"
      ]
    }
  }
}
Changelog

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.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 17 Sept 26 +1
    • Stability: 0.97 → pass security
  • 16 Sept 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 15 Sept 26 +1
    • Security disclosure: fail → unverified ▼ functional
  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 −4
    • Stability: pass → 0.77 functional
Diagnostics

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 20 Sept 2026 · Analysed npm/@pageindex/mcp@1.8.2

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 2247110593
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:8cb260ff56853aaad1a50955e7a8fd525f60e9d3a93482c3227ecd8ccc8536391421033692228e5efaea6278e0f57a8a6c76f58d7e706ecf5d0f6da68

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 →

Dependencies 113 packages
Packages resolved 113
Stale 34
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools

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.

Common questions

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 60 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 20 September 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.