updated 2026-11-10 04:07 UTC

PageIndex MCP

Repository Website

MCP server for PageIndex. PageIndex is a vectorless reasoning-based RAG system which uses multi-step reasoning and tree search to retrieve information like a human expert would.

MCP Servers TypeScript Listed MIT

Is PageIndex MCP safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 2.7 / 10
Provenance Attested
Signed commits 49%
Last push 7d ago
Advisories None known
Compare PageIndex MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: PageIndex MCP scores 70.3/100 (Grade B), ranked #373 of 1374 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 2.7/10; 49% of recent commits are signed; no published advisory affects its latest release (@pageindex/mcp); last pushed 2026-11-03. Every point is earned from checkable signals — never paid placement. How scoring works →

How PageIndex MCP could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships PageIndex MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/VectifyAI/pageindex-mcp, MIT, last pushed 2026-11-03. 49% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 2.7/10 (scanned Nov 7, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection0
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 0
    CII-Best-Practices 0
    Code-Review 0
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 1
    Packaging 10
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 0
    Signed-Releases 0
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages Linked and attested

    • npm @pageindex/mcp Source link points back to this repo Build provenance attested

  4. What you install today No known advisories

    Latest release checked: @pageindex/mcp 1.9.0. No published advisory affects it (OSV, checked 2026-11-09).

Changes to this chain

  • 2026-09-23 Package provenance attestation detected
  • 2026-08-29 OSSF Scorecard: 3.0/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues PageIndex MCP’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How PageIndex MCP compares in MCP Servers

  1. #219 Mapbox MCP Server 70.3 ±0
  2. #220 Marlinjai Email MCP 70.3 ±0
  3. #221 PageIndex MCP 70.3 this agent
  4. #222 db-mcp (SQLite MCP Server) 70.2 −0.1
  5. #223 MCP Atlassian 70.1 −0.2

Bars show each HVTrust score; the tick marks PageIndex MCP’s 70.3.

Where the 70.3 comes from

HVTrust dimensions vs the MCP Servers average

70.3 / 100 · 100.0% confidence

PageIndex MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
13.3 / 25
2.5 above avg 10.8
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.3 above avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
10.8 / 17
1.5 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
12.5 / 20
in line with avg 12.2
AdoptionLog-scaled stars · package downloads
9.7 / 20
2.1 above avg 7.6

Quick Trust Read

What Would Improve It
Increase the share of verified signed commits for clearer maintainer identity.
Recent Changes
2026-11-09
Rank Moved
Rank rose 24 spots (#394 → #370)
2026-11-03
Rank Moved
Rank rose 41 spots (#425 → #384)
2026-11-03
Activity Score Changed
Activity score up 7pts (48 → 55)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 2.7/10. Tighten the weakest checks to improve public safety evidence.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with another agent
View MCP Servers Report missing data
53.7
Activity sub-score · out of 100
#221
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-11-10 04:07 UTC · Repo last pushed 7 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
412
Forks
52
Last Push
2026-11-03
7 days ago
Commits (4 wk)
2?
Downloads (7d)
356
npm
HN mentions (30d)
—
Open Issues
0
Rank Change
▼3
was #370

Analysis

Activity Inputs

53.7 / 100
StarsRepository reach
15.7 / 30
FreshnessLast push recency
24.0 / 25
ActivityRecent commits
6.0 / 25
CommunityFork signal
8.0 / 20

Common questions about PageIndex MCP

PageIndex MCP has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does PageIndex MCP publish package provenance?
Yes. PageIndex MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does PageIndex MCP have an OpenSSF Scorecard?
PageIndex MCP has an OpenSSF Scorecard score of 2.7/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is PageIndex MCP actively maintained?
Actively maintained. The repository was pushed to within the last 7 day(s).
What license does PageIndex MCP use?
PageIndex MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are PageIndex MCP's commits signed?
49% of the last 100 commits to PageIndex MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
PageIndex MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to PageIndex MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-10-27
Activity Resumed
Activity resumed
2026-10-23
Activity Went Stale
No commits for 90 days
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected

Maintain PageIndex MCP?

For maintainers

HVTrust scores PageIndex MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 27HVTrust 4Score 3Grade 3Scorecard 1Delisted 1Listed 1Provenance 1MCP 1Stale 1Fresh 1
2026-11-09
Rank Moved
Rank rose 24 spots (#394 → #370)
2026-11-03
Rank Moved
Rank rose 41 spots (#425 → #384)
2026-11-03
Activity Score Changed
Activity score up 7pts (48 → 55)
2026-10-31
Rank Moved
Rank dropped 25 spots (#400 → #425)
2026-10-27
Activity Resumed
Activity resumed
2026-10-27
Grade Changed
Trust grade C → B
2026-10-27
Rank Moved
Rank rose 204 spots (#592 → #388)
2026-10-27
HVTrust Changed
HVTrust up 6.2pts (62.9 → 69.1)
2026-10-27
Activity Score Changed
Activity score up 13pts (36 → 49)
2026-10-23
Activity Went Stale
No commits for 90 days
2026-10-23
Rank Moved
Rank dropped 14 spots (#583 → #597)
2026-10-18
Rank Moved
Rank dropped 21 spots (#555 → #576)
2026-10-12
Rank Moved
Rank dropped 12 spots (#525 → #537)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-23
Grade Changed
Trust grade D → B
2026-09-23
Rank Moved
Rank rose 671 spots (#1139 → #468)
2026-09-23
HVTrust Changed
HVTrust up 44.4pts (20.9 → 65.3)
2026-09-22
Newly Listed
First tracked at rank #1139
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-13
Rank Moved
Rank dropped 10 spots (#421 → #431)
2026-09-11
Rank Moved
Rank dropped 16 spots (#401 → #417)
2026-09-08
Rank Moved
Rank dropped 11 spots (#380 → #391)
2026-09-07
Grade Changed
Trust grade D → B
2026-09-07
Rank Moved
Rank rose 609 spots (#989 → #380)
2026-09-07
HVTrust Changed
HVTrust up 21.9pts (44.7 → 66.6)
2026-09-06
Rank Moved
Rank dropped 13 spots (#976 → #989)
2026-09-05
Rank Moved
Rank dropped 48 spots (#928 → #976)
2026-09-04
Rank Moved
Rank dropped 29 spots (#899 → #928)
2026-09-03
Rank Moved
Rank dropped 51 spots (#848 → #899)
2026-09-02
Rank Moved
Rank dropped 46 spots (#802 → #848)
2026-09-01
Rank Moved
Rank dropped 30 spots (#772 → #802)
2026-08-31
Rank Moved
Rank dropped 36 spots (#736 → #772)
2026-08-30
Rank Moved
Rank dropped 26 spots (#710 → #736)
2026-08-29
Scorecard Added
OSSF Scorecard: 3.0/10
2026-08-29
Rank Moved
Rank rose 53 spots (#763 → #710)
2026-08-29
HVTrust Changed
HVTrust up 4.2pts (40.9 → 45.1)
2026-08-28
Rank Moved
Rank dropped 28 spots (#735 → #763)
2026-08-27
Rank Moved
Rank dropped 26 spots (#709 → #735)
2026-08-26
Rank Moved
Rank dropped 97 spots (#612 → #709)
2026-08-24
Rank Moved
Rank dropped 49 spots (#565 → #614)
2026-08-24
Activity Score Changed
Activity score down 10pts (54 → 44)
2026-08-19
Rank Moved
Rank dropped 11 spots (#559 → #570)
2026-08-13
Rank Moved
Rank dropped 12 spots (#543 → #555)
GitHub → Website → npm: @pageindex/mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 70.3 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/pageindex-mcp.svg)](https://hvtracker.net/agents/pageindex-mcp)
HTML:
<a href="https://hvtracker.net/agents/pageindex-mcp"><img src="https://hvtracker.net/badge/pageindex-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON