Ai Cli MCP

MCP server to run Claude, Codex, and Gemini CLI agents in the background from any MCP client.

MCP Servers TypeScript Grade C Listed MIT
64.3/100
Rank #453 of 1328
Compare Ai Cli MCP

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2026-09-07 · 1d ago
Recent change
Rank +8

Is Ai Cli MCP safe? Ai Cli MCP scores 64.3/100 (Grade C), ranked #453 of 1328 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; no OSSF Scorecard result yet; 20% of recent commits are signed; last pushed 2026-09-07. 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
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-09-07
Rank Moved
Rank dropped 23 spots (#424 → #447)
2026-09-06
Rank Moved
Rank rose 27 spots (#451 → #424)
2026-09-05
Rank Moved
Rank dropped 31 spots (#420 → #451)
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
51.1
Activity sub-score · out of 100
#245

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 →

Signals refreshed 2026-09-08 15:33 UTC · Repo last pushed yesterday

Rank Trend

2026-08-11 2026-09-08

Activity & Reach

Stars
25
Forks
9
Last Push
2026-09-07
yesterday
Commits (4 wk)
10
Downloads (7d)
680
npm
HN mentions (30d)
Open Issues
5
Rank Change
▼6
was #447

Analysis

HVTrust Dimensions vs MCP Servers

64.3 / 100 · 100.0% confidence

Ai Cli MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
8.5 / 25
1.4 below avg 9.9
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.6 above avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
3.5 below avg 12.0
Maintenance60% last-push freshness · 40% commit activity
16.1 / 20
3.9 above avg 12.2
AdoptionLog-scaled stars · package downloads
7.2 / 20
in line with avg 6.9

Activity Inputs

51.1 / 100
StarsRepository reach
8.5 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
13.0 / 25
CommunityFork signal
4.7 / 20

Supply Chain Trust

Package Provenance
Verified
npm attestation
OSSF Scorecard
Not available
Signed Commits
20%
of last 100 commits verified

Is Ai Cli MCP safe?

Ai Cli MCP 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 Ai Cli MCP publish package provenance?
Yes. Ai Cli MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Ai Cli MCP have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for Ai Cli MCP. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is Ai Cli MCP actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Ai Cli MCP use?
Ai Cli MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Ai Cli MCP's commits signed?
20% of the last 100 commits to Ai Cli MCP 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
Ai Cli MCP 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

Maintain Ai Cli MCP?

For maintainers

HVTrust scores Ai Cli MCP 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 16Score 2Listed 1HVTrust 1Grade 1
2026-09-07
Rank Moved
Rank dropped 23 spots (#424 → #447)
2026-09-06
Rank Moved
Rank rose 27 spots (#451 → #424)
2026-09-05
Rank Moved
Rank dropped 31 spots (#420 → #451)
2026-09-04
Rank Moved
Rank dropped 12 spots (#408 → #420)
2026-09-03
Grade Changed
Trust grade D → C
2026-09-03
Rank Moved
Rank rose 530 spots (#938 → #408)
2026-09-03
HVTrust Changed
HVTrust up 19.7pts (41.8 → 61.5)
2026-09-02
Rank Moved
Rank dropped 56 spots (#882 → #938)
2026-09-01
Rank Moved
Rank dropped 33 spots (#849 → #882)
2026-08-31
Rank Moved
Rank dropped 27 spots (#822 → #849)
2026-08-30
Rank Moved
Rank dropped 31 spots (#791 → #822)
2026-08-29
Rank Moved
Rank dropped 48 spots (#743 → #791)
2026-08-28
Rank Moved
Rank rose 24 spots (#767 → #743)
2026-08-28
Activity Score Changed
Activity score up 11pts (38 → 50)
2026-08-27
Rank Moved
Rank dropped 23 spots (#744 → #767)
2026-08-26
Rank Moved
Rank dropped 76 spots (#668 → #744)
2026-08-20
Rank Moved
Rank dropped 30 spots (#635 → #665)
2026-08-20
Activity Score Changed
Activity score down 9pts (43 → 34)
2026-08-16
Rank Moved
Rank dropped 11 spots (#618 → #629)
2026-08-10
Rank Moved
Rank dropped 21 spots (#587 → #608)
2026-08-08
Newly Listed
First tracked at rank #587

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 64.3 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/ai-cli-mcp.svg)](https://hvtracker.net/agents/ai-cli-mcp)
HTML:
<a href="https://hvtracker.net/agents/ai-cli-mcp"><img src="https://hvtracker.net/badge/ai-cli-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON