Endpoints: 28,729MCP servers: 18,413Payout addresses: 2,070Paid calls: 1,521Letters: 13Defects: 1,321counted 2 min ago
teppi

MCP serverio.usefulapi/ably

MCP server for Ably — channel history, presence, occupancy, stats, publish, and app management.
UNRATEDActivestreamable-httpably.usefulapi.io

Overview

Score?
UNRATED 0.688
of what a free look can see, on 32 looks
Looks
35
last 10 hr ago
Tools
15
changed 3 days ago

More info

URL
ably.usefulapi.io/mcp
streamable-http
Says it is
ably-mcp 1.5.1
protocol 2025-06-18
In the record since
32 days ago

Among servers18,413 with a card

0median 0.606 · this server 0.688 · highest on record 0.8561

Toolsfrom sha256:766e278450…511c87 · +0 −0 3 days ago

The tools this server lists, read out of the definition it returned
ToolSchema
ably_get_account_stats
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 /acco
input · no output
ably_get_channel_details
Get status and occupancy metrics for a single channel (connections, publishers, subscribers, presence members). REST: GET /channels/{channel}.
input · no output
ably_get_channel_history
Retrieve historical messages published to a channel, newest-first by default. REST: GET /channels/{channel}/messages.
input · no output
ably_get_presence
List the members currently present on a channel (who is online now). REST: GET /channels/{channel}/presence.
input · no output
ably_get_presence_history
Retrieve historical presence events (enter/leave/update) for a channel. REST: GET /channels/{channel}/presence/history.
input · no output
ably_get_service_time
Return the current Ably service time in ms since epoch. Useful for aligning start/end windows to the server clock. REST: GET /time.
input · no output
ably_get_stats
Retrieve message/connection/channel usage statistics for the app tied to the API key, bucketed by time. REST: GET /stats.
input · no output
ably_list_apps
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/{ac
input · no output
ably_list_channels
Enumerate channels that are currently active in the app. Requires the API key to have the 'channel-metadata' capability. REST: GET /channels.
input · no output
ably_list_keys
List the API keys for an app, including their capabilities (but not the full secret). Control API: GET /apps/{app_id}/keys.
input · no output
ably_list_namespaces
List the channel namespaces (channel-rule prefixes) configured for an app, e.g. persistence and push settings. Control API: GET /apps/{app_id}/namespaces.
input · no output
ably_list_queues
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.
input · no output
ably_list_rules
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.
input · no output
ably_publish_message
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 call
input · no output
ably_whoami
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 · no output
Verify it yourselfnpx teppi-check https://ably.usefulapi.io/mcpcurl -s https://api.teppi.xyz/v1/trust/mcp/mcs_01M1FZ2PH6GAS4N42HXCCY2WWT