Ably MCP by usefulapi
io.usefulapi/ablyusefulapi.iostreamable-httpv1.40.4Scanned
MCP server for Ably — channel history, presence, occupancy, stats, publish, and app management.
15 tools: 1 can delete or cancel things and 14 only read.
- Reads private data · 4
- Reads text others write · 3
- Can send data out · 1
- No findings
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
1 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the Ably MCP by usefulapi can do
The Ably MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 15 tools. It can delete or cancel things (1 tool: ably_publish_message). 14 tools only read.
4 tools read private data (ably_get_channel_history, ably_get_stats, ably_list_keys and 1 more); 3 tools bring in text other people can write (ably_get_channel_history, ably_get_stats and ably_list_queues); 1 tool can send data out of your system (ably_publish_message). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Oct 25, 2026, version 1.40.4.
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.
15 tools
Deletes or cancels 1Claude Code: deny
ably_publish_messageWRITE: publish a message to a channel.Can send data outNo findings
Why it is in this group
- The name "ably_publish_message" says "publish": a word for a change that another call does not undo.
- The server marks it destructive (destructiveHint: true).
What it can reach
- outboundThe name "ably_publish_message" says "publish": it sends or publishes something to other people.
Description, as the server wrote it WRITE: publish a message to a channel. Every connected subscriber receives it in real time. This is a real, outward-facing side effect — confirm the channel and payload before calling. REST: POST /channels/{channel}/messages.
Annotations the server declares
- title: Publish a message to a channel
- readOnlyHint: false
- destructiveHint: true
Only reads 14Show 14 read-only tools
ably_get_account_statsRetrieve aggregated usage statistics across the whole account, bucketed by time.No findings
Why it is in this group
- The name "ably_get_account_stats" says "get": a word for reading.
Description, as the server wrote it Retrieve aggregated usage statistics across the whole account, bucketed by time. Account id is resolved from the control token when ABLY_ACCOUNT_ID is unset. Control API: GET /accounts/{account_id}/stats.
Annotations the server declares
- title: Get account-level statistics
- readOnlyHint: true
ably_get_channel_detailsGet status and occupancy metrics for a single channel (connections, publishers, subscribers, presence members).No findings
Why it is in this group
- The name "ably_get_channel_details" says "get": a word for reading.
Description, as the server wrote it Get status and occupancy metrics for a single channel (connections, publishers, subscribers, presence members). REST: GET /channels/{channel}.
Annotations the server declares
- title: Get channel details / occupancy
- readOnlyHint: true
ably_get_channel_historyRetrieve historical messages published to a channel, newest-first by default.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "ably_get_channel_history" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "retrieve" and "message": it reads messages.
- untrusted-inputThe description's first sentence says "retrieve" and "message": it reads messages, which other people can write.
Description, as the server wrote it Retrieve historical messages published to a channel, newest-first by default. REST: GET /channels/{channel}/messages.
Annotations the server declares
- title: Get channel message history
- readOnlyHint: true
ably_get_presenceList the members currently present on a channel (who is online now).No findings
Why it is in this group
- The name "ably_get_presence" says "get": a word for reading.
Description, as the server wrote it List the members currently present on a channel (who is online now). REST: GET /channels/{channel}/presence.
Annotations the server declares
- title: Get channel presence set
- readOnlyHint: true
ably_get_presence_historyRetrieve historical presence events (enter/leave/update) for a channel.No findings
Why it is in this group
- The name "ably_get_presence_history" says "get": a word for reading.
Description, as the server wrote it Retrieve historical presence events (enter/leave/update) for a channel. REST: GET /channels/{channel}/presence/history.
Annotations the server declares
- title: Get channel presence history
- readOnlyHint: true
ably_get_service_timeReturn the current Ably service time in ms since epoch.No findings
Why it is in this group
- The name "ably_get_service_time" says "get": a word for reading.
Description, as the server wrote it Return the current Ably service time in ms since epoch. Useful for aligning start/end windows to the server clock. REST: GET /time.
Annotations the server declares
- title: Get Ably service time
- readOnlyHint: true
ably_get_statsRetrieve message/connection/channel usage statistics for the app tied to the API key, bucketed by time.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "ably_get_stats" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "retrieve" and "message": it reads messages.
- untrusted-inputThe description's first sentence says "retrieve" and "message": it reads messages, which other people can write.
Description, as the server wrote it Retrieve message/connection/channel usage statistics for the app tied to the API key, bucketed by time. REST: GET /stats.
Annotations the server declares
- title: Get app statistics
- readOnlyHint: true
ably_list_appsList all apps in the account (id, name, status, tls-only).No findings
Why it is in this group
- The name "ably_list_apps" says "list": a word for reading.
Description, as the server wrote it List all apps in the account (id, name, status, tls-only). Account id is resolved automatically from the control token when ABLY_ACCOUNT_ID is unset. Control API: GET /accounts/{account_id}/apps.
Annotations the server declares
- title: List Ably apps
- readOnlyHint: true
ably_list_channelsEnumerate channels that are currently active in the app.No findings
Why it is in this group
- The name "ably_list_channels" says "list": a word for reading.
Description, as the server wrote it Enumerate channels that are currently active in the app. Requires the API key to have the 'channel-metadata' capability. REST: GET /channels.
Annotations the server declares
- title: List active channels
- readOnlyHint: true
ably_list_keysList the API keys for an app, including their capabilities (but not the full secret).Reads private dataNo findings
Why it is in this group
- The name "ably_list_keys" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "secret": it reads secrets.
Description, as the server wrote it List the API keys for an app, including their capabilities (but not the full secret). Control API: GET /apps/{app_id}/keys.
Annotations the server declares
- title: List an app's API keys
- readOnlyHint: true
ably_list_namespacesList the channel namespaces (channel-rule prefixes) configured for an app, e.g.No findings
Why it is in this group
- The name "ably_list_namespaces" says "list": a word for reading.
Description, as the server wrote it List the channel namespaces (channel-rule prefixes) configured for an app, e.g. persistence and push settings. Control API: GET /apps/{app_id}/namespaces.
Annotations the server declares
- title: List an app's channel namespaces
- readOnlyHint: true
ably_list_queuesList the Ably Queues (AMQP/STOMP message queues) provisioned for an app, with their state and messaging stats.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "ably_list_queues" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "message": it reads messages.
- untrusted-inputThe description's first sentence says "list" and "message": it reads messages, which other people can write.
Description, as the server wrote it List the Ably Queues (AMQP/STOMP message queues) provisioned for an app, with their state and messaging stats. Control API: GET /apps/{app_id}/queues.
Annotations the server declares
- title: List an app's queues
- readOnlyHint: true
ably_list_rulesList the integration rules (reactor rules: webhooks, AWS Lambda/SQS/Kinesis, Kafka, Pulsar, etc.) configured for an app.No findings
Why it is in this group
- The name "ably_list_rules" says "list": a word for reading.
Description, as the server wrote it List the integration rules (reactor rules: webhooks, AWS Lambda/SQS/Kinesis, Kafka, Pulsar, etc.) configured for an app. Control API: GET /apps/{app_id}/rules.
Annotations the server declares
- title: List an app's integration rules
- readOnlyHint: true
ably_whoamiReturn details about the configured control token: the account and user it belongs to and its capabilities.No findings
Why it is in this group
- The name "ably_whoami" says "whoami": a word for reading.
Description, as the server wrote it Return details about the configured control token: the account and user it belongs to and its capabilities. Good first call to confirm control-plane access. Control API: GET /me.
Annotations the server declares
- title: Get control token / account info
- readOnlyHint: true
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.
12 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.
- Reads private data4
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__ably__ably_publish_message"
]
}
}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.
Looked at Nov 20, 2026, 19:31 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- no
- HTTP status of an anonymous initialize
- not observed
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- 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
The probe stopped: The server redirected a POST to a different request.
Posture changes
- Oct 29, 2026
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 1 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://ably.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://ably.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
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.
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 1 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://ably.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://ably.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Install
Pinned to version 1.40.4. Values in angle brackets are yours to fill in.
claude mcp add --transport http ably https://ably.usefulapi.io/mcpclaude mcp add --transport http ably https://ably.usefulapi.io/mcpRun 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.
{
"permissions": {
"allow": [
"mcp__ably__ably_get_channel_history",
"mcp__ably__ably_get_presence",
"mcp__ably__ably_get_presence_history",
"mcp__ably__ably_get_channel_details",
"mcp__ably__ably_list_channels",
"mcp__ably__ably_get_stats",
"mcp__ably__ably_get_service_time",
"mcp__ably__ably_whoami",
"mcp__ably__ably_list_apps",
"mcp__ably__ably_list_keys",
"mcp__ably__ably_list_namespaces",
"mcp__ably__ably_list_queues",
"mcp__ably__ably_list_rules",
"mcp__ably__ably_get_account_stats"
],
"ask": [],
"deny": [
"mcp__ably__ably_publish_message"
]
}
}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 ably. Review it before you use it.
Capability tags behind 5 rules
- mcp__ably__ably_get_channel_history private-data, untrusted-input
- mcp__ably__ably_get_stats private-data, untrusted-input
- mcp__ably__ably_publish_message outbound
- mcp__ably__ably_list_keys private-data
- mcp__ably__ably_list_queues private-data, 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/io.usefulapi/ably/verify?hash=65b814335260c3b341b9fa3d6449b4afa2279512751372b0c45f80c6e77a7313" | jq -e '.changed == false'Pinned hash 65b814335260, from Oct 25, 2026, 23:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.usefulapi/ably/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.usefulapi/ably)Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.
Ably MCP by usefulapi: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Ably MCP by usefulapi safe?
- No scan can promise that. What its definitions show: 15 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 Ably MCP by usefulapi delete data?
- Yes. 1 tool can delete, cancel or revoke something: ably_publish_message.
Can the Ably MCP by usefulapi 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 Ably MCP by usefulapi have?
- 15 tools: 1 destructive, 14 read. ably_publish_message, ably_get_channel_history, ably_get_presence, ably_get_presence_history, ably_get_channel_details, ably_list_channels, ably_get_stats, ably_get_service_time and 7 more.
Does the Ably MCP by usefulapi need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the Ably MCP by usefulapi send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): ably_publish_message.
Has the Ably MCP by usefulapi changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.