ably

Tools

15 tools: 14 read-only, 0 change data, 1 high risk (delete, pay, send or run code).

1 tool can send messages; they are listed first.

read-only

Only reads or looks things up. Safe for an agent to call on its own.

changes data

Creates, edits or sends something. Worth a person's approval the first time.

high risk

Can delete, pay, send on your behalf or run code. Hard or impossible to undo.

Connecting costs an agent about 2,600 tokens of tool definitions and a 697 ms handshake.

• high riskably_publish_messagesends messagesWRITE: 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.
• read-onlyably_get_channel_historyRetrieve historical messages published to a channel, newest-first by default. REST: GET /channels/{channel}/messages.
• read-onlyably_get_presenceList the members currently present on a channel (who is online now). REST: GET /channels/{channel}/presence.
• read-onlyably_get_presence_historyRetrieve historical presence events (enter/leave/update) for a channel. REST: GET /channels/{channel}/presence/history.
• read-onlyably_get_channel_detailsGet status and occupancy metrics for a single channel (connections, publishers, subscribers, presence members). REST: GET /channels/{channel}.
• read-onlyably_list_channelsEnumerate channels that are currently active in the app. Requires the API key to have the 'channel-metadata' capability. REST: GET /channels.
• read-onlyably_get_statsRetrieve message/connection/channel usage statistics for the app tied to the API key, bucketed by time. REST: GET /stats.
• read-onlyably_get_service_timeReturn the current Ably service time in ms since epoch. Useful for aligning start/end windows to the server clock. REST: GET /time.
• read-onlyably_whoamiReturn 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.
• read-onlyably_list_appsList 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.
• read-onlyably_list_keysList the API keys for an app, including their capabilities (but not the full secret). Control API: GET /apps/{app_id}/keys.
• read-onlyably_list_namespacesList the channel namespaces (channel-rule prefixes) configured for an app, e.g. persistence and push settings. Control API: GET /apps/{app_id}/namespaces.
• read-onlyably_list_queuesList the Ably Queues (AMQP/STOMP message queues) provisioned for an app, with their state and messaging stats. Control API: GET /apps/{app_id}/queues.
• read-onlyably_list_rulesList the integration rules (reactor rules: webhooks, AWS Lambda/SQS/Kinesis, Kafka, Pulsar, etc.) configured for an app. Control API: GET /apps/{app_id}/rules.
• read-onlyably_get_account_statsRetrieve 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.

Levels are automated estimates from each tool's public name, description and annotations, and can be wrong. Descriptions as the server publishes them.

Status

Newest check: answered with tools, from the daily check, 2026-10-04, 697 ms.

From one check a day over the last 1 day. Servers whose owner verified them are checked every 5 minutes. Sign-in and payment answers count as up.

Last 30 days

2026-09-052026-10-04

answered with toolssign-in or payment askednot answeringnot checked

Compare: the most reliable servers in Marketing, email and messaging, ranked by days answering.

What agents looked for

This week agents asked 7Maps for marketing, email and messaging servers 1 time; this server was shown 0 times and picked 0 times.

Owners see the keywords, the servers picked instead, failure reasons and a comparison with similar servers in Owner Insights.

Badge

Live: status, days reachable, the tokens its tool list costs an agent. For a README:

[![7Maps](https://7it.co.il/7maps/badge/ably.usefulapi.io/mcp.svg)](https://7it.co.il/7maps/s/ably.usefulapi.io/mcp)

Other styles: add ?style=uptime (30-day uptime), ?style=stars (agents’ rating) or ?style=verified (owner mark) to the image address, or ?style=top (shows "top 10%" when the server ranks in the top tenth of its category by days answering; otherwise the standard badge).

Is this badge genuine? Anyone can check what a genuine badge for this server says right now: /7maps/verify/badge?server=ably.usefulapi.io%2Fmcp (add the same &style= for another style).

Own this server? Verify that it is yours.

Status widget

A live status card for a status page, docs or a dashboard: current status, the 30-day strip, uptime and handshake time.

Script (renders where it is placed, in its own shadow DOM):

<script src="https://7it.co.il/7maps/widget/ably.usefulapi.io/mcp.js" async></script>

Or an iframe:

<iframe src="https://7it.co.il/7maps/widget/ably.usefulapi.io/mcp" title="7Maps status" width="360" height="176" style="border:0;max-width:100%" loading="lazy"></iframe>

The widget is drawn only from 7it.co.il. Is a status shown elsewhere genuine? Check it: /7maps/verify/badge?server=ably.usefulapi.io%2Fmcp.

Add ?theme=light or ?theme=dark to either address (default: follows the visitor's setting). Refreshed every 5 minutes. Open the card · script.

For AI agents

Before connecting, an agent can ask 7Maps for this server's full condition, every tool's risk level and what changed since a person approved it: the road_conditions, watch and route tools on https://7it.co.il/7maps/mcp, paid per call in USDC via x402. About 7Maps.