Ably MCP by usefulapi
REMOTE · ABLY.USEFULAPI.IO
MCP server for Ably — channel history, presence, occupancy, stats, publish, and app management.
Available components
Last scanned (6 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Communication
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Nov 26 −62
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 +3
- Authorization: partial → pass ▲ security
- MCP protocol: fail → pass ▲ functional
- New prompt “audit_app_setup_keys_namespaces_and_rules” functional
- New prompt “check_which_channels_have_people_connected” functional
- New prompt “publish_a_test_message_to_a_channel” functional
- New prompt “read_recent_messages_sent_on_a_channel” functional
- New prompt “review_app_and_account_usage_over_time” functional
- New prompt “see_who_is_present_on_a_channel” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.31.0 → 1.33.0 functional
- Server version: 1.30.0 → 1.31.0 functional
- Server version: 1.29.2 → 1.30.0 functional
- 30 Oct 26 0
- Server version: 1.29.1 → 1.29.2 functional
- Server version: 1.29.0 → 1.29.1 functional
- 29 Oct 26 0
- Server version: 1.28.0 → 1.29.0 functional
- Server version: 1.27.0 → 1.28.0 functional
- 28 Oct 26 0
- Server version: 1.25.0 → 1.27.0 functional
- 27 Oct 26 0
- Server version: 1.24.0 → 1.25.0 functional
- 25 Oct 26 0
- Server version: 1.23.0 → 1.24.0 functional
- Server version: 1.22.0 → 1.23.0 functional
- Server version: 1.21.3 → 1.22.0 functional
- Server version: 1.21.0 → 1.21.3 functional
- 24 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 1.20.0 → 1.21.0 functional
- Server version: 1.19.0 → 1.20.0 functional
- Server version: 1.17.0 → 1.19.0 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://ably.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of ably.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ably.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/ably/ |
| http (plaintext) | http://ably.usefulapi.io/mcp | Inconclusive | 302 | http://ably.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
ably_get_account_stats Get account-level statistics ~141
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.
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | string | – | Override the account id (defaults to the token's account). |
| end | integer | – | End of range, ms since epoch (inclusive). |
| limit | integer | – | Max buckets (<=1000). Default 100. |
| start | integer | – | Start of range, ms since epoch (inclusive). |
| unit | string | – | Bucket size: minute | hour | day | month. Default minute. |
No output schema declared.
No examples provided.
ably_get_channel_details Get channel details / occupancy ~47
Get status and occupancy metrics for a single channel (connections, publishers, subscribers, presence members). REST: GET /channels/{channel}.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | yes | Channel name. |
No output schema declared.
No examples provided.
ably_get_channel_history Get channel message history ~123
Retrieve historical messages published to a channel, newest-first by default. REST: GET /channels/{channel}/messages.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | yes | Channel name, e.g. 'chat:room1'. |
| direction | string | – | forwards (oldest-first) or backwards (newest-first, default). |
| end | integer | – | Latest message time, ms since epoch (inclusive). |
| limit | integer | – | Max messages (<=1000). Default 100. |
| start | integer | – | Earliest message time, ms since epoch (inclusive). |
No output schema declared.
No examples provided.
ably_get_presence Get channel presence set ~88
List the members currently present on a channel (who is online now). REST: GET /channels/{channel}/presence.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | yes | Channel name. |
| clientId | string | – | Filter to a specific clientId. |
| connectionId | string | – | Filter to a specific connectionId. |
| limit | integer | – | Max members (<=1000). Default 100. |
No output schema declared.
No examples provided.
ably_get_presence_history Get channel presence history ~108
Retrieve historical presence events (enter/leave/update) for a channel. REST: GET /channels/{channel}/presence/history.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | yes | Channel name. |
| direction | string | – | forwards or backwards (default backwards). |
| end | integer | – | Latest event time, ms since epoch (inclusive). |
| limit | integer | – | Max events (<=1000). Default 100. |
| start | integer | – | Earliest event time, ms since epoch (inclusive). |
No output schema declared.
No examples provided.
ably_get_service_time Get Ably service time ~40
Return the current Ably service time in ms since epoch. Useful for aligning start/end windows to the server clock. REST: GET /time.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ably_get_stats Get app statistics ~119
Retrieve message/connection/channel usage statistics for the app tied to the API key, bucketed by time. REST: GET /stats.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | forwards or backwards (default backwards). |
| end | integer | – | End of range, ms since epoch (inclusive). |
| limit | integer | – | Max buckets (<=1000). Default 100. |
| start | integer | – | Start of range, ms since epoch (inclusive). |
| unit | string | – | Bucket size: minute | hour | day | month. Default minute. |
No output schema declared.
No examples provided.
ably_list_apps List Ably apps ~74
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.
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | string | – | Override the account id (defaults to the token's account). |
No output schema declared.
No examples provided.
ably_list_channels List active channels ~97
Enumerate channels that are currently active in the app. Requires the API key to have the 'channel-metadata' capability. REST: GET /channels.
| Name | Type | Req | Description |
|---|---|---|---|
| by | string | – | Return channel ids only ('id', default) or full details ('value'). |
| limit | integer | – | Max channels per page (<=1000). Default 100. |
| prefix | string | – | Only return channels whose name starts with this prefix. |
No output schema declared.
No examples provided.
ably_list_keys List an app's API keys ~56
List the API keys for an app, including their capabilities (but not the full secret). Control API: GET /apps/{app_id}/keys.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | App id (from ably_list_apps). |
No output schema declared.
No examples provided.
ably_list_namespaces List an app's channel namespaces ~62
List the channel namespaces (channel-rule prefixes) configured for an app, e.g. persistence and push settings. Control API: GET /apps/{app_id}/namespaces.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | App id (from ably_list_apps). |
No output schema declared.
No examples provided.
ably_list_queues List an app's queues ~66
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.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | App id (from ably_list_apps). |
No output schema declared.
No examples provided.
ably_list_rules List an app's integration rules ~69
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.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | App id (from ably_list_apps). |
No output schema declared.
No examples provided.
ably_publish_message Publish a message to a channel ~125
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.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | yes | Channel name to publish to, e.g. 'chat:room1'. |
| clientId | string | – | Optional clientId to attribute the message to. |
| data | string | yes | Message payload (string; send JSON as a stringified value). |
| name | string | – | Optional event name for the message. |
No output schema declared.
No examples provided.
ably_whoami Get control token / account info ~46
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Ably MCP by usefulapi server?
Ably MCP by usefulapi is a hosted endpoint at https://ably.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · ably.usefulapi.io
claude mcp add --transport http io-usefulapi-ably 'https://ably.usefulapi.io/mcp'
What is the Ably MCP by usefulapi server?
Ably MCP by usefulapi is listed in the public MCP registry as io.usefulapi/ably. MCP server for Ably, channel history, presence, occupancy, stats, publish, and app management. This page covers its hosted endpoint (https://ably.usefulapi.io/mcp).
Is the Ably MCP by usefulapi server safe to use?
Ably MCP by usefulapi scores 18 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Ably MCP by usefulapi server expose?
Ably MCP by usefulapi exposes 15 tools: ably_get_channel_history, ably_get_presence, ably_get_presence_history, ably_get_channel_details, ably_list_channels, and 10 more. Their descriptions and schemas cost roughly 1,261 tokens of context every time the server is loaded.
Does the Ably MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Ably MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Ably MCP by usefulapi server still maintained?
Ably MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.