Agent Provider Depot
com.getagentdepotPublished by getagentdepot.comOfficial publisherv0.17.21Updated Nov 5, 2026
No-key MCP: pick the LLM, sandbox, search, email or DB provider; sourced prices; API error rescue.
Overview
No-key remote MCP that recommends dated, sourced picks and prices for third-party infrastructure an agent wires in, plus API error rescue.
- What you can do
- Get an editorial pick, runner-up and sourced price for a described task, such as running untrusted code in a sandbox.
- Recheck a pick against a stored cursor before adding a provider or after a failure.
- Rescue a failing third-party API call by passing the exact error and provider id.
- Build a session brief from your known provider, model and package ids, returning actions and a cursor.
- Report whether a pick worked or failed, and run other depot operations via an op parameter.
- When to use it
- Useful when an agent is about to choose or wire in third-party infrastructure such as LLM APIs, sandboxes, vector databases, search, email, Postgres or auth, and you want a dated, sourced recommendation rather than a benchmark. Also handy for recovering from a failing provider API call.
- Requirements
- Remote streamable HTTP endpoint; no API key or environment variables declared. Assistants are asked to identify themselves via clientInfo.name or an X-Agent-Name header. Network access to the endpoint is required.
Installation
In SourceWeft
- Open Agent Provider Depot in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.getagentdepot%2Fagent-provider-depot/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"agent-provider-depot": {
"type": "http",
"url": "https://getagentdepot.com/api/mcp?via=mcp-registry"
}
}
}Tools
0Version history
5- v0.17.21LatestNov 5, 2026
- v0.17.19Nov 5, 2026
- v0.17.18Nov 5, 2026
- v0.17.17Nov 4, 2026
- v0.16.7Oct 30, 2026
Score
56% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listedRequired15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
Publish an icon in the registry entry.
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.