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

io.github.abyssbugg-labs/sourcery

NPM · @ABYSSBUGG/SOURCERY · SCANNED OCT 6

Sourcery security findings: MCP server, CLI, and fix-prompt builder over the Sourcery API.

Available components

76 Trust /100
Trust breakdown (7 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 → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 92 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 abyssbugg-labs/sourcery-agent-bundle). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 5 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 696 tokens (~58/item across 12 items; 12 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage67
  • 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 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

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

How do I install the io.github.abyssbugg-labs/sourcery MCP server?

io.github.abyssbugg-labs/sourcery runs locally as an npm package, launched with npx -y @abyssbugg/sourcery. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @abyssbugg/sourcery

# add to Claude Code
claude mcp add abyssbugg-labs-sourcery -- npx -y @abyssbugg/sourcery
// .cursor/mcp.json
{
  "mcpServers": {
    "abyssbugg-labs-sourcery": {
      "command": "npx",
      "args": [
        "-y",
        "@abyssbugg/sourcery"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "abyssbugg-labs-sourcery": {
      "command": "npx",
      "args": [
        "-y",
        "@abyssbugg/sourcery"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add abyssbugg-labs-sourcery -- npx -y @abyssbugg/sourcery
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "abyssbugg-labs-sourcery": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@abyssbugg/sourcery"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add abyssbugg-labs-sourcery --command npx --arg -y --arg @abyssbugg/sourcery
# ~/.hermes/config.yaml
mcp_servers:
  abyssbugg-labs-sourcery:
    command: "npx"
    args: ["-y", "@abyssbugg/sourcery"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "abyssbugg-labs-sourcery": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@abyssbugg/sourcery"
      ]
    }
  }
}
# add to Vellum
assistant mcp add abyssbugg-labs-sourcery -t stdio -c npx -a -y @abyssbugg/sourcery
// mcp.json
{
  "mcpServers": {
    "abyssbugg-labs-sourcery": {
      "command": "npx",
      "args": [
        "-y",
        "@abyssbugg/sourcery"
      ]
    }
  }
}
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.

  • 1 Oct 26 +25
    • Malware scan: unverified → pass ▲ security
    • Known CVEs: unverified → pass ▲ security
    • Security disclosure: unverified → fail ▼ functional
    • Dependency health: unverified → 0.84 ▲ functional
  • 30 Sept 26 51

    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 7 Oct 2026 · Analysed npm/@abyssbugg/sourcery@0.2.4

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 npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo abyssbugg-labs/sourcery-agent-bundle
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/abyssbugg-labs/sourcery-agent-bundle/.github/workflows/publish.yml@refs/tags/v0.2.4
Rekor log index 3010746566
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:5e31dfd8206e76fb470d05a3456732efeba1b0965afd37738c7b48559fc9ff290744bd86bb3dd82e94e0356a728277e3ec59412a155e669d35344c7fa

Background: How many MCP packages publish verified provenance →

Dependencies 92 packages
Packages resolved 92
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 12 exposed · ~631 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. 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 →

Tool Tokens
sourcery_api_request ~82

Compatibility bridge: call one of the eight verified operations directly. Prefer the typed tools. The path allow-list is enforced in the client; anything outside the pinned OpenAPI surface is rejected before a request is made.

NameTypeReqDescription
body_jsonstring––
methodstringyes–
params_jsonstring––
pathstringyes–

No output schema declared.

No examples provided.

sourcery_build_fix_prompt ~61

Build a minimal-change agent prompt from a Sourcery finding object. Handles DEPENDENCY findings via `fixed_versions` + `manifest_file_path` and renders the dependency chain when `dependency_graph` is present.

NameTypeReqDescription
finding_jsonstringyes–

No output schema declared.

No examples provided.

sourcery_bulk_update_findings ~90

Bulk-update issue status/severity (max 100 ids; SOLVED cannot be set manually). Returns `updated_ids` plus `failed` entries with reason `not_found` or `not_eligible`.

NameTypeReqDescription
idsarrayyes–
reasonstring|null––
severity_override–––
snoozed_untilstring|null––
status–––

No output schema declared.

No examples provided.

sourcery_bulk_update_groups ~67

Bulk-update groups (max 100 ids); a group updates when at least one issue changes.

NameTypeReqDescription
idsarrayyes–
reasonstring|null––
severity_override–––
snoozed_untilstring|null––
status–––

No output schema declared.

No examples provided.

sourcery_capabilities ~21

Return the verified Sourcery integration boundary for this bundle.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

sourcery_get_finding ~35

Fetch a single security issue (full record incl. source snippet and dependency graph).

NameTypeReqDescription
finding_idintegeryes–

No output schema declared.

No examples provided.

sourcery_get_group ~33

Fetch a single issue group including all its issues and any linked tracker task.

NameTypeReqDescription
group_idintegeryes–

No output schema declared.

No examples provided.

sourcery_get_group_counts ~31

Aggregate group counts by status and severity.

NameTypeReqDescription
issue_types–––
repository_ids–––

No output schema declared.

No examples provided.

sourcery_get_security_counts ~31

Aggregate issue counts by status and severity.

NameTypeReqDescription
issue_types–––
repository_ids–––

No output schema declared.

No examples provided.

sourcery_list_findings ~68

List security issues with spec filters; pass a previous `next_cursor` to page.

NameTypeReqDescription
cursorstring|null––
issue_types–––
limitinteger––
repository_ids–––
searchstring|null––
statuses–––

No output schema declared.

No examples provided.

sourcery_list_groups ~66

List security issue groups (same filters as findings; groups aggregate one rule/package).

NameTypeReqDescription
cursorstring|null––
issue_types–––
limitinteger––
repository_ids–––
searchstring|null––
statuses–––

No output schema declared.

No examples provided.

sourcery_security_snapshot ~46

Triage overview: counts by status/severity plus the first page of active issues.

NameTypeReqDescription
issue_types–––
limitinteger––
repository_ids–––

No output schema declared.

No examples provided.

Common questions

What is the io.github.abyssbugg-labs/sourcery MCP server?

io.github.abyssbugg-labs/sourcery is an MCP server listed in the public MCP registry as io.github.abyssbugg-labs/sourcery. Sourcery security findings: MCP server, CLI, and fix-prompt builder over the Sourcery API. This page covers its npm package (@abyssbugg/sourcery).

Is the io.github.abyssbugg-labs/sourcery MCP server safe to use?

io.github.abyssbugg-labs/sourcery scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 6 October 2026. It declares no install or post-install scripts. 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 io.github.abyssbugg-labs/sourcery MCP server expose?

io.github.abyssbugg-labs/sourcery exposes 12 tools: sourcery_capabilities, sourcery_security_snapshot, sourcery_list_findings, sourcery_get_finding, sourcery_get_security_counts, and 7 more. Their descriptions and schemas cost roughly 631 tokens of context every time the server is loaded.

Is the io.github.abyssbugg-labs/sourcery MCP server still maintained?

io.github.abyssbugg-labs/sourcery is still listed as active in the MCP registry. We last reached this channel on 6 October 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.abyssbugg-labs/sourcery MCP server under?

io.github.abyssbugg-labs/sourcery declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.