Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

Sheriff

OCI · GHCR.IO/RYANSMITH4/SHERIFF-MCP:1.0.2 · SCANNED AUG 3

MCP server for fixing static analysis issues from SARIF reports with AI agents

Available components

oci · ghcr.io/ryansmith4/sheriff-mcp:1.0.2 33
−5 this week 33 Trust /100
Trust breakdown (6 categories)

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 →

Supply Chain Security0
  • Malware scan not yet available for this package.Unverified
  • CVE data not yet available for this package.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency-health data not yet available.Unverified
Provenance & Transparency39
Schema Quality & AI Usability54
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 346 tokens (~346/item across 1 items; 1 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 Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

oci · ghcr.io/ryansmith4/sheriff-mcp:1.0.2

# add to Claude Code
claude mcp add ryansmith4-sheriff-mcp -- docker run --rm -i ghcr.io/ryansmith4/sheriff-mcp:1.0.2
# add to Codex CLI
codex mcp add ryansmith4-sheriff-mcp -- docker run --rm -i ghcr.io/ryansmith4/sheriff-mcp:1.0.2
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ryansmith4-sheriff-mcp": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/ryansmith4/sheriff-mcp:1.0.2"
      ],
      "enabled": true
    }
  }
}
# ~/.hermes/config.yaml
mcp_servers:
  ryansmith4-sheriff-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/ryansmith4/sheriff-mcp:1.0.2"]
// mcp.json
{
  "mcpServers": {
    "ryansmith4-sheriff-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/ryansmith4/sheriff-mcp:1.0.2"
      ]
    }
  }
}
Changelog

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.

  • 2 Aug 26 +3
    • Stability: unverified → 0.20 ▲ functional
  • 31 Jul 26 −8
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 +29
    • Tool coverage: unverified → 100 ▲ functional
    • First check of Schema quality: fail functional
    • First check of Tool coverage: 100 functional
    • First check of Schema quality: good functional
    • First check of Schema quality: fail functional
  • 26 Jul 26 9

    First indexed and scored.

    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

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 3 Aug 2026 · Analysed oci/ghcr.io/ryansmith4/sheriff-mcp:1.0.2

Provenance none

Ecosystem: oci · Outcome: none

Reason: no_attestation

MCP tools — 1 exposed · ~346 tokens

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.

Tool Tokens
sheriff ~346

AI work queue manager for static analysis issues. Actions: - load: Load SARIF file(s). Args: target (path) - next: Get next batch of issues (default limit: 25). Args: scope (optional), fmt (default/checklist), limit (optional, default 25) - done: Mark issues as fixed/skipped. Args: fps (fingerprints), status (fixed/skip) - progress: Get session progress. Args: scope (optional) - reopen: Reopen issues marked as fixed/skipped. Args: fps (fingerprints) - summary: Get breakdown by rule/severity/file. No args. - export: Export remaining issues to file. Args: scope (optional), path (optional), format (json/list) Scope filter: {rule: "RuleId", severity: "High/Moderate/Low", file: "glob pattern"}

NameTypeReqDescription
actionstringyesThe action to perform
fmtstring—Output format (for 'next' action)
formatstring—Export format (for 'export' action)
fpsarray—Issue fingerprints (for 'done' and 'reopen' actions)
limitinteger—Maximum number of issues to return (for 'next' action, default: 25)
pathstring—Output file path (for 'export' action)
scopeobject—Filter scope (for 'next', 'progress', and 'export' actions)
statusstring—Status to set (for 'done' action)
targetstring—Path to SARIF file or directory (for 'load' action)

No output schema declared.

No examples provided.