Sourcery security findings for AI coding agents: MCP server, findings CLI, and remediation prompt builder over the public Sourcery security API.
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
SOURCERY_API_KEYAPI keyrequiredSourcery Team-plan API key with security scanning enabled
Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
sourcery_capabilitiesReturn the verified Sourcery integration boundary for this bundle.Return the verified Sourcery integration boundary for this bundle.
No input schema was published for this tool.
sourcery_security_snapshotTriage overview: counts by status/severity plus the first page of active issues.Triage overview: counts by status/severity plus the first page of active issues.
No input schema was published for this tool.
sourcery_list_findingsList security issues with spec filters; pass a previous `next_cursor` to page.List security issues with spec filters; pass a previous `next_cursor` to page.
No input schema was published for this tool.
sourcery_get_findingFetch a single security issue (full record incl. source snippet and dependency graph).Fetch a single security issue (full record incl. source snippet and dependency graph).
No input schema was published for this tool.
sourcery_get_security_countsAggregate issue counts by status and severity.Aggregate issue counts by status and severity.
No input schema was published for this tool.
sourcery_bulk_update_findingsBulk-update issue status/severity (max 100 ids; SOLVED cannot be set manually).Bulk-update issue status/severity (max 100 ids; SOLVED cannot be set manually).
No input schema was published for this tool.
sourcery_list_groupsList security issue groups (same filters as findings; groups aggregate one rule/package).List security issue groups (same filters as findings; groups aggregate one rule/package).
No input schema was published for this tool.
sourcery_get_groupFetch a single issue group including all its issues and any linked tracker task.Fetch a single issue group including all its issues and any linked tracker task.
No input schema was published for this tool.
sourcery_get_group_countsAggregate group counts by status and severity.Aggregate group counts by status and severity.
No input schema was published for this tool.
sourcery_bulk_update_groupsBulk-update groups (max 100 ids); a group updates when at least one issue changes.Bulk-update groups (max 100 ids); a group updates when at least one issue changes.
No input schema was published for this tool.
sourcery_build_fix_promptBuild a minimal-change agent prompt from a Sourcery finding object.Build a minimal-change agent prompt from a Sourcery finding object.
No input schema was published for this tool.
sourcery_api_requestCompatibility bridge: call one of the eight verified operations directly.Compatibility bridge: call one of the eight verified operations directly.
No input schema was published for this tool.
12 of 12 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Sourcery security findings for AI coding agents: MCP server, findings CLI, and remediation prompt builder over the public Sourcery security API.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
The crawl stopped at the depth-4 limit. Anything below that level was never resolved.
The crawl stopped at the 60-package limit. The rest of the tree was never resolved.
36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)
53 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.
+41 more not listed. The counts by reason above cover all of them.
Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.