# @gaffer-sh/mcp

Test analytics for AI agents: test history, flaky tests, failure clusters, coverage.

- **Type:** MCP server
- **Trust:** 85/100 (A), scored on the package rubric
- **Verification:** verified (build provenance)
- **Version:** 0.9.0
- **Author:** sh.gaffer
- **License:** Unknown
- **npm:** @gaffer-sh/mcp
- **Source:** https://github.com/gaffer-sh/mcp
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

85/100 (A), scored on the package rubric
- Publisher verified: no
- Build provenance: verified attestation
- npm trusted publishing (OIDC): yes
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 9 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-08-19T07:51:45.422Z
- **Version scanned:** 0.9.0
- **CVEs:** none found by OSV at scan time

## Tools

20 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `execute_code`
- `search_tools`
- `compare_test_metrics`
- `find_uncovered_failure_areas`
- `get_coverage_for_file`
- `get_coverage_summary`
- `get_failure_clusters`
- `get_flaky_tests`
- `get_project_health`
- `get_report_browser_url`
- `get_report`
- `get_slowest_tests`
- `get_test_history`
- `get_test_run_details`
- `get_untested_files`
- `get_upload_status`
- `list_test_runs`
- `search_failures`
- `upload_test_results`
- `list_projects`

## Install

**Verdict: install** — No blocking findings and no open coverage gaps — safe to install as configured.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"mcp\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"@gaffer-sh/mcp\"\n      ]\n    }\n  }\n}"
```

## Blast radius

Moderate to extensive — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: mutates data; runs on your machine.
- Floor 31, ceiling 55 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/%40gaffer-sh%2Fmcp
- Install plan: https://forgeregistry.com/api/v1/packages/%40gaffer-sh%2Fmcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/%40gaffer-sh%2Fmcp
- HTML page: https://forgeregistry.com/registry/%40gaffer-sh%2Fmcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.