io.github.grahamnotgrant/blacksmith
NPM · BLACKSMITH-MCP
MCP server for Blacksmith CI - query runs, analyze test failures, detect flaky tests.
Available components
Last scanned (3 hours ago)
Scores higher than 61% of npm servers
Category Testing and QA
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 Security80
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 51 of 128 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency44
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 288 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability79
- 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 21 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 4 Nov 26 0
- Stability: 0.97 → pass security
- 3 Nov 26 +1
- Security disclosure: fail → unverified ▼ functional
- 2 Nov 26 −1
- Stability: pass → 0.93 functional
- 1 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 30 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 28 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 27 Oct 26 0
- Stability: 0.97 → pass security
- Security disclosure: fail → unverified ▼ functional
- 26 Oct 26 0
- Stability: pass → 0.97 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 5 Nov 2026 · Analysed npm/blacksmith-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 128 packages
| Packages resolved | 128 |
|---|---|
| Deprecated | 1 |
| Stale | 50 |
| 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 →
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.
| Name | Type | Req | Description |
|---|---|---|---|
| base_run_id | string | – | Base run ID to compare against. If not provided, compares against most recent prior run. |
| job_name | string | yes | Job name to compare (e.g., "Test (Blacksmith/Self-Hosted)") |
| run_id | string | yes | Current 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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of entries to return (default: 20) |
| repository | string | yes | Repository 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.
| Name | Type | Req | Description |
|---|---|---|---|
| include_history | boolean | – | Include 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).
| Name | Type | Req | Description |
|---|---|---|---|
| error_lines | number | – | Number of error lines to include per test (default: 5, max: 50) |
| job_id | string | yes | GitHub Actions job ID |
| limit | number | – | Maximum number of failed tests to return (default: all) |
| run_id | string | yes | GitHub Actions workflow run ID |
| suite | string | – | Filter 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.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | GitHub Actions job ID |
| run_id | string | yes | GitHub Actions workflow run ID |
| top_n | number | – | Number 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.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | Number of days to analyze (default: 7) |
| job_name | string | yes | Job name to analyze (e.g., "Test (Blacksmith/Self-Hosted)") |
| min_runs | number | – | Minimum number of runs a test must appear in to be considered (default: 3) |
| threshold | number | – | Flakiness 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.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | GitHub Actions job ID |
| run_id | string | yes | GitHub 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.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | GitHub Actions job ID |
| limit | number | – | Maximum number of log lines (default: 1000) |
| vm_id | string | – | VM 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).
| Name | Type | Req | Description |
|---|---|---|---|
| include_tests | boolean | – | Include individual test details (default: false, returns summary only) |
| job_id | string | yes | GitHub Actions job ID |
| limit | number | – | Maximum number of tests to return when include_tests is true (default: 50) |
| run_id | string | yes | GitHub Actions workflow run ID |
| status | string | – | Filter 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.
| Name | Type | Req | Description |
|---|---|---|---|
| run_id | string | yes | GitHub 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.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | GitHub Actions job ID |
| limit | number | – | Maximum number of slow tests to return (default: 20) |
| run_id | string | yes | GitHub Actions workflow run ID |
| threshold_ms | number | – | Duration 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.
| Name | Type | Req | Description |
|---|---|---|---|
| job_name | string | yes | Job name to search in (e.g., "Test (Blacksmith/Self-Hosted)") |
| limit | number | – | Number of historical results to return (default: 10) |
| suite | string | – | Test suite name (helps disambiguate if multiple tests have same name) |
| test_name | string | yes | Name 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.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | Number of days to analyze (default: 14) |
| granularity | string | – | Group data by day or week (default: day) |
| job_name | string | yes | Job name to analyze (e.g., "Test (Blacksmith/Self-Hosted)") |
| metric | string | yes | Metric 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.
| Name | Type | Req | Description |
|---|---|---|---|
| run_id | string | yes | GitHub 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.
| Name | Type | Req | Description |
|---|---|---|---|
| actor | string | – | Filter by actor (GitHub username who triggered the run) |
| branch | string | – | Filter by branch name |
| end_date | string | – | End date (YYYY-MM-DD) |
| limit | number | – | Maximum number of runs to return |
| pr_number | number | – | Filter by pull request number |
| start_date | string | – | Start date (YYYY-MM-DD) |
| status | string | – | Filter by run status: success, failure, cancelled, skipped, or in_progress |
| workflow_name | string | – | Filter 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.
| Name | Type | Req | Description |
|---|---|---|---|
| hours | number | – | Number of hours to search back (default: 1, max: 24) |
| level | string | – | Filter by log level |
| limit | number | – | Maximum number of logs to return (default: 100) |
| query | string | – | Search query (e.g., "error", "timeout", "failed"). Leave empty to get all logs. |
No output schema declared.
No examples provided.
How do I install the io.github.grahamnotgrant/blacksmith MCP server?
io.github.grahamnotgrant/blacksmith runs locally as an npm package, launched with npx -y blacksmith-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · blacksmith-mcp
claude mcp add grahamnotgrant-blacksmith -- npx -y blacksmith-mcp
What is the io.github.grahamnotgrant/blacksmith MCP server?
io.github.grahamnotgrant/blacksmith is an MCP server listed in the public MCP registry as io.github.grahamnotgrant/blacksmith. MCP server for Blacksmith CI - query runs, analyze test failures, detect flaky tests. This page covers its npm package (blacksmith-mcp).
Is the io.github.grahamnotgrant/blacksmith MCP server safe to use?
io.github.grahamnotgrant/blacksmith scores 79 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. 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 io.github.grahamnotgrant/blacksmith MCP server expose?
io.github.grahamnotgrant/blacksmith exposes 21 tools: list_orgs, get_org_status, list_runs, get_run, list_jobs, and 16 more. Their descriptions and schemas cost roughly 1,727 tokens of context every time the server is loaded.
Is the io.github.grahamnotgrant/blacksmith MCP server still maintained?
io.github.grahamnotgrant/blacksmith is still listed as active in the MCP registry. We last reached this channel on 5 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 io.github.grahamnotgrant/blacksmith MCP server under?
io.github.grahamnotgrant/blacksmith declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.