depot-mcp

MCPattested

v0.2.1io.github.akshayjain3450UnknownUpdated 27d agonpm GitHub

Read-only MCP server for Depot (depot.dev): CI failure diagnosis, build forensics, and usage.

Works in

ClaudeCursorCopilotGemini

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.

Attested build

A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.

1GitHub stars

27d agoLast update

Needs 1 credential before it runs

DEPOT_TOKENAPI keyrequired
Depot Organization token (Organization Settings > API Tokens). Project tokens do not work.

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.

Package

Authorio.github.akshayjain3450

LicenseUnknown

Version0.2.1

Sourcenpm+mcp-registry

GitHubakshayjain3450/depot-mcp

SBOMCycloneDX 1.6 ↓

Trust Status

A

85/100Trusted

✓Listed in Forge index+10/10

✓Identity verified · attested build+20/20

—Ed25519 publish signature+0/5

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

✓npm Trusted Publishing (Sigstore)+5/5

—npm maintainer match+0/5

→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusIdentity verified

PublisherUnverified

SignatureUnsigned

Domain—

Provenance✓ Sigstore-verified · d1d6bce

Dependencies✓ 60 resolved+ · none vulnerable

Tool surface40 tools · 3 privileged

Security scan✓ Cleanv0.2.1 · 25d agoHow well does this scan work?

EvalsNone

IndexedSep 8, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

40 tools · 3 privileged

Statically extracted from the published packagev0.2.1 · 25d ago

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.

Filter toolsPrivileged only

depot_audit_trust_policiesNo description published

This tool published no description. Forge does not invent one.

depot_list_project_tokensNo description published

This tool published no description. Forge does not invent one.

depot_diagnose_buildNo description published

This tool published no description. Forge does not invent one.

depot_get_buildNo description published

This tool published no description. Forge does not invent one.

depot_list_buildsNo description published

This tool published no description. Forge does not invent one.

depot_get_cache_summaryNo description published

This tool published no description. Forge does not invent one.

depot_list_ci_artifactsNo description published

This tool published no description. Forge does not invent one.

depot_get_ci_artifact_urlNo description published

This tool published no description. Forge does not invent one.

depot_compare_ci_runsNo description published

This tool published no description. Forge does not invent one.

depot_list_ci_secretsNo description published

This tool published no description. Forge does not invent one.

depot_list_ci_variablesNo description published

This tool published no description. Forge does not invent one.

depot_diagnose_ci_failureNo description published

This tool published no description. Forge does not invent one.

depot_dispatch_ci_workflowNo description published

This tool published no description. Forge does not invent one.

depot_get_ci_jobNo description published

This tool published no description. Forge does not invent one.

depot_get_ci_attemptNo description published

This tool published no description. Forge does not invent one.

depot_get_ci_logsNo description published

This tool published no description. Forge does not invent one.

depot_get_ci_metricsNo description published

This tool published no description. Forge does not invent one.

depot_list_ci_runsNo description published

This tool published no description. Forge does not invent one.

depot_get_ci_runShow one Depot CI run as its workflow -> job -> attempt tree, with the status of every node and the ids needed to drill in. Use this to see the shape of a run: which jobs exist, which failed, and which attempt ids to pass to depot_get_ci_logs or depot_get_ci_metrics. Set failedOnly=true to cut a l…

Show one Depot CI run as its workflow -> job -> attempt tree, with the status of every node and the ids needed to drill in. Use this to see the shape of a run: which jobs exist, which failed, and which attempt ids to pass to depot_get_ci_logs or depot_get_ci_metrics. Set failedOnly=true to cut a l…

No input schema was published for this tool.

depot_get_ci_job_summaryNo description published

This tool published no description. Forge does not invent one.

depot_set_ci_variableNo description published

This tool published no description. Forge does not invent one.

depot_delete_ci_variableprivilegedNo description published

This tool published no description. Forge does not invent one.

depot_wait_for_ci_runNo description published

This tool published no description. Forge does not invent one.

depot_list_ci_workflowsNo description published

This tool published no description. Forge does not invent one.

depot_get_ci_workflowNo description published

This tool published no description. Forge does not invent one.

depot_cancel_ci_runNo description published

This tool published no description. Forge does not invent one.

depot_cancel_ci_jobCancel a single queued or running Depot CI job (CancelJob), leaving the rest of its workflow and run untouched. Use this for one stuck or pointless job, for example a matrix entry that is hanging, when the rest of the run should finish. To stop everything, use depot_cancel_ci_run instead. Cancelli…

Cancel a single queued or running Depot CI job (CancelJob), leaving the rest of its workflow and run untouched. Use this for one stuck or pointless job, for example a matrix entry that is hanging, when the rest of the run should finish. To stop everything, use depot_cancel_ci_run instead. Cancelli…

No input schema was published for this tool.

depot_retry_ci_failed_jobsNo description published

This tool published no description. Forge does not invent one.

depot_retry_ci_jobNo description published

This tool published no description. Forge does not invent one.

depot_rerun_ci_workflowNo description published

This tool published no description. Forge does not invent one.

depot_update_projectNo description published

This tool published no description. Forge does not invent one.

depot_delete_projectprivilegedNo description published

This tool published no description. Forge does not invent one.

depot_create_projectNo description published

This tool published no description. Forge does not invent one.

depot_list_projectsList Depot container build projects with their region, runner hardware, and cache policy. Use this to find a projectId for depot_list_builds, depot_diagnose_build, or depot_list_images, and to check configuration that affects build speed: which region a project builds in, how large its runners are…

List Depot container build projects with their region, runner hardware, and cache policy. Use this to find a projectId for depot_list_builds, depot_diagnose_build, or depot_list_images, and to check configuration that affects build speed: which region a project builds in, how large its runners are…

No input schema was published for this tool.

depot_get_projectNo description published

This tool published no description. Forge does not invent one.

depot_list_registry_repositoriesNo description published

This tool published no description. Forge does not invent one.

depot_get_registry_imageNo description published

This tool published no description. Forge does not invent one.

depot_list_imagesNo description published

This tool published no description. Forge does not invent one.

depot_stop_sandboxNo description published

This tool published no description. Forge does not invent one.

depot_kill_sandboxprivilegedNo description published

This tool published no description. Forge does not invent one.

3 of 40 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.

About

Read-only MCP server for Depot (depot.dev): CI failure diagnosis, build forensics, and usage.

Keywords

mcp

Alternatives

Comparing tool surfaces…

Tools exposed

40 tools · 3 privileged · observed 2026-09-09 by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-09 — observed resolution, not a publisher declaration.

60 packages resolved · 2 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

zod4.5.4
@modelcontextprotocol/sdk1.30.017 dependencies
- ajv8.20.04 dependencies
  - fast-deep-equal3.1.3
  - fast-uri3.1.7
  - json-schema-traverse1.0.0
  - require-from-string2.0.2
- zod4.5.4shown above
- cors2.8.62 dependencies
  - object-assign4.1.1
  - vary1.1.2
- hono4.13.7
- jose6.2.12
- express5.2.1+26 not drawn2 dependencies
  - vary1.1.2shown above
  - content-type1.0.5
- raw-body3.0.2+4 not drawn
- ajv-formats3.0.11 dependency
  - ajv8.20.0shown above
- cross-spawn7.0.6+3 not drawn
- eventsource3.0.71 dependency
  - eventsource-parser3.1.1
- content-type1.0.5shown above
- pkce-challenge5.0.1
- @hono/node-server2.1.1
- json-schema-typed8.0.2
- eventsource-parser3.1.1shown above
- express-rate-limit8.7.0+2 not drawn
- zod-to-json-schema3.25.2

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)

Declared but not resolved

53 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

package cap reached: 48
below the depth cap: 5

http-errors ^2.0.1 — required by send@1.2.1package cap reached
mime-types ^3.0.2 — required by send@1.2.1package cap reached
ms ^2.1.3 — required by send@1.2.1package cap reached
on-finished ^2.4.1 — required by send@1.2.1package cap reached
range-parser ^1.2.1 — required by send@1.2.1package cap reached
statuses ^2.0.2 — required by send@1.2.1package cap reached
ms ^2.1.3 — required by debug@4.4.3package cap reached
debug ^4.4.0 — required by router@2.2.0package cap reached
depd ^2.0.0 — required by router@2.2.0package cap reached
is-promise ^4.0.0 — required by router@2.2.0package cap reached
parseurl ^1.3.3 — required by router@2.2.0package cap reached
path-to-regexp ^8.0.0 — required by router@2.2.0package cap reached

+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.