updated 2026-11-10 04:07 UTC

Just MCP Server

Repository

mcp server for just

MCP Servers Rust Listed MIT

Is Just MCP Server safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 3.7 / 10
Provenance None
Signed commits 12%
Last push 118d ago
Compare Just MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Just MCP Server scores 38.0/100 (Grade D), ranked #1244 of 1374 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.7/10; 12% of recent commits are signed; last pushed 2026-07-15. Every point is earned from checkable signals — never paid placement. How scoring works →

How Just MCP Server 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 Just MCP Server 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/PromptExecution/just-mcp, MIT, last pushed 2026-07-15. 12% 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.7/10 (scanned Oct 30, 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 5
    CII-Best-Practices 0
    Code-Review 0
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 0
    Packaging 10
    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 ghcr.io/promptexecution/just-mcp:0.1.5; HVTracker doesn't check that registry's source link yet.

Changes to this chain

  • 2026-08-28 OSSF Scorecard: 3.9/10

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

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

Verify this score yourself

Every build re-issues Just MCP Server’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 Just MCP Server compares in MCP Servers

  1. #717 Power Automate MCP Server by Flow Studio 38.1 +0.1
  2. #718 MCP Power Automate 38.1 +0.1
  3. #719 Just MCP Server 38.0 this agent
  4. #720 XamlMcp 38.0 ±0
  5. #721 Hummingbot MCP 38.0 ±0

Bars show each HVTrust score; the tick marks Just MCP Server’s 38.0.

Where the 38.0 comes from

HVTrust dimensions vs the MCP Servers average

38.0 / 100 · 100.0% confidence

Just MCP Server MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.2 / 25
5.6 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.6 / 17
0.7 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
4.1 / 20
8.1 below avg 12.2
AdoptionLog-scaled stars · package downloads
4.3 / 20
3.3 below avg 7.6

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-19
Rank Moved
Rank dropped 11 spots (#1213 → #1224)
2026-10-13
Activity Went Stale
No commits for 90 days
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.7/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 118 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent
View MCP Servers Report missing data
24.3
Activity sub-score · out of 100
#719
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 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-11-10 04:07 UTC · Repo last pushed 118 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
60
Forks
10
Last Push
2026-07-15
118 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
3
Rank Change
▼1
was #1243

Analysis

Activity Inputs

24.3 / 100
StarsRepository reach
10.7 / 30
FreshnessLast push recency
8.6 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
4.8 / 20

Common questions about Just MCP Server

Public trust evidence for Just MCP Server 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 Just MCP Server publish package provenance?
No published build provenance is currently detected for Just MCP Server. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Just MCP Server have an OpenSSF Scorecard?
Just MCP Server has an OpenSSF Scorecard score of 3.7/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 Just MCP Server actively maintained?
Slowing down. Last push was 118 days ago — keep an eye on whether activity resumes.
What license does Just MCP Server use?
Just MCP Server ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Just MCP Server's commits signed?
12% of the last 100 commits to Just MCP Server 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
Just MCP Server 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 Just MCP Server'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-10-13
Activity Went Stale
No commits for 90 days
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain Just MCP Server?

For maintainers

HVTrust scores Just MCP Server 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 24HVTrust 6Score 1Scorecard 1Delisted 1Listed 1MCP 1Stale 1
2026-10-19
Rank Moved
Rank dropped 11 spots (#1213 → #1224)
2026-10-13
Activity Went Stale
No commits for 90 days
2026-10-09
Rank Moved
Rank dropped 11 spots (#1167 → #1178)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank rose 23 spots (#1155 → #1132)
2026-09-23
HVTrust Changed
HVTrust up 21.2pts (20.5 → 41.7)
2026-09-22
Newly Listed
First tracked at rank #1155
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-18
Rank Moved
Rank rose 173 spots (#1297 → #1124)
2026-09-18
HVTrust Changed
HVTrust up 13.4pts (28.7 → 42.1)
2026-09-17
Rank Moved
Rank dropped 181 spots (#1116 → #1297)
2026-09-17
HVTrust Changed
HVTrust down 13.5pts (42.2 → 28.7)
2026-09-12
Rank Moved
Rank dropped 15 spots (#1103 → #1118)
2026-09-09
Rank Moved
Rank rose 186 spots (#1285 → #1099)
2026-09-09
HVTrust Changed
HVTrust up 13.5pts (29.1 → 42.6)
2026-09-08
Rank Moved
Rank dropped 209 spots (#1076 → #1285)
2026-09-08
HVTrust Changed
HVTrust down 13.6pts (42.7 → 29.1)
2026-09-07
Rank Moved
Rank dropped 31 spots (#1045 → #1076)
2026-09-06
Rank Moved
Rank dropped 15 spots (#1030 → #1045)
2026-09-05
Rank Moved
Rank dropped 42 spots (#988 → #1030)
2026-09-04
Rank Moved
Rank dropped 30 spots (#958 → #988)
2026-09-03
Rank Moved
Rank dropped 55 spots (#903 → #958)
2026-09-02
Rank Moved
Rank dropped 52 spots (#851 → #903)
2026-09-01
Rank Moved
Rank dropped 31 spots (#820 → #851)
2026-08-31
Rank Moved
Rank dropped 34 spots (#786 → #820)
2026-08-30
Rank Moved
Rank dropped 30 spots (#756 → #786)
2026-08-29
Rank Moved
Rank dropped 50 spots (#706 → #756)
2026-08-28
Scorecard Added
OSSF Scorecard: 3.9/10
2026-08-28
Rank Moved
Rank rose 495 spots (#1201 → #706)
2026-08-28
HVTrust Changed
HVTrust up 24.8pts (18.6 → 43.4)
2026-08-27
Rank Moved
Rank dropped 11 spots (#1190 → #1201)
2026-08-26
Rank Moved
Rank dropped 46 spots (#1144 → #1190)
2026-08-24
Rank Moved
Rank dropped 12 spots (#1131 → #1143)
2026-08-16
Rank Moved
Rank dropped 25 spots (#1109 → #1134)
2026-08-14
Rank Moved
Rank dropped 61 spots (#1047 → #1108)
2026-08-14
Activity Score Changed
Activity score down 8pts (44 → 36)
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 38.0 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/just-mcp-server.svg)](https://hvtracker.net/agents/just-mcp-server)
HTML:
<a href="https://hvtracker.net/agents/just-mcp-server"><img src="https://hvtracker.net/badge/just-mcp-server.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