ARC-1

MCP Servers TypeScript Grade C Listed MIT
57.6/100
Rank #531 of 1320
Compare ARC-1

Promising trust profile, but some evidence still deserves review.

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 +14

Is ARC-1 safe? ARC-1 scores 57.6/100 (Grade C), ranked #531 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 7.0/10; 100% 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 MCP Servers

Quick Trust Read

What Would Improve It
Expose more independent signals, such as package metadata, provenance, or public usage evidence.
Recent Changes
2026-09-04
Rank Moved
Rank dropped 22 spots (#509 → #531)
2026-09-03
Rank Moved
Rank dropped 22 spots (#487 → #509)
2026-09-02
Grade Changed
Trust grade A → C
Maintainer Checklist
Keep signals current Trust posture is already in a healthy range. The main job is to keep provenance, maintenance, and public evidence fresh.
67.8
Activity sub-score · out of 100
#247

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 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
177
Forks
54
Last Push
2026-09-04
today
Commits (4 wk)
49
Downloads (7d)
HN mentions (30d)
Open Issues
1
Rank Change
▼22
was #509

Analysis

HVTrust Dimensions vs MCP Servers

57.6 / 100 · 67.0% confidence

ARC-1 MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
21.2 / 25
11.6 above avg 9.6
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.6 above avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
14.4 / 17
2.6 above avg 11.8
Maintenance60% last-push freshness · 40% commit activity
18.8 / 20
6.6 above avg 12.2
AdoptionLog-scaled stars · package downloads
5.4 / 20
0.9 below avg 6.3

Activity Inputs

67.8 / 100
StarsRepository reach
13.5 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
21.2 / 25
CommunityFork signal
8.1 / 20

Supply Chain Trust

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

Is ARC-1 safe?

ARC-1 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 ARC-1 publish package provenance?
Yes. ARC-1's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does ARC-1 have an OpenSSF Scorecard?
ARC-1 has an OpenSSF Scorecard score of 7.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 ARC-1 actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does ARC-1 use?
ARC-1 ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are ARC-1's commits signed?
100% of the last 100 commits to ARC-1 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
ARC-1 appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
medium confidence
1 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration 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 ARC-1'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-08-12
Tool Surface Changed
Detected tool/plugin surface changed: marketplace → declared

Maintain ARC-1?

For maintainers

HVTrust scores ARC-1 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 7HVTrust 4Grade 4Listed 1Surface 1Scorecard 1
2026-09-04
Rank Moved
Rank dropped 22 spots (#509 → #531)
2026-09-03
Rank Moved
Rank dropped 22 spots (#487 → #509)
2026-09-02
Grade Changed
Trust grade A → C
2026-09-02
Rank Moved
Rank dropped 455 spots (#32 → #487)
2026-09-02
HVTrust Changed
HVTrust down 29.6pts (87.2 → 57.6)
2026-08-31
Grade Changed
Trust grade C → A
2026-08-31
Rank Moved
Rank rose 406 spots (#439 → #33)
2026-08-31
HVTrust Changed
HVTrust up 29.9pts (57.3 → 87.2)
2026-08-30
Grade Changed
Trust grade A → C
2026-08-30
Rank Moved
Rank dropped 404 spots (#35 → #439)
2026-08-30
HVTrust Changed
HVTrust down 29.5pts (86.8 → 57.3)
2026-08-29
Scorecard Added
OSSF Scorecard: 7.0/10
2026-08-29
Grade Changed
Trust grade B → A
2026-08-29
Rank Moved
Rank rose 102 spots (#137 → #35)
2026-08-29
HVTrust Changed
HVTrust up 13.9pts (72.9 → 86.8)
2026-08-26
Rank Moved
Rank dropped 18 spots (#108 → #126)
2026-08-12
Tool Surface Changed
Detected tool/plugin surface changed: marketplace → declared
2026-08-08
Newly Listed
First tracked at rank #98

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 57.6 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/arc-1.svg)](https://hvtracker.net/agents/arc-1)
HTML:
<a href="https://hvtracker.net/agents/arc-1"><img src="https://hvtracker.net/badge/arc-1.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