PageIndex MCP

MCP server for PageIndex. PageIndex is a vectorless reasoning-based RAG system which uses multi-step reasoning and tree

MCP Servers TypeScript Grade D Listed MIT
44.9/100
Rank #914 of 1320
Compare PageIndex MCP

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-07-25 · 41d ago
Recent change
Rank +9

Is PageIndex MCP safe? PageIndex MCP scores 44.9/100 (Grade D), ranked #914 of 1320 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 3.0/10; 49% of recent commits are signed; last pushed 2026-07-25. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

Quick Trust Read

What Would Improve It
Increase the share of verified signed commits for clearer maintainer identity.
Recent Changes
2026-09-04
Rank Moved
Rank dropped 15 spots (#899 → #914)
2026-09-03
Rank Moved
Rank dropped 51 spots (#848 → #899)
2026-09-02
Rank Moved
Rank dropped 46 spots (#802 → #848)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.0/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.
Refresh maintenance signals The repo was last pushed 41 days ago. Fresh activity helps separate stable projects from stale ones.
42.6
Activity sub-score · out of 100
#499

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

Signals refreshed 2026-09-04 14:33 UTC · Repo last pushed 41 days ago

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars
383
Forks
47
Last Push
2026-07-25
41 days ago
Commits (4 wk)
0
Downloads (7d)
HN mentions (30d)
Open Issues
0
Rank Change
▼15
was #899

Analysis

HVTrust Dimensions vs MCP Servers

44.9 / 100 · 67.0% confidence

PageIndex MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
13.7 / 25
4.2 above avg 9.5
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.6 above avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
11.1 / 17
0.7 below avg 11.8
Maintenance60% last-push freshness · 40% commit activity
9.3 / 20
2.9 below avg 12.2
AdoptionLog-scaled stars · package downloads
6.2 / 20
in line with avg 6.2

Activity Inputs

42.6 / 100
StarsRepository reach
15.5 / 30
FreshnessLast push recency
19.3 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
7.8 / 20

Supply Chain Trust

Package Provenance
Verified
npm attestation
OSSF Scorecard
3.0 / 10
OpenSSF Scorecard · scanned Aug 29, 2026
Signed Commits
49%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests -1
CII-Best-Practices 0
Code-Review 0
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 5
Packaging 10
Pinned-Dependencies 0
SAST 0
Security-Policy 0
Signed-Releases 0
Token-Permissions 0
Vulnerabilities 0

Is PageIndex MCP safe?

Public trust evidence for PageIndex MCP is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
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 3.0/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?
Slowing down. Last push was 41 days ago — keep an eye on whether activity resumes.
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

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.

Reputation Timeline

Signal history
Rank 14Listed 1Score 1HVTrust 1Scorecard 1
2026-09-04
Rank Moved
Rank dropped 15 spots (#899 → #914)
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)
2026-08-10
Rank Moved
Rank dropped 19 spots (#532 → #551)
2026-08-08
Newly Listed
First tracked at rank #531

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 44.9 Grade D
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.3 · Raw JSON