Agent Reach
Give your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
Is Agent Reach safe? Promising trust profile, but some evidence still deserves review.
Compare Agent Reach
How does it stack up against its Protocols & Tool Integration neighbours?
Pick any agent to compare →In detail: Agent Reach scores 61.2/100 (Grade C), ranked #655 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.8/10; 14% of recent commits are signed; last pushed 2026-10-25. Every point is earned from checkable signals — never paid placement. How scoring works →
What Agent Reach can reach, and who runs it
Checked 2026-10-09, each with its source. PUBLISHER is the company's or project's own statement, which we haven't verified; CHECKED is something we observed ourselves. These facts describe the product. They don't change its score.
What it can reach
- PUBLISHER Its README, which is in Chinese, says it works by having your agent run shell commands, such as pip install, mcporter and twitter.
- PUBLISHER The README warns that scripting platforms such as Twitter or Xiaohongshu with your cookies risks an account ban, and recommends a dedicated secondary account.
Where your data goes
- PUBLISHER Cookies and tokens for logged-in platforms stay on your machine, in ~/.agent-reach/config.yaml with owner-only (600) permissions, and aren't uploaded.
Security practice
- CHECKED The repository has a SECURITY.md; GitHub private vulnerability reporting is off.
How Agent Reach 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.
- Raise the OSSF Scorecard from 4.8 to 9.0lowest checks: CII-Best-Practices 0, Contributors 0, Dependency-Update-Tool 0 +8.8 → 70.0 B · #18 of 63
- Sign every commit14% signed today +4.3 → 65.5 B · #30 of 63
Chain of custody
Scanners check what the code says. This traces who ships Agent Reach and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.
-
Source Partly signed
github.com/Panniantong/Agent-Reach, MIT, last pushed 2026-10-25. 14% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
-
Review and release Mixed
OpenSSF Scorecard rates the repository's practices 4.8/10 (scanned Oct 30, 2026). The checks that decide who can get a change released:
- Code Review3
- Branch Protection3
- Signed Releases0
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies1
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 3CI-Tests 10CII-Best-Practices 0Code-Review 3Contributors 0Dangerous-Workflow 10Dependency-Update-Tool 0Fuzzing 0License 10Maintained 10Packaging -1Pinned-Dependencies 1SAST 0Security-Policy 10Signed-Releases 0Token-Permissions 0Vulnerabilities 10 -
Published packages None
No registry package. Agent Reach is used from its repository, so what you run is whatever you check out: pin a release tag or commit.
Changes to this chain
No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Agent Reach.
Evidence behind this score
Coverage B: 3 of 5 independent evidence types found.
- GitHub repository data
- Package downloads (missing)
- Supply-chain checks
- Public actions (missing)
- Community mentions
Verify this score yourself
Every build re-issues Agent Reach’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 Agent Reach compares in Protocols & Tool Integration
- #38 MCP Client for Ollama 62.3 +1.1
- #39 CodeGraph 61.9 +0.7
- #40 Agent Reach 61.2 this agent
- #41 mcp-gateway-registry 60.8 −0.4
- #42 open-connector 60.4 −0.8
Bars show each HVTrust score; the tick marks Agent Reach’s 61.2.
Where the 61.2 comes from
HVTrust dimensions vs the Protocols & Tool Integration average
61.2 / 100 · 100.0% confidenceAgent Reach Protocols & Tool Integration average (63 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
95.8 / 100Common questions about Agent Reach
Does Agent Reach publish package provenance?
Does Agent Reach have an OpenSSF Scorecard?
Is Agent Reach actively maintained?
What license does Agent Reach use?
Are Agent Reach'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 Agent Reach'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 Agent Reach?
For maintainers
HVTrust scores Agent Reach 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/agent-reach)
<a href="https://hvtracker.net/agents/agent-reach"><img src="https://hvtracker.net/badge/agent-reach.svg" alt="HVTrust"></a>
Other agents in Protocols & Tool Integration
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON