mcpbeat Sign in

Apideck MCP Server

not responding

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

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

Installs per day peak 252 · avg 61 · -12% w/w
a month agotoday
Uptime history 91 days of history · worst day 0%
91 days agonow
0.0%
Uptime 24h
0 of 92 checks
4
Tools
read from the server
95 ms
Response time
average over 24h
373
Installs / week
npm and PyPI

What changed 8

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

27 Oct a tool description was rewritten list_tools
14 Oct a tool changed version2 times that day
14 Oct a tool changed the parameters it asks for execute_tool
14 Oct a tool description was rewritten execute_tool
12 Oct a tool changed version
5 Oct a tool changed version
10 Aug a tool changed version
and 1 more, back to 10 August 2026

Apideck does not always answer

Over the last week it answered 17.7% 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 0 min ago.

run in your terminal
claude mcp add mcp --transport http https://mcp.apideck.dev/mcp
Settings → Connectors → Add custom connector, then paste this address
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
{
  "servers": {
    "mcp": {
      "type": "http",
      "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 validated against the target schema before dispatch.
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. Scoped to the connection's supported resources when service_id is set.

Endpoints

URLTransportStateLatencyChecked
https://mcp.apideck.dev/mcp streamable-http answering 95 ms 0 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).

60 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.

80 installs/wk local only
CRM Connector
by crm-connector

The integration hub for your CRM, field service and accounting apps: integrations and AI agents.

63 tools answering
Qoyod Connector (Awsel)
by awsel

Turn chat invoices into drafts in Qoyod accounting. 27 tools, OAuth sign-in, human approval.

answering
Bitget Agent MCP
by bitget-ai

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

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

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

96 installs/wk local only
Daftra Connector (Awsel)
by awsel

Turn chat invoices into drafts in Daftra accounting. 16 tools, OAuth sign-in, human approval.

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 0 of 92 checks got a reply (0.0%), average response time 95 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 in the form 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 many people use Apideck?
The npm package @apideck/mcp was installed 373 times in the last week. Week over week that is -12%. 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?
The code is open source: it is published under the MIT licence, written in Dockerfile, 21 stars on GitHub and 1 open issue. The licence covers the code in the repository, not the hosted service at mcp.apideck.dev, which runs on its operator's own terms.