Is supportbee-mcp live?

Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.

Is supportbee-mcp free to use?

No — it asks for a key or a login before it will serve.

What tools does supportbee-mcp have?

22 tools: supportbee_list_labels, supportbee_list_forwarding_addresses, supportbee_get_reply, supportbee_get_user, supportbee_remove_label, supportbee_unassign_ticket, supportbee_list_snippets, supportbee_list_teams, ….

Is supportbee-mcp 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.

_ registry / mcp streamable-http · checked 1h ago

supportbee-mcp

https://supportbee.usefulapi.io

Registry code: 17ca36c11b6aa13d

api record

Tools for SupportBee, hosted by usefulapi.io. Read-only tools never change data; ask the user before a tool that creates, changes or deletes SupportBee data. Free plan: 100 tool calls per month. Run supportbee_usage_status to see the calls used this month. If the user asks for something none of these tools can do, tell the user and, with their OK, run supportbee_request_feature to record the request. Pro (unlimited calls, $9/month or $90/year): when the user wants more calls or reaches the limit, run supportbee_upgrade; it returns a Stripe Checkout link for the user to open.…

endpoint: https://supportbee.usefulapi.io/mcp
protocol: streamable-http ·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 supportbee-mcp live?: Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is supportbee-mcp free to use?: No — it asks for a key or a login before it will serve.
What tools does supportbee-mcp have?: 22 tools: supportbee_list_labels, supportbee_list_forwarding_addresses, supportbee_get_reply, supportbee_get_user, supportbee_remove_label, supportbee_unassign_ticket, supportbee_list_snippets, supportbee_list_teams, ….
Is supportbee-mcp 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

live

uptime, 30 days

100%

90 days 100%· all time 100%

latency

151ms

last good check

priced tools

of 22 tools

_ answered our checks, 90 days 1 checks · signed record

2026-10-11 22:40 unknown → live

_ 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

through this hub

calls served

successful

paid through this hub

0 USDC

what callers paid

_ what it can do 22 tools

22 auth-required 22 of 22 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.

supportbee_list_labels auth-required 1h ago
All custom labels of the company (name and color). Use a label name with supportbee_add_label or the label filter. GET /labels.

mcp-tool
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": {} }
arguments 5 lines
supportbee_list_forwarding_addresses auth-required never probed
The support e-mail addresses (forwarding addresses) of the desk: id, name, the address tickets arrive at and the from address. GET /emails.

mcp-tool
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": {} }
arguments 5 lines

supportbee_get_reply auth-required never probed

One reply of a ticket (text, replier, cc/bcc). GET /tickets/{ticket_id}/replies/{id}.

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "ticket_id",
    "reply_id"
  ],
  "properties": {
    "reply_id": {
      "type": "integer",
      "maximum": 9007199254740991,
      "description": "The reply id (from supportbee_list_replies).",
      "exclusiveMinimum": 0
    },
    "ticket_id": {
      "type": "integer",
      "maximum": 9007199254740991,
      "description": "The SupportBee ticket id (the number in the ticket URL; from supportbee_list_tickets).",
      "exclusiveMinimum": 0
    }
  }
}

arguments 22 lines

supportbee_get_user auth-required never probed

One user or customer with role, teams, ticket counts and a few of their recent tickets. GET /users/{id}.

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "user_id"
  ],
  "properties": {
    "user_id": {
      "type": "integer",
      "maximum": 9007199254740991,
      "description": "The user id (from supportbee_list_users).",
      "exclusiveMinimum": 0
    },
    "max_tickets": {
      "type": "integer",
      "maximum": 50,
      "minimum": 0,
      "description": "How many of the user's tickets to include (default 5)."
    }
  }
}

arguments 21 lines

supportbee_remove_label auth-required never probed

WRITE: removes a label from a ticket (the label itself stays; 404 if the ticket does not have it). DELETE /tickets/{id}/labels/{label}.

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "ticket_id",
    "label"
  ],
  "properties": {
    "label": {
      "type": "string",
      "maxLength": 100,
      "minLength": 1,
      "description": "The label name."
    },
    "ticket_id": {
      "type": "integer",
      "maximum": 9007199254740991,
      "description": "The SupportBee ticket id (the number in the ticket URL; from supportbee_list_tickets).",
      "exclusiveMinimum": 0
    }
  }
}

arguments 22 lines

supportbee_unassign_ticket auth-required never probed

WRITE: clears the user assignee or the team assignee of a ticket. DELETE /tickets/{id}/user_assignment or /team_assignment.

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "ticket_id",
    "assignee"
  ],
  "properties": {
    "assignee": {
      "enum": [
        "user",
        "team"
      ],
      "type": "string",
      "description": "Which assignment to clear."
    },
    "ticket_id": {
      "type": "integer",
      "maximum": 9007199254740991,
      "description": "The SupportBee ticket id (the number in the ticket URL; from supportbee_list_tickets).",
      "exclusiveMinimum": 0
    }
  }
}

arguments 24 lines

supportbee_list_snippets auth-required 1h ago
The canned replies (snippets) of the company: name, tags and text, to reuse in a reply. GET /snippets.

mcp-tool
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": {} }
arguments 5 lines

supportbee_list_teams auth-required 1h ago

The teams of the company (id, name), optionally only those that have users in them, or only the token user's teams. GET /teams.

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "mine_only": {
      "type": "boolean",
      "description": "Only the teams of the user who owns the token."
    },
    "with_users": {
      "type": "boolean",
      "description": "Only teams that have users in them (SupportBee's with_users filter; it does not add the member list)."
    }
  }
}

arguments 14 lines

supportbee_list_tickets auth-required never probed

List tickets of the shared inbox, newest activity first, with filters (assignee, team, label, requester, dates, spam/trash/archived). By default archived, spam and trashed tickets are left out. Each ticket has id, subject, labels, requester, assignee, replies_count, comments_count, unanswered, archived and the first message text (cut). With total_only=true only the number of matching tickets comes back. GET /tickets.

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "page": {
      "type": "integer",
      "maximum": 10000,
      "minimum": 1,
      "description": "Page number, 1-based (default 1). Use next_page from the previous reply."
    },
    "spam": {
      "type": "boolean",
      "description": "Include tickets marked as spam (default false)."
    },
    "label": {
      "type": "string",
      "maxLength": 100,
      "minLength": 1,
      "description": "Only tickets with this label name (supportbee_list_labels)."
    },
    "since": {
      "type": "string",
      "pattern": "^(\\d{4}-\\d{2}-\\d{2}([T ]\\d{2}:\\d{2}(:\\d{2}(\\.\\d+)?)?(Z|[+-]\\d{2}:?\\d{2})?)?|\\d{9,11})$",
      "description": "Only tickets with last activity after this time (date, ISO date-time or Unix timestamp)."
    },
    "trash": {
      "type": "boolean",
      "description": "Include trashed tickets (default false)."
    },
    "until": {
      "type": "string",
      "pattern": "^(\\d{4}-\\d{2}-\\d{2}([T ]\\d{2}:\\d{2}(:\\d{2}(\\.\\d+)?)?(Z|[+-]\\d{2}:?\\d{2})?)?|\\d{9,11})$",
      "description": "Only tickets with last activity before this time (date, ISO date-time or Unix timestamp)."
    },
    "sort_by": {
      "enum": [
        "last_activity",
        "creation_time"
      ],
      "type": "string",
      "description": "Sort order (default last_activity)."
    },
    "archived": {
      "enum": [
        "true",
        "false",
        "any"
      ],
      "type": "string",
      "description": "true = only archived tickets, false = no archived tickets (default), any = both."
    },
    "per_page": {
      "type": "integer",
      "maximum": 99,
      "minimum": 1,
      "description": "Tickets per page, 1-99 (default 15)."
    },
    "total_only": {
      "type": "boolean",
      "description": "Return only the total number of matching tickets."
    },
    "has_replies": {
      "type": "boolean",
      "description": "true = only tickets that have replies, false = only tickets without replies."
    },
    "max_replies": {
      "type": "integer",
      "maximum": 1000,
      "minimum": 0,
      "description": "Only tickets with this number of replies (not with has_replies=false)."
    },
    "assigned_team": {
      "type": "string",
      "pattern": "^(mine|none|\\d{1,12})$",
      "description": "mine = assigned to the user's teams, a team id (from supportbee_list_teams), none = no team."
    },
    "assigned_user": {
      "type": "string",
      "pattern": "^(me|any|none|\\d{1,12})$",
      "description": "me = assigned to the token's user, an agent id (from supportbee_list_users), any = assigned to someone, none = unassigned."
    },
    "requester_emails": {
      "type": "array",
      "items": {
        "type": "string",
        "format": "email",
        "pattern": "^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
        "maxLength": 254
      },
      "maxItems": 10,
      "minItems": 1,
      "description": "Only tickets from these requester e-mail addresses (max 10)."
    }
  }
}

arguments 95 lines

supportbee_search_tickets auth-required never probed

Full-text search over tickets (subject, body, requester) with SupportBee's search syntax, newest activity first. Spam and trash are excluded unless asked. GET /tickets/search.

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "query"
  ],
  "properties": {
    "page": {
      "type": "integer",
      "maximum": 10000,
      "minimum": 1,
      "description": "Page number, 1-based (default 1). Use next_page from the previous reply."
    },
    "spam": {
      "type": "boolean",
      "description": "Include tickets marked as spam (default false)."
    },
    "query": {
      "type": "string",
      "maxLength": 500,
      "minLength": 1,
      "description": "The search keywords or query."
    },
    "trash": {
      "type": "boolean",
      "description": "Include trashed tickets (default false)."
    },
    "per_page": {
      "type": "integer",
      "maximum": 99,
      "minimum": 1,
      "description": "Tickets per page, 1-99 (default 15)."
    }
  }
}

arguments 35 lines

supportbee_get_ticket auth-required never probed

One ticket with subject, requester, labels, assignees, state and the first message text. Replies and comments are separate calls. GET /tickets/{id}.

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "ticket_id"
  ],
  "properties": {
    "ticket_id": {
      "type": "integer",
      "maximum": 9007199254740991,
      "description": "The SupportBee ticket id (the number in the ticket URL; from supportbee_list_tickets).",
      "exclusiveMinimum": 0
    }
  }
}

arguments 15 lines

supportbee_list_replies auth-required never probed

The public replies (the conversation with the customer) of a ticket, oldest first, as text. GET /tickets/{id}/replies.

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "ticket_id"
  ],
  "properties": {
    "ticket_id": {
      "type": "integer",
      "maximum": 9007199254740991,
      "description": "The SupportBee ticket id (the number in the ticket URL; from supportbee_list_tickets).",
      "exclusiveMinimum": 0
    }
  }
}

arguments 15 lines

supportbee_list_comments auth-required never probed

The internal comments (visible to agents only, never e-mailed) of a ticket, oldest first, as text. GET /tickets/{id}/comments.

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "ticket_id"
  ],
  "properties": {
    "ticket_id": {
      "type": "integer",
      "maximum": 9007199254740991,
      "description": "The SupportBee ticket id (the number in the ticket URL; from supportbee_list_tickets).",
      "exclusiveMinimum": 0
    }
  }
}

arguments 15 lines

supportbee_get_ticket_audit auth-required never probed

What happened to a ticket and who did it (assignments, label changes, replies, archiving) with timestamps. GET /tickets/{id}/audit.

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "ticket_id"
  ],
  "properties": {
    "ticket_id": {
      "type": "integer",
      "maximum": 9007199254740991,
      "description": "The SupportBee ticket id (the number in the ticket URL; from supportbee_list_tickets).",
      "exclusiveMinimum": 0
    }
  }
}

arguments 15 lines

supportbee_list_users auth-required never probed

The agents, admins and collaborators of the desk (id, name, e-mail, role, teams), or customer groups. Use the id as assigned_user or user_id. GET /users.

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "type": {
      "enum": [
        "user",
        "customer_group"
      ],
      "type": "string",
      "description": "user (default) or customer_group."
    },
    "with_roles": {
      "type": "array",
      "items": {
        "enum": [
          "admin",
          "agent",
          "collaborator",
          "customer"
        ],
        "type": "string"
      },
      "maxItems": 4,
      "minItems": 1,
      "description": "Roles to include (default admin, agent, collaborator)."
    },
    "with_invited": {
      "type": "boolean",
      "description": "Include users who were invited but have not joined yet (default false)."
    }
  }
}

arguments 33 lines

supportbee_get_report auth-required never probed

A report as time-series data points (value, timestamp): tickets_count, replies_count or avg_first_response_time, optionally for one agent, team or label. Needs an admin token. GET /reports/{report}.

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "report"
  ],
  "properties": {
    "team": {
      "type": "integer",
      "maximum": 9007199254740991,
      "description": "Only this team (team id).",
      "exclusiveMinimum": 0
    },
    "user": {
      "type": "integer",
      "maximum": 9007199254740991,
      "description": "Only this agent (user id).",
      "exclusiveMinimum": 0
    },
    "label": {
      "type": "string",
      "maxLength": 100,
      "minLength": 1,
      "description": "Only this label (name)."
    },
    "since": {
      "type": "string",
      "pattern": "^(\\d{4}-\\d{2}-\\d{2}([T ]\\d{2}:\\d{2}(:\\d{2}(\\.\\d+)?)?(Z|[+-]\\d{2}:?\\d{2})?)?|\\d{9,11})$",
      "description": "Start of the period (date, ISO date-time or Unix timestamp)."
    },
    "report": {
      "enum": [
        "tickets_count",
        "replies_count",
        "avg_first_response_time"
      ],
      "type": "string",
      "description": "Which report."
    }
  }
}

arguments 41 lines

supportbee_reply_to_ticket auth-required never probed

WRITE: SENDS AN E-MAIL to the customer. Posts a public reply on ONE ticket; SupportBee e-mails it to the ticket's requester and to the cc/bcc addresses you list (at most 10 addresses in total). It cannot be recalled. The reply comes from the token's user. For a note only your team sees, use supportbee_add_comment. POST /tickets/{id}/replies.

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "ticket_id",
    "text"
  ],
  "properties": {
    "cc": {
      "type": "array",
      "items": {
        "type": "string",
        "format": "email",
        "pattern": "^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
        "maxLength": 254
      },
      "maxItems": 10,
      "description": "Extra recipients in cc (cc + bcc together at most 10)."
    },
    "bcc": {
      "type": "array",
      "items": {
        "type": "string",
        "format": "email",
        "pattern": "^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
        "maxLength": 254
      },
      "maxItems": 10,
      "description": "Extra recipients in bcc (cc + bcc together at most 10)."
    },
    "text": {
      "type": "string",
      "maxLength": 20000,
      "minLength": 1,
      "description": "The reply text (plain text; blank lines separate paragraphs)."
    },
    "ticket_id": {
      "type": "integer",
      "maximum": 9007199254740991,
      "description": "The SupportBee ticket id (the number in the ticket URL; from supportbee_list_tickets).",
      "exclusiveMinimum": 0
    }
  }
}

arguments 44 lines

supportbee_add_comment auth-required never probed

WRITE: adds an internal comment to a ticket. Comments are visible to your agents only and are never e-mailed to the customer. POST /tickets/{id}/comments.

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "ticket_id",
    "text"
  ],
  "properties": {
    "text": {
      "type": "string",
      "maxLength": 20000,
      "minLength": 1,
      "description": "The comment text (plain text; blank lines separate paragraphs)."
    },
    "ticket_id": {
      "type": "integer",
      "maximum": 9007199254740991,
      "description": "The SupportBee ticket id (the number in the ticket URL; from supportbee_list_tickets).",
      "exclusiveMinimum": 0
    }
  }
}

arguments 22 lines

supportbee_add_label auth-required never probed

WRITE: adds an existing label to a ticket (404 if the label does not exist; names come from supportbee_list_labels). Safe to repeat. POST /tickets/{id}/labels/{label}.

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "ticket_id",
    "label"
  ],
  "properties": {
    "label": {
      "type": "string",
      "maxLength": 100,
      "minLength": 1,
      "description": "The label name, exactly as in supportbee_list_labels."
    },
    "ticket_id": {
      "type": "integer",
      "maximum": 9007199254740991,
      "description": "The SupportBee ticket id (the number in the ticket URL; from supportbee_list_tickets).",
      "exclusiveMinimum": 0
    }
  }
}

arguments 22 lines

supportbee_assign_ticket auth-required never probed

WRITE: assigns a ticket to ONE agent (user_id) or ONE team (team_id), not both. A ticket that belongs to a team can only go to a member of that team; assigning to another team removes the user assignee. The customer is not e-mailed (SupportBee may notify the assigned agent). POST /tickets/{id}/user_assignment or /team_assignment.

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "ticket_id"
  ],
  "properties": {
    "team_id": {
      "type": "integer",
      "maximum": 9007199254740991,
      "description": "The team id (supportbee_list_teams).",
      "exclusiveMinimum": 0
    },
    "user_id": {
      "type": "integer",
      "maximum": 9007199254740991,
      "description": "The agent id (supportbee_list_users).",
      "exclusiveMinimum": 0
    },
    "ticket_id": {
      "type": "integer",
      "maximum": 9007199254740991,
      "description": "The SupportBee ticket id (the number in the ticket URL; from supportbee_list_tickets).",
      "exclusiveMinimum": 0
    }
  }
}

arguments 27 lines

supportbee_set_ticket_archived auth-required never probed

WRITE: archives a ticket (archived=true, it leaves the open inbox) or moves it back (archived=false). Nothing is deleted or sent. POST/DELETE /tickets/{id}/archive.

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "ticket_id",
    "archived"
  ],
  "properties": {
    "archived": {
      "type": "boolean",
      "description": "true = archive, false = move back to the inbox."
    },
    "ticket_id": {
      "type": "integer",
      "maximum": 9007199254740991,
      "description": "The SupportBee ticket id (the number in the ticket URL; from supportbee_list_tickets).",
      "exclusiveMinimum": 0
    }
  }
}

arguments 20 lines

supportbee_set_ticket_answered auth-required never probed

WRITE: marks a ticket as answered (answered=true) or unanswered (answered=false) without sending anything. POST/DELETE /tickets/{id}/answered.

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "ticket_id",
    "answered"
  ],
  "properties": {
    "answered": {
      "type": "boolean",
      "description": "true = mark answered, false = mark unanswered."
    },
    "ticket_id": {
      "type": "integer",
      "maximum": 9007199254740991,
      "description": "The SupportBee ticket id (the number in the ticket URL; from supportbee_list_tickets).",
      "exclusiveMinimum": 0
    }
  }
}

arguments 20 lines

_ try it 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.

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

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

_ for your README measured, not declared

[![measured by brick.blue](https://brick.blue/api/v1/agents/17ca36c11b6aa13d/badge.svg)](https://brick.blue/agent/17ca36c11b6aa13d?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 know

card completeness

100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ 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 usefulapi.io 131 entries

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.

fleetio.usefulapi.io fleetio-mcp mcp · 44 tools
runcloud.usefulapi.io runcloud-mcp mcp · 36 tools
billomat.usefulapi.io billomat-mcp mcp · 34 tools
teamgate.usefulapi.io teamgate-mcp mcp · 34 tools
synchroteam.usefulapi.io synchroteam-mcp mcp · 33 tools
sendlane.usefulapi.io sendlane-mcp mcp · 31 tools
klippa-dochorizon.usefulapi.io klippa-dochorizon-mcp mcp · 30 tools
pipeline-crm.usefulapi.io pipeline-crm-mcp mcp · 30 tools

123 more sit on this domain. All of them.