Home / MCP registry index / io.usefulapi/aircall
Aircall MCP by usefulapi
io.usefulapi/aircall in the official MCP registry.
Endpoint https://aircall.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: Read calls, contacts, users, teams and numbers; tag calls and create or update contacts.
We read its 25 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
aircall_ping aircall_get_company aircall_list_users aircall_get_user aircall_list_calls aircall_get_call aircall_search_calls aircall_list_numbers aircall_get_number aircall_list_contacts aircall_get_contact aircall_search_contacts aircall_list_tags aircall_get_tag aircall_list_teams aircall_get_team aircall_get_call_transcription aircall_get_call_sentiments aircall_get_call_topics aircall_get_call_summary aircall_get_call_action_items aircall_create_contact aircall_update_contact aircall_add_call_comment aircall_tag_call
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-usefulapi-aircall)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.