updated 2026-11-11 00:08 UTC

MonkeyMCP

Repository

The MCP the world needs

MCP Servers Jupyter Notebook Listed MIT

Is MonkeyMCP safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 3.4 / 10
Provenance None
Signed commits 28%
Last push 43d ago
Compare MonkeyMCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: MonkeyMCP scores 48.3/100 (Grade D), ranked #1062 of 1387 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 3.4/10; 28% of recent commits are signed; last pushed 2026-09-29. Every point is earned from checkable signals — never paid placement. How scoring works →

How MonkeyMCP 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.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships MonkeyMCP 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.

  1. Source Partly signed

    github.com/jamesmontemagno/MonkeyMCP, MIT, last pushed 2026-09-29. 28% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 3.4/10 (scanned Nov 7, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 2
    CII-Best-Practices 0
    Code-Review 0
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 1
    Packaging -1
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 10

  3. Published packages None

    Distributed as the container image docker.io/jamesmontemagno/monkeymcp:2.0.3; HVTracker doesn't check that registry's source link yet.

Changes to this chain

  • 2026-08-31 OSSF Scorecard: 3.4/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues MonkeyMCP’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.

Signed credential (JSON) How to verify

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 MonkeyMCP compares in MCP Servers

  1. #596 OSS Snowflake MCP Server 48.5 +0.2
  2. #597 Weather MCP Server 48.5 +0.2
  3. #598 MonkeyMCP 48.3 this agent
  4. #599 Nouz 48.3 ±0
  5. #600 Jotform MCP Server 48.2 −0.1

Bars show each HVTrust score; the tick marks MonkeyMCP’s 48.3.

Where the 48.3 comes from

HVTrust dimensions vs the MCP Servers average

48.3 / 100 · 100.0% confidence

MonkeyMCP MCP Servers average (779 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.6 / 25
5.2 below avg 10.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.9 below avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
11.4 / 17
0.9 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
9.1 / 20
3.2 below avg 12.3
AdoptionLog-scaled stars · package downloads
9.4 / 20
1.8 above avg 7.6

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-11-08
Rank Moved
Rank dropped 11 spots (#1046 → #1057)
2026-10-29
Grade Changed
Trust grade C → D
2026-10-29
Rank Moved
Rank dropped 49 spots (#978 → #1027)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.4/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Refresh maintenance signals The repo was last pushed 43 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent
View MCP Servers Report missing data
40.3
Activity sub-score · out of 100
#598
In MCP Servers

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 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-11-11 00:08 UTC · Repo last pushed 43 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
125
Forks
67
Last Push
2026-09-29
43 days ago
Commits (4 wk)
0
Downloads (7d)
1,787
docker
HN mentions (30d)
—
Open Issues
1
Rank Change
=
was #1062

Analysis

Activity Inputs

40.3 / 100
StarsRepository reach
12.6 / 30
FreshnessLast push recency
19.0 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
8.5 / 20

Common questions about MonkeyMCP

Public trust evidence for MonkeyMCP 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 MonkeyMCP publish package provenance?
No published build provenance is currently detected for MonkeyMCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does MonkeyMCP have an OpenSSF Scorecard?
MonkeyMCP has an OpenSSF Scorecard score of 3.4/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 MonkeyMCP actively maintained?
Slowing down. Last push was 43 days ago — keep an eye on whether activity resumes.
What license does MonkeyMCP use?
MonkeyMCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are MonkeyMCP's commits signed?
27% of the last 100 commits to MonkeyMCP 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
MonkeyMCP 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
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
How this surface has changed

Detected changes to MonkeyMCP'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-29
Activity Resumed
Activity resumed
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain MonkeyMCP?

For maintainers

HVTrust scores MonkeyMCP 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
Rank 20HVTrust 8Score 2Scorecard 1Delisted 1Listed 1MCP 1Fresh 1Grade 1
2026-11-08
Rank Moved
Rank dropped 11 spots (#1046 → #1057)
2026-10-29
Grade Changed
Trust grade C → D
2026-10-29
Rank Moved
Rank dropped 49 spots (#978 → #1027)
2026-10-29
Activity Score Changed
Activity score down 6pts (48 → 42)
2026-10-12
Rank Moved
Rank dropped 11 spots (#909 → #920)
2026-10-09
Rank Moved
Rank dropped 15 spots (#880 → #895)
2026-10-07
Rank Moved
Rank rose 28 spots (#900 → #872)
2026-09-30
Rank Moved
Rank dropped 11 spots (#878 → #889)
2026-09-29
Activity Resumed
Activity resumed
2026-09-29
Activity Score Changed
Activity score up 31pts (21 → 52)
2026-09-25
Rank Moved
Rank rose 64 spots (#1246 → #1182)
2026-09-25
HVTrust Changed
HVTrust up 4.3pts (34.8 → 39.1)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank rose 11 spots (#1255 → #1244)
2026-09-23
HVTrust Changed
HVTrust up 19.5pts (15.3 → 34.8)
2026-09-22
Newly Listed
First tracked at rank #1255
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-20
Rank Moved
Rank dropped 68 spots (#1243 → #1311)
2026-09-20
HVTrust Changed
HVTrust down 10.9pts (34.8 → 23.9)
2026-09-08
Rank Moved
Rank dropped 13 spots (#1212 → #1225)
2026-09-07
Rank Moved
Rank dropped 16 spots (#1196 → #1212)
2026-09-06
Rank Moved
Rank rose 86 spots (#1282 → #1196)
2026-09-06
HVTrust Changed
HVTrust up 10.9pts (23.9 → 34.8)
2026-09-05
Rank Moved
Rank dropped 133 spots (#1149 → #1282)
2026-09-05
HVTrust Changed
HVTrust down 10.9pts (34.8 → 23.9)
2026-09-04
Rank Moved
Rank dropped 12 spots (#1137 → #1149)
2026-09-03
Rank Moved
Rank rose 85 spots (#1222 → #1137)
2026-09-03
HVTrust Changed
HVTrust up 10.9pts (23.9 → 34.8)
2026-09-02
Rank Moved
Rank dropped 177 spots (#1045 → #1222)
2026-09-02
HVTrust Changed
HVTrust down 10.9pts (34.8 → 23.9)
2026-09-01
Rank Moved
Rank dropped 37 spots (#1008 → #1045)
2026-08-31
Scorecard Added
OSSF Scorecard: 3.4/10
2026-08-31
Rank Moved
Rank rose 293 spots (#1301 → #1008)
2026-08-31
HVTrust Changed
HVTrust up 20.0pts (14.8 → 34.8)
2026-08-26
Rank Moved
Rank dropped 17 spots (#1270 → #1287)
2026-08-16
Rank Moved
Rank dropped 26 spots (#1247 → #1273)
GitHub →

Embed Badge Badge guide for maintainers →

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

Other agents in MCP Servers

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