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.

io.github.grahamnotgrant/blacksmith

NPM · BLACKSMITH-MCP · SCANNED AUG 3

MCP server for Blacksmith CI - query runs, analyze test failures, detect flaky tests.

Available components

+24 this week 70 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 Security87
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (130 of 134), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (130 of 134), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 1727 tokens (~82/item across 21 items; 21 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

npm · blacksmith-mcp

# add to Claude Code
claude mcp add grahamnotgrant-blacksmith -- npx -y blacksmith-mcp
# add to Codex CLI
codex mcp add grahamnotgrant-blacksmith -- npx -y blacksmith-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "grahamnotgrant-blacksmith": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "blacksmith-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add grahamnotgrant-blacksmith --command npx --arg -y --arg blacksmith-mcp
# ~/.hermes/config.yaml
mcp_servers:
  grahamnotgrant-blacksmith:
    command: "npx"
    args: ["-y", "blacksmith-mcp"]
// mcp.json
{
  "mcpServers": {
    "grahamnotgrant-blacksmith": {
      "command": "npx",
      "args": [
        "-y",
        "blacksmith-mcp"
      ]
    }
  }
}
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.

  • 3 Aug 26 +4
    • Stability: unverified → 0.27 functional
  • 2 Aug 26 +45
    • Provenance: unverified → fail security
    • Install scripts: unverified → pass security
    • Known CVEs: unverified → partial security
    • Malware scan: unverified → pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • Schema quality: unverified → excellent functional
    • License: unverified → pass functional
    • Dependency health: unverified → partial functional
    • Maintenance: unverified → pass functional
    • MCP protocol: unverified → pass functional
    • Licence: MIT functional
  • 31 Jul 26 −3
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Jul 26 −22
    • Tool coverage: 100 → unverified functional
    • First check of Schema quality: unverified functional
  • 27 Jul 26 46

    First indexed and scored.

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 npm/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 130 packages

130 packages in the resolved dependency tree · 130 deprecated · 49 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 21 exposed · ~1,727 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
compare_test_runs ~111

Compare test failures between two runs to identify regressions. Shows new failures, fixed tests, and persistent failures. If base_run_id not provided, compares against most recent prior run.

NameTypeReqDescription
base_run_idstringBase run ID to compare against. If not provided, compares against most recent prior run.
job_namestringyesJob name to compare (e.g., "Test (Blacksmith/Self-Hosted)")
run_idstringyesCurrent GitHub Actions workflow run ID

No output schema declared.

No examples provided.

get_cache_entries ~95

Get detailed cache entries for a repository. Shows cache keys, sizes, scopes (branches), and last hit times. Useful for debugging cache issues.

NameTypeReqDescription
limitnumberMaximum number of entries to return (default: 20)
repositorystringyesRepository name - try short name first (e.g., "votion"), or full name (e.g., "Votion-Platform/votion") if needed

No output schema declared.

No examples provided.

get_cache_stats ~49

Get Blacksmith cache statistics: total size, hit rate, entries by repository. Shows how effectively caching is being used.

NameTypeReqDescription
include_historybooleanInclude historical cache data (default: false)

No output schema declared.

No examples provided.

get_current_usage ~21

Get current core usage snapshot (active cores vs max cores).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_failed_tests ~130

Get failed tests for a job with full error details. Use error_lines param to control stack trace length. Returns all failures by default (no limit).

NameTypeReqDescription
error_linesnumberNumber of error lines to include per test (default: 5, max: 50)
job_idstringyesGitHub Actions job ID
limitnumberMaximum number of failed tests to return (default: all)
run_idstringyesGitHub Actions workflow run ID
suitestringFilter by test suite name (e.g., "FeatureFlags Middleware")

No output schema declared.

No examples provided.

get_failures_by_pattern ~100

Group failed tests by error pattern (e.g., "is not a function", "Cannot read properties"). Shows count, affected suites/files, and sample error for each pattern. Best for quickly identifying root causes.

NameTypeReqDescription
job_idstringyesGitHub Actions job ID
run_idstringyesGitHub Actions workflow run ID
top_nnumberNumber of top error patterns to return (default: 10)

No output schema declared.

No examples provided.

get_flaky_tests ~154

Detect flaky tests by analyzing pass/fail patterns across recent runs. Returns tests that fail intermittently (e.g., "failed 3 of 10 runs"). Killer feature for CI stability.

NameTypeReqDescription
daysnumberNumber of days to analyze (default: 7)
job_namestringyesJob name to analyze (e.g., "Test (Blacksmith/Self-Hosted)")
min_runsnumberMinimum number of runs a test must appear in to be considered (default: 3)
thresholdnumberFlakiness threshold 0-1, e.g., 0.2 means test failed 20%+ of runs (default: 0.1)

No output schema declared.

No examples provided.

get_invoice_amount ~17

Get the current billing period invoice amount.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_job ~50

Get details of a specific job including steps, runner info, and timing.

NameTypeReqDescription
job_idstringyesGitHub Actions job ID
run_idstringyesGitHub Actions workflow run ID

No output schema declared.

No examples provided.

get_job_logs ~68

Get the logs for a specific job. Returns raw log output.

NameTypeReqDescription
job_idstringyesGitHub Actions job ID
limitnumberMaximum number of log lines (default: 1000)
vm_idstringVM ID for the job (optional)

No output schema declared.

No examples provided.

get_job_tests ~109

Get test results for a job. Optionally filter by status (pass/fail/skip).

NameTypeReqDescription
include_testsbooleanInclude individual test details (default: false, returns summary only)
job_idstringyesGitHub Actions job ID
limitnumberMaximum number of tests to return when include_tests is true (default: 50)
run_idstringyesGitHub Actions workflow run ID
statusstringFilter by test status

No output schema declared.

No examples provided.

get_org_status ~25

Get the status of the current organization (personal org, onboarding, runner region).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_run ~37

Get details of a specific workflow run by ID. Includes list of jobs.

NameTypeReqDescription
run_idstringyesGitHub Actions workflow run ID

No output schema declared.

No examples provided.

get_slow_tests ~103

Find tests exceeding a duration threshold. Shows slowest tests, their percentage of total test time, and average duration stats.

NameTypeReqDescription
job_idstringyesGitHub Actions job ID
limitnumberMaximum number of slow tests to return (default: 20)
run_idstringyesGitHub Actions workflow run ID
threshold_msnumberDuration threshold in milliseconds (default: 5000ms = 5s)

No output schema declared.

No examples provided.

get_test_history ~118

Get the failure history for a specific test across recent runs. Shows when it passed/failed, on which branches, and error messages for failures.

NameTypeReqDescription
job_namestringyesJob name to search in (e.g., "Test (Blacksmith/Self-Hosted)")
limitnumberNumber of historical results to return (default: 10)
suitestringTest suite name (helps disambiguate if multiple tests have same name)
test_namestringyesName of the test to look up

No output schema declared.

No examples provided.

get_trends ~133

Track metrics over time: duration (are tests getting slower?), failure_rate (are tests getting flakier?), test_count (are we adding tests?). Returns trend analysis with data points.

NameTypeReqDescription
daysnumberNumber of days to analyze (default: 14)
granularitystringGroup data by day or week (default: day)
job_namestringyesJob name to analyze (e.g., "Test (Blacksmith/Self-Hosted)")
metricstringyesMetric to track: duration (job runtime), failure_rate (% tests failing), test_count (total tests)

No output schema declared.

No examples provided.

get_usage_summary ~29

Get usage summary showing billable minutes vs free tier allowance. Shows remaining free minutes and overage.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_jobs ~50

List all jobs for a specific workflow run. Use this to get job IDs for get_job, get_job_logs, and get_job_tests.

NameTypeReqDescription
run_idstringyesGitHub Actions workflow run ID

No output schema declared.

No examples provided.

list_orgs ~28

List all Blacksmith organizations accessible to your account. Use this first to see available orgs.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_runs ~171

List workflow runs with filtering. Filter by status (success/failure/cancelled/skipped/in_progress), branch, workflow name, actor, or PR number. Example: list_runs(status="failure") to find failed runs.

NameTypeReqDescription
actorstringFilter by actor (GitHub username who triggered the run)
branchstringFilter by branch name
end_datestringEnd date (YYYY-MM-DD)
limitnumberMaximum number of runs to return
pr_numbernumberFilter by pull request number
start_datestringStart date (YYYY-MM-DD)
statusstringFilter by run status: success, failure, cancelled, skipped, or in_progress
workflow_namestringFilter by workflow name

No output schema declared.

No examples provided.

search_logs ~129

Search logs across all jobs. Filter by query (e.g., "error", "timeout"), log level (INFO/WARN/ERROR/DEBUG), and time range. Great for finding issues across runs.

NameTypeReqDescription
hoursnumberNumber of hours to search back (default: 1, max: 24)
levelstringFilter by log level
limitnumberMaximum number of logs to return (default: 100)
querystringSearch query (e.g., "error", "timeout", "failed"). Leave empty to get all logs.

No output schema declared.

No examples provided.