Skip to content

apideck.com MCP server

com.apideck/mcpapideck.comstreamable-httpv0.1.13Scanned

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

4 tools: 1 can delete or cancel things and 3 only read.

Tools: 1 delete, 0 irreversible, 0 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the apideck.com MCP server can do

The apideck.com MCP server is published by apideck.com, a domain the MCP Registry verified. It has 4 tools. It can delete or cancel things (1 tool: execute_tool). 3 tools only read.

1 tool brings in text other people can write (execute_tool).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 10, 2026, version 0.1.13.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Deletes or cancels 1Claude Code: deny
  • execute_toolInvoke a tool by name.Reads text others writeNo findings

    Why it is in this group

    • The name "execute_tool" says "execute": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Invoke a tool by name. `input` is validated against the target schema before dispatch.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
Only reads 3Show 3 read-only tools
  • describe_tool_inputReturn the JSON-Schema input contract for a tool by name.No findings

    Why it is in this group

    • The name "describe_tool_input" says "describe": a word for reading.
    Description, as the server wrote it
    Return the JSON-Schema input contract for a tool by name.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_scopesReturn the list of allowed MCP scopes.No findings

    Why it is in this group

    • The name "list_scopes" says "list": a word for reading.
    Description, as the server wrote it
    Return the list of allowed MCP scopes.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_toolsDiscover Apideck tools.No findings

    Why it is in this group

    • The name "list_tools" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:34 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 destructive). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.apideck.dev/mcp: tools/list returned 4 tools to an anonymous client, including execute_tool (destructive)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools2 changed.~2 changedView diff

Install

Pinned to version 0.1.13. Values in angle brackets are yours to fill in.

claude mcp add --transport http apideck https://mcp.apideck.dev/mcp --header 'x-apideck-api-key: <your-x-apideck-api-key>' --header 'x-apideck-app-id: <your-x-apideck-app-id>' --header 'x-apideck-consumer-id: <your-x-apideck-consumer-id>'
claude mcp add --transport http apideck https://mcp.apideck.dev/mcp --header 'x-apideck-api-key: <your-x-apideck-api-key>' --header 'x-apideck-app-id: <your-x-apideck-app-id>' --header 'x-apideck-consumer-id: <your-x-apideck-consumer-id>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__apideck__list_tools",
      "mcp__apideck__describe_tool_input",
      "mcp__apideck__list_scopes"
    ],
    "ask": [],
    "deny": [
      "mcp__apideck__execute_tool"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as apideck. Review it before you use it.

Capability tags behind 1 rule
  • mcp__apideck__execute_tool untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.apideck/mcp/verify?hash=2bd2228d076860c6ff426c4a74af4b4c622c8e725a8f0a68382943ba5a6cd012" | jq -e '.changed == false'

Pinned hash 2bd2228d0768, from Nov 10, 2026, 10:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.apideck/mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.apideck/mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/com.apideck/mcp.svg)](https://radar.anlyon.com/servers/com.apideck/mcp)

Source: MCP Registry · repository. Synced Oct 21, 2026, 17:49 UTC.

apideck.com MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the apideck.com MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the apideck.com MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: execute_tool.

Can the apideck.com MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the apideck.com MCP server have?

4 tools: 1 destructive, 3 read. execute_tool, list_tools, describe_tool_input and list_scopes.

Does the apideck.com MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the apideck.com MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the apideck.com MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Oct 29, 2026. Every change is on this page and in its Atom feed.