arcade-mcp

MCP Server Framework and Tool Development library for building custom capabilities into agents.

Protocols & Tool Integration Python Grade D Listed MIT
23.4/100
Rank #899 of 1283
Compare arcade-mcp

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

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade D · 1/5 signals
Last push
2026-08-10 · 1d ago
Recent change
Rank +2

Is arcade-mcp safe? arcade-mcp scores 23.4/100 (Grade D), ranked #899 of 1283 tracked open-source AI agent projects, on evidence coverage D (1 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 100% of recent commits are signed; last pushed 2026-08-10. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Protocols & Tool Integration

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-10
Rank Moved
Rank dropped 40 spots (#848 → #888)
2026-08-08
Rank Moved
Rank dropped 330 spots (#481 → #811)
2026-08-06
Newly Listed
First tracked at rank #501
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
62.0
Activity sub-score · out of 100
#47

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage D is separate — it grades how many independent signal types back the score (1 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-08-11 20:32 UTC · Repo last pushed yesterday

Activity & Reach

Stars
1.0k
Forks
106
Last Push
2026-08-10
yesterday
Commits (4 wk)
5?
Downloads (7d)
HN mentions (30d)
Open Issues
11
Rank Change
▼11
was #888

Analysis

HVTrust Dimensions vs Protocols & Tool Integration

23.4 / 100 · 50.0% confidence

arcade-mcp Protocols & Tool Integration average (57 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.0 / 25
3.6 below avg 8.6
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.9 below avg 11.7
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
2.9 below avg 11.4
Maintenance60% last-push freshness · 40% commit activity
13.5 / 20
in line with avg 13.8
AdoptionLog-scaled stars · package downloads
7.2 / 20
3.2 below avg 10.4

Activity Inputs

62.0 / 100
StarsRepository reach
18.0 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
9.7 / 25
CommunityFork signal
9.4 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
Not available
Signed Commits
100%
of last 100 commits verified

Is arcade-mcp safe?

Public trust evidence for arcade-mcp is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does arcade-mcp publish package provenance?
No published build provenance is currently detected for arcade-mcp. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does arcade-mcp have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for arcade-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 arcade-mcp actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does arcade-mcp use?
arcade-mcp ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are arcade-mcp's commits signed?
100% of the last 100 commits to arcade-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
arcade-mcp appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
2 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.
  • shell
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain arcade-mcp?

For maintainers

HVTrust scores arcade-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 2Listed 1
2026-08-10
Rank Moved
Rank dropped 40 spots (#848 → #888)
2026-08-08
Rank Moved
Rank dropped 330 spots (#481 → #811)
2026-08-06
Newly Listed
First tracked at rank #501

Embed Badge Badge guide for maintainers →

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

Other agents in Protocols & Tool Integration

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