mcpbeat

Apideck MCP Server

com.apideck/mcp
not responding

Apideck is listed as active in the registry but did not answer our last check. 420 installs a week from npm. It exposes 4 tools. Last commit 2 Aug 2026.

Apideck Unified API MCP — 330 tools across 200+ SaaS connectors (accounting, CRM, HRIS, ATS).

Installs per day peak 223 · avg 52 · -13% w/w
a month agotoday
Uptime history 40 hours of history · worst hour 0%
40 hours agonow
3.3%
Uptime 24h
3 of 91 checks
4
Tools
read from the server
481 ms
Response time
average over 24h
420
Installs / week
npm and PyPI

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

run in your terminal
claude mcp add mcp --transport http https://mcp.apideck.dev/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.apideck.dev/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.mcp]
url = "https://mcp.apideck.dev/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.apideck.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.apideck.dev/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

describe
describe_tool_input
Return the JSON-Schema input contract for a tool by name.
execute
execute_tool
Invoke a tool by name. `input` is forwarded raw to the tool handler.
scopes
list_scopes
Return the list of allowed MCP scopes.
tools
list_tools
Discover Apideck tools. Call with no args for domain index; filter with domain/search_terms/scope.

Endpoints

URLTransportStateLatencyChecked
https://mcp.apideck.dev/mcp streamable-http answering 337 ms 11 min ago

Apideck — questions

Answers built from our own checks of this server.

What can Apideck do?
It exposes 4 tools, read directly from the server on our last check. Among them: describe_tool_input, execute_tool, list_scopes, list_tools. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Apideck working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 3 of 91 checks got a reply (3.3%), average response time 481 ms. The bar chart above shows every period we have measured.
The registry lists Apideck as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Apideck?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Apideck need an API key?
No. Apideck completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Apideck?
It answers our handshake in 481 ms on average, which is faster than 24% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use Apideck?
The npm package @apideck/mcp was installed 420 times in the last week. Week over week that is -13%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Apideck open source?
Yes — it is published under the MIT licence, written in Dockerfile and 15 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.