Aircall MCP by usefulapi
REMOTE · AIRCALL.USEFULAPI.IO
Read calls, contacts, users, teams and numbers; tag calls and create or update contacts.
Available components
Last scanned (3 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 “check_the_sentiment_and_topics_of_a_call” functional
- New prompt “look_up_add_or_update_a_contact” functional
- New prompt “review_recent_calls_by_date_number_or_tag” functional
- New prompt “see_your_agents_teams_and_phone_numbers” functional
- New prompt “summarize_a_call_and_list_its_follow_ups” functional
- New prompt “tag_a_call_or_add_a_note_to_it” 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://aircall.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 aircall.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://aircall.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/aircall/ |
| http (plaintext) | http://aircall.usefulapi.io/mcp | Inconclusive | 302 | http://aircall.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 →
aircall_add_call_comment Add call comment ~57
Add a comment / note to a call. Aircall REST: POST /calls/{id}/comments.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The comment text (required). |
| id | integer | yes | The call id to comment on. |
No output schema declared.
No examples provided.
aircall_create_contact Create contact ~136
Create a new contact in the shared address book. Aircall typically requires at least one of first_name / last_name / company_name. Aircall REST: POST /contacts.
| Name | Type | Req | Description |
|---|---|---|---|
| company_name | string | – | The contact's company name. |
| emails | array | – | Email addresses for the contact, each { label, value }. |
| first_name | string | – | The contact's first name. |
| information | string | – | Freeform notes about the contact. |
| last_name | string | – | The contact's last name. |
| phone_numbers | array | – | Phone numbers for the contact, each { label, value }. |
No output schema declared.
No examples provided.
aircall_get_call Get call ~56
Get a single call by id. Aircall REST: GET /calls/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| fetch_contact | boolean | – | If true, include the full contact details for the call. |
| id | integer | yes | The call id. |
No output schema declared.
No examples provided.
aircall_get_call_action_items Get call action items ~55
Get the AI-extracted action items / follow-ups from a call (Aircall AI Voice feature). Aircall REST: GET /calls/{id}/action_items.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | The call id. |
No output schema declared.
No examples provided.
aircall_get_call_sentiments Get call sentiments ~51
Get the AI-generated sentiment analysis of a call (Aircall AI Voice feature). Aircall REST: GET /calls/{id}/sentiments.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | The call id. |
No output schema declared.
No examples provided.
aircall_get_call_summary Get call summary ~48
Get the AI-generated summary of a call (Aircall AI Voice feature). Aircall REST: GET /calls/{id}/summary.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | The call id. |
No output schema declared.
No examples provided.
aircall_get_call_topics Get call topics ~49
Get the AI-detected topics of a call (Aircall AI Voice feature). Aircall REST: GET /calls/{id}/topics.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | The call id. |
No output schema declared.
No examples provided.
aircall_get_call_transcription Get call transcription ~50
Get the AI-generated transcription of a call (Aircall AI Voice feature). Aircall REST: GET /calls/{id}/transcription.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | The call id. |
No output schema declared.
No examples provided.
aircall_get_company Get company ~33
Get details of the authenticated Aircall company (name, plan, usage). Aircall REST: GET /company.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
aircall_get_contact Get contact ~37
Get a single contact by id. Aircall REST: GET /contacts/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | The contact id. |
No output schema declared.
No examples provided.
aircall_get_number Get number ~38
Get a single phone number by id. Aircall REST: GET /numbers/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | The number id. |
No output schema declared.
No examples provided.
aircall_get_tag Get tag ~37
Get a single tag by id. Aircall REST: GET /tags/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | The tag id. |
No output schema declared.
No examples provided.
aircall_get_team Get team ~37
Get a single team by id. Aircall REST: GET /teams/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | The team id. |
No output schema declared.
No examples provided.
aircall_get_user Get user ~40
Get a single user (agent) by id. Aircall REST: GET /users/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | The user id. |
No output schema declared.
No examples provided.
aircall_list_calls List calls ~151
List calls, optionally filtered by a creation-date window and ordered. Aircall REST: GET /calls.
| Name | Type | Req | Description |
|---|---|---|---|
| fetch_contact | boolean | – | If true, include the full contact details of each call. |
| from | string | – | Minimal creation date — a UNIX timestamp or ISO 8601 string. |
| order | string | – | Sort order by creation date — 'asc' or 'desc' (default asc). |
| page | integer | – | 1-based page number to fetch (default 1). |
| per_page | integer | – | Results per page (default 20, max 50). |
| to | string | – | Maximal creation date — a UNIX timestamp or ISO 8601 string. |
No output schema declared.
No examples provided.
aircall_list_contacts List contacts ~135
List contacts in the shared address book, optionally by creation-date window and order. Aircall REST: GET /contacts.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Minimal creation date — a UNIX timestamp or ISO 8601 string. |
| order | string | – | Sort order by creation date — 'asc' or 'desc' (default asc). |
| page | integer | – | 1-based page number to fetch (default 1). |
| per_page | integer | – | Results per page (default 20, max 50). |
| to | string | – | Maximal creation date — a UNIX timestamp or ISO 8601 string. |
No output schema declared.
No examples provided.
aircall_list_numbers List numbers ~72
List the phone numbers owned by the company (id, name, digits, country). Aircall REST: GET /numbers.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | 1-based page number to fetch (default 1). |
| per_page | integer | – | Results per page (default 20, max 50). |
No output schema declared.
No examples provided.
aircall_list_tags List tags ~67
List the company's call tags (id, name, color). Aircall REST: GET /tags.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | 1-based page number to fetch (default 1). |
| per_page | integer | – | Results per page (default 20, max 50). |
No output schema declared.
No examples provided.
aircall_list_teams List teams ~64
List the company's teams and their members. Aircall REST: GET /teams.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | 1-based page number to fetch (default 1). |
| per_page | integer | – | Results per page (default 20, max 50). |
No output schema declared.
No examples provided.
aircall_list_users List users ~74
List users (agents) in the Aircall company (id, name, email, availability). Aircall REST: GET /users.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | 1-based page number to fetch (default 1). |
| per_page | integer | – | Results per page (default 20, max 50). |
No output schema declared.
No examples provided.
aircall_ping Ping ~31
Health check — verify the API is reachable and the credentials are valid. Aircall REST: GET /ping.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
aircall_search_calls Search calls ~87
Search calls by a free-text term (e.g. phone number, tag, direction). Aircall REST: GET /calls/search.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | 1-based page number to fetch (default 1). |
| per_page | integer | – | Results per page (default 20, max 50). |
| q | string | – | Search term to match calls against. |
No output schema declared.
No examples provided.
aircall_search_contacts Search contacts ~87
Search contacts by a free-text term (e.g. name, phone number, email). Aircall REST: GET /contacts/search.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | 1-based page number to fetch (default 1). |
| per_page | integer | – | Results per page (default 20, max 50). |
| q | string | – | Search term to match contacts against. |
No output schema declared.
No examples provided.
aircall_tag_call Tag call ~75
Apply tags to a call by tag id (get ids from aircall_list_tags). Aircall REST: POST /calls/{id}/tags.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | The call id to tag. |
| tag_ids | array | yes | Ids of the tags to apply (from aircall_list_tags) (required). |
No output schema declared.
No examples provided.
aircall_update_contact Update contact ~138
Update fields on an existing contact. Only provided fields are changed. Aircall REST: PUT /contacts/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| company_name | string | – | The contact's company name. |
| emails | array | – | Replace the contact's email addresses, each { label, value }. |
| first_name | string | – | The contact's first name. |
| id | integer | yes | The contact id to update. |
| information | string | – | Freeform notes about the contact. |
| last_name | string | – | The contact's last name. |
| phone_numbers | array | – | Replace the contact's phone numbers, each { label, value }. |
No output schema declared.
No examples provided.
How do I install the Aircall MCP by usefulapi server?
Aircall MCP by usefulapi is a hosted endpoint at https://aircall.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 · aircall.usefulapi.io
claude mcp add --transport http io-usefulapi-aircall 'https://aircall.usefulapi.io/mcp'
What is the Aircall MCP by usefulapi server?
Aircall MCP by usefulapi is listed in the public MCP registry as io.usefulapi/aircall. Read calls, contacts, users, teams and numbers; tag calls and create or update contacts. This page covers its hosted endpoint (https://aircall.usefulapi.io/mcp).
Is the Aircall MCP by usefulapi server safe to use?
Aircall 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 Aircall MCP by usefulapi server expose?
Aircall MCP by usefulapi exposes 25 tools: aircall_ping, aircall_get_company, aircall_list_users, aircall_get_user, aircall_list_calls, and 20 more. Their descriptions and schemas cost roughly 1,705 tokens of context every time the server is loaded.
Does the Aircall MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Aircall 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 Aircall MCP by usefulapi server still maintained?
Aircall 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.