mcpbeat Sign in

Apideck MCP Server

not responding

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

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

Installs per day peak 81 · avg 22 · +123% w/w
a month agotoday
Uptime history 51 days of history · worst day 0%
51 days agonow
2.2%
Uptime 24h
2 of 91 checks
4
Tools
read from the server
378 ms
Response time
average over 24h
97
Installs / week
npm and PyPI

What changed 1

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 10 August 2026. No other catalogue keeps this.

10 Aug a tool changed version

Apideck does not always answer

Over the last week it answered 0.9% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 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"
    }
  }
}

This one needs environment variables set before it will start: APIDECK_API_KEY (Your Apideck API key (from https://platform.apideck.com/configuration/api-keys).), APIDECK_APP_ID (Your Apideck application ID (from https://platform.apideck.com/configuration/api-keys).), APIDECK_CONSUMER_ID (The end-user/customer ID whose Vault connections should be used.). The author declared them in the registry entry; get the values from the project itself.

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 174 ms 7 min ago

Alternatives to Apideck

same job, measured the same way
MCP Reportia
by javalenciacai

Reportia HTTP API as 66 curated MCP tools (accounting, mappings, SIIGO).

110 installs/wk local only
Wafeq
by ohneben

Wafeq accounting API: all 251 endpoints as safety-categorized MCP tools, over stdio or HTTP.

local only
Rise MCP
by gzlo

RISE CRM MCP server — 36 tools across CRM, projects, tickets, finance, sales, HR, and reports.

92 installs/wk local only
Bitget Agent MCP
by bitget-ai

Official Bitget MCP Server for the Unified Trading Account (UTA v3) API.

780 installs/wk local only
Holded MCP
by energio-es

MCP server for Holded — invoicing, accounting, CRM, projects, and team

61 installs/wk local only
Aurora Agent
by murariambati

FIBER decision-context compiler with honest omission accounting: 259 evidence-bearing MCP tools.

25 installs/wk local only
Crane Ledger
by craneledger

Headless API-first double-entry accounting & bookkeeping engine. 84 MCP tools over HTTP.

answering
Stripe_connect
by pipeworx-io

Stripe MCP Pack — read-only access to Stripe data via API key.

42 tools answering

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 2 of 91 checks got a reply (2.2%), average response time 378 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 378 ms on average, which is faster than 43% of all working MCP servers we measure. 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 97 times in the last week. Week over week that is +123%. 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, 17 stars on GitHub and 2 open issues. The source link is on this page, so you can read exactly what it does with your data before you connect it.