
Apideck MCP server
Which servers in the official MCP registry are Apideck's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-15
- Registry namecom.apideck/mcpverified in the MCP registry
The registry name sits under apideck.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-15
- Tools4
- Server calls itselfapideck-mcp
- Server version0.25.1
- Protocol version2025-06-18
On 2026-10-15 the server answered initialize and tools/list without a sign-in. First answer in 179 ms.
- Whether its tools do the product's job has not been judged yet.
- Checked on 4 of the 7 days it takes to judge reliability.
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.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 4 so far
- Use369 npm downloads a week20 GitHub stars
- Answeredmeasuring4 of the 7 daily checks it takes to print a share
- Median first answer180 ms
- Space in an agent's context≈ 477 tokensthe definitions of all its tools (4), which an agent carries on every turn
- Tool definitionsA · 100 of 100
- Typed results0 of 4 toolsdeclared outputSchema: results come typed, read once
- Every tool passes all six checks.
What an agent can do with it
- not sure · Sync vendor bills and approvals across accounting systems
- not sure · Send customer invoices and payment updates into users' ledgers
- not sure · Pull expense data to automate spend reporting
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 (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). 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 →
list_toolsDiscover Apideck tools. Call with no args for domain index; filter with domain/search_terms/scope.
describe_tool_inputReturn the JSON-Schema input contract for a tool by name.
execute_toolInvoke a tool by name. `input` is validated against the target schema before dispatch.
list_scopesReturn the list of allowed MCP scopes.
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"apideck": {
"type": "http",
"url": "https://mcp.apideck.dev/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http apideck https://mcp.apideck.dev/mcpclaude.ai, ChatGPT and other clients: add https://mcp.apideck.dev/mcp as a custom connector in the settings.
Also shipped through: npm
OpenAPI spec
14 paths, read 2026-10-15. 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.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.