AgentPhone
Is AgentPhone safe? Promising trust profile, but some evidence still deserves review.
Compare AgentPhone
How does it stack up against its MCP Servers neighbours?
- MCP Proxmox +0.1 higher
- MCP Server for WinDbg Crash Analysis same score
- Google Workspace MCP 0.1 lower
In detail: AgentPhone scores 64.5/100 (Grade C), ranked #553 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 3.7/10; 94% of recent commits are signed; no published advisory affects its latest release (agentphone-mcp); last pushed 2026-11-09. Every point is earned from checkable signals — never paid placement. How scoring works →
How AgentPhone 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.
- Publish build provenance for its packagesnpm publish --provenance from CI +14.7 → 79.2 B · #108 of 778
- Raise the OSSF Scorecard from 3.7 to 9.0lowest checks: CII-Best-Practices 0, Dependency-Update-Tool 0, Fuzzing 0 +11.2 → 75.7 B · #149 of 778
Chain of custody
Scanners check what the code says. This traces who ships AgentPhone 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.
-
Source Signed
github.com/AgentPhone-AI/agentphone-mcp, MIT, last pushed 2026-11-09. 94% of the last 100 commits carry a verified signature, so changes trace to a verified account.
-
Review and release Weak
OpenSSF Scorecard rates the repository's practices 3.7/10 (scanned Nov 4, 2026). The checks that decide who can get a change released:
- Code Review1
- Branch Protection1
- Signed Releasesn/a
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies4
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 1CI-Tests 9CII-Best-Practices 0Code-Review 1Contributors 3Dangerous-Workflow 10Dependency-Update-Tool 0Fuzzing 0License 10Maintained 10Packaging -1Pinned-Dependencies 4SAST 0Security-Policy 0Signed-Releases -1Token-Permissions 0Vulnerabilities 0 -
Published packages Linked, not attested
- npm agentphone-mcp Source link points back to this repo No build attestation
Without a build attestation, nothing proves the published files were built from this repository.
-
What you install today No known advisories
Latest release checked: agentphone-mcp 0.8.0. No published advisory affects it (OSV, checked 2026-11-09).
Changes to this chain
- 2026-08-30 OSSF Scorecard: 3.9/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 AgentPhone’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.
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 AgentPhone compares in MCP Servers
- #313 MCP Proxmox 64.6 +0.1
- #314 MCP Server for WinDbg Crash Analysis 64.5 ±0
- #315 AgentPhone 64.5 this agent
- #316 Google Workspace MCP 64.4 −0.1
- #317 InsForge InsForge 64.3 −0.2
Bars show each HVTrust score; the tick marks AgentPhone’s 64.5.
Where the 64.5 comes from
HVTrust dimensions vs the MCP Servers average
64.5 / 100 · 100.0% confidenceAgentPhone MCP Servers average (778 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C 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 →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
67.3 / 100Common questions about AgentPhone
Does AgentPhone publish package provenance?
Does AgentPhone have an OpenSSF Scorecard?
Is AgentPhone actively maintained?
What license does AgentPhone use?
Are AgentPhone's commits signed?
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
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to AgentPhone'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.
Maintain AgentPhone?
For maintainers
HVTrust scores AgentPhone 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
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/agentphone)
<a href="https://hvtracker.net/agents/agentphone"><img src="https://hvtracker.net/badge/agentphone.svg" alt="HVTrust"></a>
Other agents in MCP Servers
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