io.usefulapi/bird
REMOTE · BIRD.USEFULAPI.IO · SCANNED SEP 20
Read SMS, WhatsApp, email, contacts and audiences from your Bird workspace, plus safe CRM writes.
Available components
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 Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement. 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1080 tokens (~67/item across 16 items; 16 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.usefulapi/bird MCP server?
io.usefulapi/bird is a hosted endpoint at https://bird.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 · bird.usefulapi.io
claude mcp add --transport http io-usefulapi-bird 'https://bird.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-bird": {
"url": "https://bird.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-bird": {
"type": "http",
"url": "https://bird.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-bird] url = "https://bird.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-bird": {
"type": "remote",
"url": "https://bird.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-bird --url 'https://bird.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-bird:
url: "https://bird.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-bird": {
"Transport": "http",
"Url": "https://bird.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-bird -t streamable-http -u 'https://bird.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-bird": {
"type": "http",
"url": "https://bird.usefulapi.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 −10
- Stability: pass → 0.30 functional
- 17 Sept 26 +57
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: behind authorisation → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 16 Sept 26 +10
- Endpoint reachability: not serving MCP → behind authorisation ▼ security
- Transport: unverified → pass ▲ security
- Tool safety: Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools. security
- Tool coverage: Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools. functional
- Schema quality: Schema blocked by authentication: the endpoint requires auth we don't have to read it. functional
- Capabilities: Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. functional
- 13 Sept 26 −10
- Endpoint reachability: behind authorisation → not serving MCP ▼ security
- Transport: pass → unverified ▼ security
- Tool safety: Tool safety not yet verified: we couldn't read the endpoint's tools. security
- Tool coverage: Tool coverage not yet verified: we couldn't read the endpoint's tools. functional
- Capabilities: Capabilities not yet verified: we couldn't read the endpoint's capabilities. functional
- Schema quality: Schema not yet verified: we couldn't read the endpoint's schema. functional
- 12 Sept 26 −58
- Endpoint reachability: reachable → behind authorisation ▼ security
- Authorization: pass → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: Schema blocked by authentication: the endpoint requires auth we don't have to read it. functional
- 11 Sept 26 +1
- Stability: 0.97 → pass security
- 10 Sept 26 +54
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Schema quality: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → pass ▲ functional
- Schema quality: unverified → good ▲ functional
- First check of Destructive annotations: pass functional
- Stability: fail → 0.97 functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day 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 20 Sept 2026 · Probed https://bird.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 | 14 Sept 2026 | 13 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 69fd8a2fc0b230250e9a934d076555be |
| SANs: usefulapi.io, bird.usefulapi.io, *.bird.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 bird.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://bird.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"
Bearer realm="OAuth", resource_metadata="https://bird.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"Protected resource metadata
| Document | https://bird.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://bird.usefulapi.io/mcp |
| Authorisation server | https://bird.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://bird.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://bird.usefulapi.io/mcp | Inconclusive | 401 |
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 →
bird_create_audience Create an audience ~87
Creates an audience (contact list) in Bird — additive, sends no message. Static audiences start empty. Bird API: POST /v1/audiences.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Longer description of who this audience is. |
| name | string | yes | Display name for the audience. |
| type | string | – | How members are determined. Only `static` is generally available. |
No output schema declared.
No examples provided.
bird_create_contact Create a contact ~133
Creates a contact (CRM record) in Bird — additive, sends no message. Contacts are unique by email. Bird API: POST /v1/contacts.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | Custom property values. Each key must be a property created via the contact-properties API; values match the property's declared type. |
| string | yes | The contact's email address (unique within the workspace). | |
| external_id | string | – | Your own identifier for this contact (unique within the workspace). |
| first_name | string | – | The contact's first name. |
| last_name | string | – | The contact's last name. |
No output schema declared.
No examples provided.
bird_get_audience Get an audience ~42
Fetch a single audience by id. Bird API: GET /v1/audiences/{audience_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| audience_id | string | yes | Audience id. |
No output schema declared.
No examples provided.
bird_get_contact Get a contact ~39
Fetch a single contact by id. Bird API: GET /v1/contacts/{contact_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | string | yes | Contact id. |
No output schema declared.
No examples provided.
bird_get_email_message Get an email message ~42
Fetch a single email message by id. Bird API: GET /v1/email/messages/{message_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| message_id | string | yes | Email message id. |
No output schema declared.
No examples provided.
bird_get_sms_message Get an SMS message ~43
Fetch a single SMS message by id. Bird API: GET /v1/sms/messages/{message_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| message_id | string | yes | SMS message id. |
No output schema declared.
No examples provided.
bird_get_whatsapp_message Get a WhatsApp message ~47
Fetch a single WhatsApp message by id. Bird API: GET /v1/whatsapp/messages/{message_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| message_id | string | yes | WhatsApp message id. |
No output schema declared.
No examples provided.
bird_list_audience_contacts List an audience's contacts ~89
List the contacts that belong to a static audience, as a cursor page. Bird API: GET /v1/audiences/{audience_id}/contacts.
| Name | Type | Req | Description |
|---|---|---|---|
| audience_id | string | yes | Audience id. |
| limit | integer | – | Max items per page. |
| starting_after | string | – | Cursor from a previous response's `next_cursor` field, to fetch the next page. |
No output schema declared.
No examples provided.
bird_list_audiences List audiences ~76
List audiences (contact lists) in the workspace, newest first, as a cursor page. Bird API: GET /v1/audiences.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max items per page. |
| starting_after | string | – | Cursor from a previous response's `next_cursor` field, to fetch the next page. |
No output schema declared.
No examples provided.
bird_list_contact_properties List contact properties ~69
List the custom contact-property definitions (schema) for the workspace. Bird API: GET /v1/contact-properties.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max items per page. |
| starting_after | string | – | Cursor from a previous response's `next_cursor` field, to fetch the next page. |
No output schema declared.
No examples provided.
bird_list_contacts List contacts ~73
List contacts (CRM records) in the workspace, newest first, as a cursor page. Bird API: GET /v1/contacts.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max items per page. |
| starting_after | string | – | Cursor from a previous response's `next_cursor` field, to fetch the next page. |
No output schema declared.
No examples provided.
bird_list_email_messages List email messages ~72
List email messages sent from the workspace, newest first, as a cursor page. Bird API: GET /v1/email/messages.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max items per page. |
| starting_after | string | – | Cursor from a previous response's `next_cursor` field, to fetch the next page. |
No output schema declared.
No examples provided.
bird_list_sms_messages List SMS messages ~78
List SMS messages (inbound + outbound) for the workspace, newest first, as a cursor page. Bird API: GET /v1/sms/messages.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max items per page. |
| starting_after | string | – | Cursor from a previous response's `next_cursor` field, to fetch the next page. |
No output schema declared.
No examples provided.
bird_list_sms_templates List SMS templates ~75
List the SMS templates available to the workspace (Bird built-ins + your own). Bird API: GET /v1/sms/templates.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter by category. |
| language | string | – | Keep only templates in this BCP-47 language tag. |
| scope | string | – | Filter by scope. |
No output schema declared.
No examples provided.
bird_list_whatsapp_messages List WhatsApp messages ~81
List WhatsApp messages (inbound + outbound) for the workspace, newest first, as a cursor page. Bird API: GET /v1/whatsapp/messages.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max items per page. |
| starting_after | string | – | Cursor from a previous response's `next_cursor` field, to fetch the next page. |
No output schema declared.
No examples provided.
bird_list_whatsapp_templates List WhatsApp templates ~34
List the WhatsApp message templates available to the workspace. Bird API: GET /v1/whatsapp/templates.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the io.usefulapi/bird MCP server?
io.usefulapi/bird is an MCP server listed in the public MCP registry as io.usefulapi/bird. Read SMS, WhatsApp, email, contacts and audiences from your Bird workspace, plus safe CRM writes. This page covers its hosted endpoint (https://bird.usefulapi.io/mcp).
Is the io.usefulapi/bird MCP server safe to use?
io.usefulapi/bird scores 76 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 io.usefulapi/bird MCP server expose?
io.usefulapi/bird exposes 16 tools: bird_list_contacts, bird_get_contact, bird_list_contact_properties, bird_list_audiences, bird_get_audience, and 11 more. Their descriptions and schemas cost roughly 1,080 tokens of context every time the server is loaded.
Does the io.usefulapi/bird MCP server require authentication?
Yes. io.usefulapi/bird asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.usefulapi/bird MCP server still maintained?
io.usefulapi/bird is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.