_ registry / a2a + mcp http-sse

Apideck

https://developers.apideck.com

Registry code: 58cc9c99c6c40f2d

api record

Apideck exposes 229 tools across 5 Unified APIs (Accounting, CRM, HRIS, File Storage, Lead) covering 200+ downstream SaaS services. Managed OAuth via Apideck Vault; progressive tool discovery via four meta-tools keeps the initial context under ~1,300 tokens.

endpoint
https://mcp.apideck.dev/mcp
door code
25543122921cb2c4
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is Apideck live?
Yes — it answered the hub's last check. It answered 99% of checks over the last 30 days.
Is Apideck free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does Apideck have?
4 tools: list_scopes, list_tools, describe_tool_input, execute_tool.
Is Apideck safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
unknown
uptime, 30 days
99.4%

90 days 99.2%

latency
—

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 251 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
topic
developer tools apis & integration
used for
  • read and write accounting records across saas
  • manage crm contacts across platforms
  • manage hris employee data
  • manage files across cloud storage
  • search apideck documentation
takes → gives
data → data, documents
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
4 never probed 0 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_scopes unknown never probed

    Return the list of allowed MCP scopes.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {}
}
    arguments 5 lines
  • list_tools unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "scope": {
      "enum": [
        "read",
        "write",
        "destructive"
      ],
      "type": "string",
      "description": "Filter by mutation scope: \"read\" (no writes), \"write\" (creates/updates), or \"destructive\" (deletes/overwrites). Omit to include all scopes."
    },
    "domain": {
      "type": "string",
      "description": "Restrict results to a single tool domain (e.g. \"accounting\", \"hris\"). Omit to get the cross-domain index. Use a key returned by a prior no-arg call."
    },
    "search_terms": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Case-insensitive substring terms ANDed across a tool name/description (e.g. [\"invoice\",\"create\"]). Omit to list everything in the domain."
    }
  }
}
    arguments 26 lines
  • describe_tool_input unknown never probed

    Return the JSON-Schema input contract for a tool by name.

    mcp-tool

    {
  "type": "object",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "Exact tool name to describe (e.g. \"accounting-invoices-create\"), as returned by list_tools."
    }
  }
}
    arguments 12 lines
  • execute_tool unknown never probed

    Invoke a tool by name. `input` is validated against the target schema before dispatch.

    mcp-tool

    {
  "type": "object",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "Exact tool name to invoke (e.g. \"accounting-invoices-create\"), as returned by list_tools."
    },
    "input": {
      "type": "object",
      "description": "Arguments object validated before being forwarded to the target tool. Its shape matches that tool's input schema (fetch it with describe_tool_input). Omit for tools that take no arguments.",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    }
  }
}
    arguments 20 lines
_ try it over mcp through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your agent card — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 58cc9c99c6c40f2d.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/58cc9c99c6c40f2d/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/58cc9c99c6c40f2d/badge.svg)](https://brick.blue/agent/58cc9c99c6c40f2d?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we knowoff the a2a door
card completeness
87%

How much of the published card is filled in. Not a judgement of the agent — a measure of what it told the world about itself.

spec deviations
1

Places where the published card departs from the specification. Recorded rather than hidden, and counted against every agent the same way.

  • supportedInterfaces[0].protocolBinding missing
_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on apideck.com 1 entry

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.