Skip to content

Agent Provider Depot MCP server

Which MCP servers are Agent Provider Depot's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-30

← Back to Agent Provider Depot

Whose server it is
  • Registry namecom.getagentdepot/agent-provider-depotverified in the MCP registry

The registry name sits under getagentdepot.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-30
  • Stateanswerschecked 2026-10-30
  • Tools4
  • Server calls itselfcom.getagentdepot/agent-provider-depot
  • Server version0.16.8
  • Protocol version2025-06-18

On 2026-10-30 the server answered initialize and tools/list without a sign-in. First answer in 142 ms.

Should an agent connect itNot proven either way yet
  • Its tools do every use case we checked: pick a default provider for each job; estimate monthly cost of a multi-job stack; find a replacement provider after runtime errors.
  • Checked on 4 of the 7 days it takes to judge reliability.

Once connected

  • For "pick a default provider for each job", the likely first call is decide.
  • For "estimate monthly cost of a multi-job stack", the likely first call is depot.
  • For "find a replacement provider after runtime errors", the likely first call is rescue.
  • Parameters are untyped or undescribed in 3 of 4 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 4, the first on 2026-10-30
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 4 so far
  • What an agent can do with it3 of 3 use cases
  • Answeredmeasuring4 of the 7 daily checks it takes to print a share
  • Median first answer147 ms
  • Space in an agent's context≈ 845 tokensthe definitions of all its tools (4), which an agent carries on every turn
  • Tool definitionsB · 88 of 100
  • Typed results0 of 4 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 3 of 4

What an agent can do with it

  • can do · pick a default provider for each job
  • can do · estimate monthly cost of a multi-job stack
  • can do · find a replacement provider after runtime errors

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers4 tools · read 2026-10-30
  • session_brief

    What changed for the stack you run since your last call: retired models, price changes, deprecated packages, pick changes. Use at session start if your code calls third-party APIs. Send provider, model and package ids (never a manifest)…

  • rescue

    Diagnose a failing third-party API call before you retry or swap: paste the exact error (429, 402, 529 overloaded, insufficient_quota, model_not_found, deprecated SDK) and provider id. Returns the cause, an immediate fix and a fallback…

  • decide

    Choose a provider before writing integration code: LLM API, code sandbox, vector DB, web search, email, Postgres, auth, browser, observability. Send task in words or a jtbd id. Returns the dated editorial Depot Pick, a runner-up, the…

  • depot

    Lookups beyond one pick; one op per call, args as an object: quote(jtbd) sourced SKU prices; estimate(jtbd, workload) monthly cost; compare(providers); free(jtbd) $0/OSS rows; check(providers) deprecated/retired flags…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "agent-provider-depot": {
      "type": "http",
      "url": "https://getagentdepot.com/api/mcp?via=mcp-registry"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http getagentdepot https://getagentdepot.com/api/mcp?via=mcp-registry

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://getagentdepot.com/api/mcp?via=mcp-registry as a custom connector in the settings.

OpenAPI spec

144 paths, read 2026-10-30. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.