mcpc has an HVTrust score of 84.3/100 (Grade A), ranked #92 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for mcpc?

mcpc scores 84.3/100 on HVTracker's evidence-weighted HVTrust scale. It has 908 GitHub stars and is categorized under Protocols & Tool Integration.

mcpc

apify/mcpc

A universal CLI client for MCP. mcpc supports persistent sessions, stdio/HTTP, OAuth 2.1, tasks, JSON output for code mode, proxy for AI sandboxes, x402, and more.

Protocols & Tool Integration TypeScript Listed Apache-2.0

Is mcpc safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 5.3 / 10

Provenance Attested

Signed commits 90%

Last push 2d ago

Compare mcpc

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

Pick any agent to compare →

Suggest a correction

In detail: mcpc scores 84.3/100 (Grade A), ranked #92 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 5.3/10; 90% of recent commits are signed; last pushed 2026-09-24. Every point is earned from checkable signals — never paid placement. How scoring works →

How mcpc compares in Protocols & Tool Integration

Bars show each HVTrust score; the tick marks mcpc’s 84.3.

Where the 84.3 comes from

HVTrust dimensions vs the Protocols & Tool Integration average

84.3 / 100 · 100.0% confidence

mcpc Protocols & Tool Integration average (61 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

18.6 / 25

8.1 above avg 10.5

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

6.4 above avg 11.6

Transparency50% declared license · 50% OSSF Scorecard

13.0 / 17

in line with avg 12.9

Maintenance60% last-push freshness · 40% commit activity

18.1 / 20

4.0 above avg 14.1

AdoptionLog-scaled stars · package downloads

11.6 / 20

1.0 above avg 10.6

Quick Trust Read

What Would Improve It

Improve adoption to lift the weakest part of the trust profile.

Recent Changes

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → A

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.3/10. Tighten the weakest checks to improve public safety evidence.

Compare with MCP Inspector Get email alerts for mcpc View Protocols & Tool Integration Report missing data

71.2

Activity sub-score · out of 100

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 A 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

2026-08-11 2026-09-26

Activity & Reach

Stars

908

Forks

Last Push

2026-09-24

2 days ago

Commits (4 wk)

Downloads (7d)

2,480

npm

HN mentions (30d)

—

Open Issues

Rank Change

▲3

was #95

Analysis

Activity Inputs

71.2 / 100

StarsRepository reach

17.8 / 30

FreshnessLast push recency

24.7 / 25

ActivityRecent commits

19.4 / 25

CommunityFork signal

9.1 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

5.3 / 10

OpenSSF Scorecard · scanned Sep 25, 2026

Signed Commits

90%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 6

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 10

Common questions about mcpc

Public supply-chain signals for mcpc are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but mcpc carries less obvious unverified-evidence risk than projects with thin signals.

Does mcpc publish package provenance?

Yes. mcpc's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does mcpc have an OpenSSF Scorecard?

mcpc has an OpenSSF Scorecard score of 5.3/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 mcpc actively maintained?

Actively maintained. The repository was pushed to within the last 2 day(s).

What license does mcpc use?

mcpc ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are mcpc's commits signed?

90% of the last 100 commits to mcpc 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.

Compare mcpc head-to-head

mcpc vs MCP Inspector → mcpc vs MCP Apps → mcpc vs A2A / Agent2Agent Protocol →

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

mcpc appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

low confidence

None detected

No clear third-party provider dependency detected.

Credential signal: API keys or service config markers documented.

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 mcpc'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-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-08-12

Tool Surface Changed

Detected tool/plugin surface changed: marketplace → none

Maintain mcpc?

For maintainers

HVTrust scores mcpc 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

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → A

2026-09-23

Rank Moved

Rank rose 588 spots (#678 → #90)

2026-09-23

HVTrust Changed

HVTrust up 53.1pts (31.3 → 84.4)

2026-09-22

Newly Listed

First tracked at rank #678

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-11

Rank Moved

Rank rose 21 spots (#124 → #103)

2026-09-05

Rank Moved

Rank dropped 28 spots (#91 → #119)

2026-09-02

Rank Moved

Rank rose 13 spots (#98 → #85)

2026-08-29

Scorecard Added

OSSF Scorecard: 4.6/10

2026-08-29

Grade Changed

Trust grade B → A

2026-08-29

Rank Moved

Rank rose 66 spots (#151 → #85)

2026-08-29

HVTrust Changed

HVTrust up 9.7pts (71.7 → 81.4)

2026-08-26

Rank Moved

Rank dropped 14 spots (#124 → #138)

2026-08-13

Rank Moved

Rank dropped 10 spots (#114 → #124)

2026-08-12

Tool Surface Changed

Detected tool/plugin surface changed: marketplace → none

2026-08-10

Newly Listed

First tracked at rank #120

GitHub → npm: @apify/mcpc

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/mcpc.svg)](https://hvtracker.net/agents/mcpc)
            
HTML:
            <a href="https://hvtracker.net/agents/mcpc"><img src="https://hvtracker.net/badge/mcpc.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