Home / MCP registry index / io.usefulapi/ably
Ably MCP by usefulapi
io.usefulapi/ably in the official MCP registry.
Endpoint https://ably.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: MCP server for Ably — channel history, presence, occupancy, stats, publish, and app management.
We read its 15 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
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 ably_publish_message ably_whoami ably_list_apps ably_list_keys ably_list_namespaces ably_list_queues ably_list_rules ably_get_account_stats
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-usefulapi-ably)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.