updated 2026-10-17 20:06 UTC

Operant MCP

Repository Website

Turn your AI agent into a hacker by plugging in this MCP

MCP Servers TypeScript Listed MIT

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

OSSF Scorecard 1.8 / 10
Provenance None
Signed commits 0%
Last push 199d ago
Advisories None known
Compare Operant MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Operant MCP scores 31.1/100 (Grade D), ranked #1329 of 1378 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 1.8/10; recent commits are unsigned; no published advisory affects its latest release (operant-mcp); last pushed 2026-04-01. Every point is earned from checkable signals — never paid placement. How scoring works →

How Operant MCP 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 Operant MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Unsigned

    github.com/operantlabs/operant-mcp, MIT, last pushed 2026-04-01. None of the last 100 commits carry a verified signature, so no change traces to a verified identity.

  2. Review and release Weak

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

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

  3. Published packages Not linked

    • npm operant-mcp No source link declared No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: operant-mcp 1.1.0. No published advisory affects it (OSV, checked 2026-10-17).

Changes to this chain

  • 2026-08-28 OSSF Scorecard: 1.8/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 Operant MCP’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 Operant MCP compares in MCP Servers

  1. #766 ByteAsk Embedded MCP 31.5 +0.4
  2. #767 A Mem MCP 31.5 +0.4
  3. #768 Operant MCP 31.1 this agent
  4. #769 Logoloom 30.7 −0.4
  5. #770 MCP Server Taiwan Weather 30.7 −0.4

Bars show each HVTrust score; the tick marks Operant MCP’s 31.1.

Where the 31.1 comes from

HVTrust dimensions vs the MCP Servers average

31.1 / 100 · 100.0% confidence

Operant MCP MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
2.2 / 25
8.3 below avg 10.5
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.7 below avg 13.5
Transparency50% declared license · 50% OSSF Scorecard
10.0 / 17
2.3 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
0 / 20
12.3 below avg 12.3
AdoptionLog-scaled stars · package downloads
6.1 / 20
1.3 below avg 7.4

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-09
Rank Moved
Rank dropped 11 spots (#1301 → #1312)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank rose 30 spots (#1313 → #1283)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 1.8/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 199 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for Operant MCP View MCP Servers Report missing data
12.7
Activity sub-score · out of 100
#768
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-10-17 20:06 UTC · Repo last pushed 199 days ago — may be stale

Rank Trend

2026-09-29 2026-10-17

Activity & Reach

Stars
25
Forks
7
Last Push
2026-04-01
199 days ago
Commits (4 wk)
0
Downloads (7d)
101
npm
HN mentions (30d)
—
Open Issues
1
Rank Change
▼2
was #1327

Analysis

Activity Inputs

12.7 / 100
StarsRepository reach
8.5 / 30
FreshnessLast push recency
0.0 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
4.2 / 20

Common questions about Operant MCP

Public trust evidence for Operant 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 Operant MCP publish package provenance?
No published build provenance is currently detected for Operant 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 Operant MCP have an OpenSSF Scorecard?
Operant MCP has an OpenSSF Scorecard score of 1.8/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 Operant MCP actively maintained?
Stale. The repository has not been pushed to in 199 days. Consider whether the project is still being maintained.
What license does Operant MCP use?
Operant MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Operant MCP's commits signed?
0% of the last 100 commits to Operant 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
Operant 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
low confidence
Unknown
Package source metadata is missing or inconclusive
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 Operant MCP'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

Maintain Operant MCP?

For maintainers

HVTrust scores Operant 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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 21Listed 2HVTrust 2Scorecard 1Delisted 1MCP 1
2026-10-09
Rank Moved
Rank dropped 11 spots (#1301 → #1312)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank rose 30 spots (#1313 → #1283)
2026-09-23
HVTrust Changed
HVTrust up 18.6pts (12.1 → 30.7)
2026-09-22
Newly Listed
First tracked at rank #1313
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-08
Rank Moved
Rank dropped 13 spots (#1244 → #1257)
2026-09-07
Rank Moved
Rank dropped 11 spots (#1233 → #1244)
2026-09-06
Rank Moved
Rank dropped 19 spots (#1214 → #1233)
2026-09-05
Rank Moved
Rank dropped 25 spots (#1189 → #1214)
2026-09-04
Rank Moved
Rank dropped 17 spots (#1172 → #1189)
2026-09-03
Rank Moved
Rank dropped 42 spots (#1130 → #1172)
2026-09-02
Rank Moved
Rank dropped 39 spots (#1091 → #1130)
2026-09-01
Rank Moved
Rank dropped 40 spots (#1051 → #1091)
2026-08-31
Rank Moved
Rank dropped 33 spots (#1018 → #1051)
2026-08-30
Rank Moved
Rank dropped 54 spots (#964 → #1018)
2026-08-29
Rank Moved
Rank dropped 49 spots (#915 → #964)
2026-08-28
Scorecard Added
OSSF Scorecard: 1.8/10
2026-08-28
Rank Moved
Rank rose 236 spots (#1151 → #915)
2026-08-28
HVTrust Changed
HVTrust up 12.7pts (20.0 → 32.7)
2026-08-27
Rank Moved
Rank dropped 22 spots (#1129 → #1151)
2026-08-26
Rank Moved
Rank dropped 55 spots (#1074 → #1129)
2026-08-24
Rank Moved
Rank dropped 17 spots (#1058 → #1075)
2026-08-17
Rank Moved
Rank rose 15 spots (#1064 → #1049)
2026-08-16
Rank Moved
Rank dropped 35 spots (#1029 → #1064)
2026-08-12
Rank Moved
Rank rose 16 spots (#1030 → #1014)
2026-08-10
Rank Moved
Rank dropped 60 spots (#963 → #1023)
2026-08-08
Newly Listed
First tracked at rank #955
GitHub → Website → npm: operant-mcp

Embed Badge Badge guide for maintainers →

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

Other agents in MCP Servers

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.4 · Raw JSON