Pi MCP Adapter

Token-efficient MCP adapter for Pi coding agent

Protocols & Tool Integration TypeScript Grade D Listed MIT
46.5/100
Rank #886 of 1320
Compare Pi MCP Adapter

How does it stack up against its Protocols & Tool Integration neighbours?

Pick any agent to compare →

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-09-04 · 0d ago
Recent change
Rank +5

Is Pi MCP Adapter safe? Pi MCP Adapter scores 46.5/100 (Grade D), ranked #886 of 1320 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.6/10; 85% of recent commits are signed; last pushed 2026-09-04. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Protocols & Tool Integration

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-04
Rank Moved
Rank dropped 31 spots (#855 → #886)
2026-09-03
Tool Surface Changed
Detected tool/plugin surface changed: extension-based → none
2026-09-03
Grade Changed
Trust grade B → D
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.6/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
80.5
Activity sub-score · out of 100
#49

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 23:32 UTC · Repo last pushed today

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars
1.4k
Forks
317
Last Push
2026-09-04
today
Commits (4 wk)
145
Downloads (7d)
HN mentions (30d)
Open Issues
2
Rank Change
▼31
was #855

Analysis

HVTrust Dimensions vs Protocols & Tool Integration

46.5 / 100 · 67.0% confidence

Pi MCP Adapter Protocols & Tool Integration average (61 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
10.0 / 25
in line with avg 10.4
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.8 below avg 11.6
Transparency50% declared license · 50% OSSF Scorecard
12.4 / 17
in line with avg 12.7
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
5.7 above avg 14.3
AdoptionLog-scaled stars · package downloads
7.6 / 20
2.4 below avg 10.0

Activity Inputs

80.5 / 100
StarsRepository reach
18.9 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
11.6 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
4.6 / 10
OpenSSF Scorecard · scanned Sep 1, 2026
Signed Commits
85%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests 10
CII-Best-Practices 0
Code-Review 2
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 10
Packaging -1
Pinned-Dependencies 2
SAST 0
Security-Policy 0
Signed-Releases -1
Token-Permissions 10
Vulnerabilities 0

Is Pi MCP Adapter safe?

Public trust evidence for Pi MCP Adapter 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 Pi MCP Adapter publish package provenance?
No published build provenance is currently detected for Pi MCP Adapter. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Pi MCP Adapter have an OpenSSF Scorecard?
Pi MCP Adapter has an OpenSSF Scorecard score of 4.6/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 Pi MCP Adapter actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Pi MCP Adapter use?
Pi MCP Adapter ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Pi MCP Adapter's commits signed?
85% of the last 100 commits to Pi MCP Adapter 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
Pi MCP Adapter 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 Pi MCP Adapter'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-09-03
Tool Surface Changed
Detected tool/plugin surface changed: extension-based → none

Maintain Pi MCP Adapter?

For maintainers

HVTrust scores Pi MCP Adapter 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 6HVTrust 2Grade 2Listed 1Scorecard 1Surface 1
2026-09-04
Rank Moved
Rank dropped 31 spots (#855 → #886)
2026-09-03
Tool Surface Changed
Detected tool/plugin surface changed: extension-based → none
2026-09-03
Grade Changed
Trust grade B → D
2026-09-03
Rank Moved
Rank dropped 675 spots (#180 → #855)
2026-09-03
HVTrust Changed
HVTrust down 25.2pts (71.7 → 46.5)
2026-08-31
Rank Moved
Rank dropped 21 spots (#150 → #171)
2026-08-26
Scorecard Added
OSSF Scorecard: 4.6/10
2026-08-26
Grade Changed
Trust grade D → B
2026-08-26
Rank Moved
Rank rose 438 spots (#581 → #143)
2026-08-26
HVTrust Changed
HVTrust up 28.5pts (43.1 → 71.6)
2026-08-24
Rank Moved
Rank dropped 10 spots (#569 → #579)
2026-08-22
Rank Moved
Rank rose 10 spots (#583 → #573)
2026-08-10
Newly Listed
First tracked at rank #566

Embed Badge Badge guide for maintainers →

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

Other agents in Protocols & Tool Integration

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