updated 2026-11-10 04:07 UTC

Pi MCP Adapter

Repository by nicobailon

Token-efficient MCP adapter for Pi coding agent

Protocols & Tool Integration TypeScript Listed MIT

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

OSSF Scorecard 4.4 / 10
Provenance None
Signed commits 90%
Last push 4d ago
Advisories None known
Compare Pi MCP Adapter

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

Pick any agent to compare →
Suggest a correction

In detail: Pi MCP Adapter scores 73.5/100 (Grade B), ranked #293 of 1374 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.4/10; 90% of recent commits are signed; no published advisory affects its latest release (pi-mcp-adapter); last pushed 2026-11-06. Every point is earned from checkable signals — never paid placement. How scoring works →

How Pi MCP Adapter 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 Pi MCP Adapter 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 Signed

    github.com/nicobailon/pi-mcp-adapter, MIT, last pushed 2026-11-06. 90% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Mixed

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

    • Code Review2
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions10
    • Pinned Dependencies1
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 7
    CII-Best-Practices 0
    Code-Review 2
    Contributors 6
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging -1
    Pinned-Dependencies 1
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 10
    Vulnerabilities 0

  3. Published packages Linked, not attested

    • npm pi-mcp-adapter Source link points back to this repo No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: pi-mcp-adapter 7.0.1. No published advisory affects it (OSV, checked 2026-11-10).

Changes to this chain

  • 2026-08-26 OSSF Scorecard: 4.6/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 Pi MCP Adapter’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 Pi MCP Adapter compares in Protocols & Tool Integration

  1. #11 Jevgrep 78.2 +4.7
  2. #12 Chrome DevTools MCP 74.0 +0.5
  3. #13 Pi MCP Adapter 73.5 this agent
  4. #14 CLI-Anything 73.5 ±0
  5. #15 Treg 71.7 −1.8

Bars show each HVTrust score; the tick marks Pi MCP Adapter’s 73.5.

Where the 73.5 comes from

HVTrust dimensions vs the Protocols & Tool Integration average

73.5 / 100 · 100.0% confidence

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

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
10.0 / 25
1.2 below avg 11.2
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.3 below avg 12.1
Transparency50% declared license · 50% OSSF Scorecard
12.2 / 17
0.8 below avg 13.0
Maintenance60% last-push freshness · 40% commit activity
19.3 / 20
4.7 above avg 14.6
AdoptionLog-scaled stars · package downloads
15.2 / 20
4.1 above avg 11.1

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-28
Rank Moved
Rank rose 36 spots (#313 → #277)
2026-10-27
Rank Moved
Rank dropped 41 spots (#272 → #313)
2026-10-15
Rank Moved
Rank dropped 27 spots (#231 → #258)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.4/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.
Compare with another agent
View Protocols & Tool Integration Report missing data
79.5
Activity sub-score · out of 100
#13
In Protocols & Tool Integration

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 4 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
1.6k
Forks
393
Last Push
2026-11-06
4 days ago
Commits (4 wk)
76
Downloads (7d)
441,120
npm
HN mentions (30d)
—
Open Issues
0
Rank Change
▲2
was #295

Analysis

Activity Inputs

79.5 / 100
StarsRepository reach
19.3 / 30
FreshnessLast push recency
24.4 / 25
ActivityRecent commits
23.5 / 25
CommunityFork signal
12.1 / 20

Common questions about Pi MCP Adapter

Pi MCP Adapter 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 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.4/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 4 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?
90% 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-10-01
Provider Removed
Runtime surface shrank — no longer detected: OpenRouter
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 15HVTrust 4Grade 4Scorecard 1Surface 1Delisted 1Listed 1MCP 1Surface 1
2026-10-28
Rank Moved
Rank rose 36 spots (#313 → #277)
2026-10-27
Rank Moved
Rank dropped 41 spots (#272 → #313)
2026-10-15
Rank Moved
Rank dropped 27 spots (#231 → #258)
2026-10-01
Provider Removed
Runtime surface shrank — no longer detected: OpenRouter
2026-10-01
Rank Moved
Rank rose 30 spots (#239 → #209)
2026-09-28
Rank Moved
Rank rose 28 spots (#260 → #232)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → B
2026-09-23
Rank Moved
Rank rose 399 spots (#659 → #260)
2026-09-23
HVTrust Changed
HVTrust up 41.1pts (31.9 → 73.0)
2026-09-22
Newly Listed
First tracked at rank #659
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-20
Rank Moved
Rank dropped 14 spots (#245 → #259)
2026-09-07
Rank Moved
Rank dropped 13 spots (#220 → #233)
2026-09-05
Grade Changed
Trust grade D → B
2026-09-05
Rank Moved
Rank rose 669 spots (#886 → #217)
2026-09-05
HVTrust Changed
HVTrust up 27.3pts (46.5 → 73.8)
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)
GitHub → npm: pi-mcp-adapter

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 73.5 Grade B
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.4 · Raw JSON