gmi-security-mcp
PYPI · GMI-SECURITY-MCP
Triage semgrep findings with GMI Inference, with cost shown before every run.
Available components
Last scanned (14 hours ago)
Scores higher than 57% of PyPI servers
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 29 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to Jayanng/gmi-security-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 8 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability55
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2321 tokens (~154/item across 15 items; 15 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (15)
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain SecurityMalware scan not yet available for this package.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- 20 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- 14 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 13 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- 12 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
- Package version: 0.5.8 → 0.5.11 functional
- Package version: 0.5.8 → 0.5.10 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Analysed pypi/gmi-security-mcp@0.5.11
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | Jayanng/gmi-security-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Jayanng/gmi-security-mcp/.github/workflows/publish.yml@refs/tags/v0.5.11 |
| Rekor log index | 3830413991 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:7d0b3f768f673f8835b4ecc02bc16ebc82064d066a9b44a3b63a4a44c76fd878 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 29 packages
| Packages resolved | 29 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_osv_advisory ~106
Check one lockfile against OSV with the local osv-scanner. Parses the lockfile locally, then runs osv-scanner on it and returns advisories as facts: id, package, installed version, fixed version, severity, summary, and link. Packages with only a version range and no exact version are reported unresolved, never given a verdict. No GMI call is made.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | – | – | – |
| lockfile_path | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
draft_private_disclosure ~262
Draft a private disclosure from a confirmed real finding. Uses the GitHub Security Lab report template, with the ssh-mcp-server host-key draft as the worked example of the format. Refuses when the verdict is not real, or when confidence is below 0.8 without explicit confirmation. When finding_id is given, the finding must be in the store with status confirmed, or triaged with verdict real and confidence at or above 0.8; otherwise the draft is refused and the result says why. Returns the draft as Markdown and writes it only when write_path is given. It is never sent, never opened as a PR, never forked, never pushed, never emailed. sent is always false. Writing the draft to write_path needs --allow-apply on the server command line; without it the call is refused. When --require-scope is set, the write target must sit inside a repo with scope enabled.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm_low_confidence | boolean | – | – |
| db_path | – | – | – |
| finding | object | yes | – |
| finding_id | – | – | – |
| include_fix | boolean | – | – |
| maintainer_contact | – | – | – |
| repo | string | yes | – |
| write_path | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
estimate_cost ~88
Estimate the cost of a run with no API call and no spend. Returns typical and maximum cost in USD, the prompt token estimate, and the per-token pricing used. An unpriced model returns priced false and null costs.
| Name | Type | Req | Description |
|---|---|---|---|
| max_tokens | integer | – | – |
| model | string | yes | – |
| n_findings | integer | – | – |
| text_length_chars | integer | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
explain_cve ~136
Explain a CVE, GHSA, or OSV id from its advisory, with citations. Fetches the advisory from OSV by exact id. When no advisory with that id exists, returns found false and invents nothing. When a model is named, GMI writes one plain-language paragraph from the retrieved advisory only. When no model is named, the explanation is the advisory summary itself.
| Name | Type | Req | Description |
|---|---|---|---|
| advisory_id | string | yes | – |
| max_tokens | integer | – | – |
| package | – | – | – |
| spend_cap_usd | number | – | – |
| stage1_model | – | – | – |
| version | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_finding ~54
Get one stored finding in full: code, evidence, verdict history, pipeline events, verification results, business impact, and matching triage memories.
| Name | Type | Req | Description |
|---|---|---|---|
| db_path | – | – | – |
| finding_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_findings ~101
List stored finding summaries, newest first. Filters: status, check, severity, repo_path. limit defaults to 20 and is capped at 100. cursor pages through results. Summaries only: no code in list output, only in get_finding.
| Name | Type | Req | Description |
|---|---|---|---|
| check | – | – | – |
| cursor | – | – | – |
| db_path | – | – | – |
| limit | integer | – | – |
| repo_path | – | – | – |
| severity | – | – | – |
| status | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_rules ~93
List the custom semgrep rules pack. No GMI call, no spend. Returns each rule with id, name, category, severity, description, and whether it is enabled by default. category filters to one of the 7 known checks. The pack ships in src/gmi_security_mcp/rules/; set GMI_SECURITY_MCP_RULES_DIR when it is elsewhere.
| Name | Type | Req | Description |
|---|---|---|---|
| category | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
mark_confirmed ~72
Mark a stored finding confirmed. reason is required. Only when a verification result with status reproduced exists for the finding. Otherwise the call is refused, and an LLM verdict alone cannot set confirmation.
| Name | Type | Req | Description |
|---|---|---|---|
| db_path | – | – | – |
| finding_id | string | yes | – |
| reason | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
mark_fp ~104
Mark a stored finding false_positive. reason is required. Creates a triage memory with the given scope (global, package, or target, default target). The memory is a hint only: it never auto-rejects a future finding, and the agent must still triage it. Memories are created only by this human call.
| Name | Type | Req | Description |
|---|---|---|---|
| db_path | – | – | – |
| finding_id | string | yes | – |
| reason | string | yes | – |
| scope | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
repo_scan ~325
Scan a repo with semgrep and osv-scanner, then two-stage triage. Returns a JSON report: per-finding verdicts with stage and cost, totals, skipped findings with reasons, the OSV section, and the estimate versus actual cost. A dry run runs the scanners and estimates the cost with no GMI calls. Files over max_file_kb are skipped unless the caller raises the cap. Every triaged finding is stored in the findings store (per-user ~/.gmi-security-mcp/findings.db by default) and the report carries scan_id, with one finding_id per finding. The custom rules pack runs in addition to the default semgrep config, and its findings carry source custom-rule. A clean repo_scan does NOT mean flawless. Writing the report to write_report needs --allow-apply on the server command line; without it the scan still runs but the write is refused.
| Name | Type | Req | Description |
|---|---|---|---|
| db_path | – | – | – |
| dry_run | boolean | – | – |
| include_tests | boolean | – | – |
| max_file_kb | integer | – | – |
| max_files | integer | – | – |
| max_tokens | integer | – | – |
| max_total_kb | integer | – | – |
| repo_path | string | yes | – |
| rules_dir | – | – | – |
| semgrep_config | – | – | – |
| spend_cap_usd | number | – | – |
| stage1_model | string | yes | – |
| stage2_model | string | yes | – |
| threshold | number | – | – |
| write_report | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
scope_disable ~52
Disable scope for one repo. Returns disabled with a warning that tools will now refuse if --require-scope is set, because there is no scope policy for the repo.
| Name | Type | Req | Description |
|---|---|---|---|
| repo_path | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
scope_enable ~83
Enable scope for one repo from a scope file. A scope file alone never activates checks; only this call does. Returns the in-scope and out-of-scope lists and a warning that scope is a destination policy, not authorisation to test, and not an OS sandbox.
| Name | Type | Req | Description |
|---|---|---|---|
| repo_path | string | yes | – |
| scope_file | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
triage_semgrep_finding ~219
Triage one semgrep or scanner finding with GMI Inference. Returns one validated finding as JSON: verdict, severity, confidence, reason, fix, stage used, latency, tokens, cost, and the estimate made before the call. An unparsed reply returns verdict null and unparsed true. It never returns clean. The verdict is stored in the findings store (per-user ~/.gmi-security-mcp/findings.db by default) and the result carries finding_id. An explicit db_path is allowed, with a warning that the caller is responsible for not committing it.
| Name | Type | Req | Description |
|---|---|---|---|
| check | – | – | – |
| code | string | yes | – |
| db_path | – | – | – |
| file | – | – | – |
| finding | string | yes | – |
| line | – | – | – |
| max_tokens | integer | – | – |
| spend_cap_usd | number | – | – |
| stage1_model | – | – | – |
| stage2_model | – | – | – |
| threshold | number | – | – |
| two_stage | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
update_finding ~141
Update a stored finding. reason is required. business_impact changes business impact only, never technical severity, verification, review gates, or patch permissions. status moves one step at a time and is refused when it skips a state, for example new to confirmed without a reproduced verification. Suppressing a critical/high finding with business impact Urgent/High is refused unless force is true with a reason, and is then recorded with that reason and actor.
| Name | Type | Req | Description |
|---|---|---|---|
| business_impact | – | – | – |
| db_path | – | – | – |
| finding_id | string | yes | – |
| force | boolean | – | – |
| reason | – | – | – |
| status | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
verify_finding ~413
Verify one finding with a deterministic oracle, PoV-is-truth. A finding stays a candidate until an oracle reproduces it. GMI only writes the PoC, when poc is null; the local oracle decides. code is the audited code and harness description sent with the finding when a PoC is generated. A generated PoC is returned for review and only runs when run_poc is true AND confirm_generated_poc is true: run_poc alone never runs model-generated code on the host in the same call that generated it. A caller-supplied PoC runs when run_poc is true, with no extra flag, because the caller already reviewed it. A false_positive finding is refused unless regression_check is true, and then the result is labelled regression, not confirmation. Categories without an oracle return skipped with "no oracle for this category". test_command runs a PoC file already in the repo, or the written PoC when it names {poc}, for example pytest {poc} -k host_key. The PoC runs on the host by default, with a warning; pass executor docker for a disposable container when Docker is available. verify_finding never applies a fix; a fix_candidate is run through patch validation and then restored. A fix_candidate needs --allow-apply on the server command line; without it the call is refused.
| Name | Type | Req | Description |
|---|---|---|---|
| code | – | – | – |
| confirm_generated_poc | boolean | – | – |
| db_path | – | – | – |
| executor | string | – | – |
| finding | – | – | – |
| finding_id | – | – | – |
| fix_candidate | – | – | – |
| harness_module | – | – | – |
| max_tokens | integer | – | – |
| poc | – | – | – |
| regression_check | boolean | – | – |
| repo_path | – | – | – |
| run_poc | boolean | – | – |
| spend_cap_usd | number | – | – |
| stage1_model | – | – | – |
| test_command | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the gmi-security-mcp server?
gmi-security-mcp runs locally as a PyPI package, launched with uvx gmi-security-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · gmi-security-mcp
claude mcp add jayanng-gmi-security-mcp -- uvx gmi-security-mcp
What is the gmi-security-mcp server?
gmi-security-mcp is listed in the public MCP registry as io.github.Jayanng/gmi-security-mcp. Triage semgrep findings with GMI Inference, with cost shown before every run. This page covers its PyPI package (gmi-security-mcp).
Is the gmi-security-mcp server safe to use?
gmi-security-mcp scores 65 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the gmi-security-mcp server expose?
gmi-security-mcp exposes 15 tools: triage_semgrep_finding, estimate_cost, repo_scan, check_osv_advisory, explain_cve, and 10 more. Their descriptions and schemas cost roughly 2,249 tokens of context every time the server is loaded.
Is the gmi-security-mcp server still maintained?
gmi-security-mcp is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the gmi-security-mcp server under?
gmi-security-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the gmi-security-mcp server?
VerifyMCP ran 15 checks on gmi-security-mcp, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about gmi-security-mcp: Malware scan. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.