Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Missive MCP by usefulapi

REMOTE · MISSIVE.USEFULAPI.IO

Read email/chat conversations, messages, contacts and teams; draft, send and update threads.

−59 this week 18 Trust /100

Last scanned (7 hours ago)

Scores higher than 4% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Communication

Trust breakdown (7 categories)

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
Transport & Reachability0
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.

What we tested

Checks we ran (4)

  • TLS certificate
  • HSTS header
  • DNSSEC
  • Transport

Checks we could not complete (7)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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 “assign_label_or_close_conversations” functional
    • New prompt “catch_up_on_the_latest_conversations” functional
    • New prompt “draft_or_send_an_email” functional
    • New prompt “find_contacts_and_add_a_new_one” functional
    • New prompt “read_a_whole_conversation” 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
Diagnostics

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://missive.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 missive.usefulapi.io. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
io. DS published 38690 8 Verified
usefulapi.io. No DS 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://missive.usefulapi.io/mcp Redirected 302 https://usefulapi.io/missive/
http (plaintext) http://missive.usefulapi.io/mcp Inconclusive 302 http://missive.usefulapi.io/mcp
MCP tools · 19 exposed · ~1,881 tokens

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 →

Tool Tokens
missive_create_contact ~106

Create a contact in the given contact book. Missive: POST /contacts.

NameTypeReqDescription
contact_bookstringyesThe contact book id to create the contact in (required).
first_namestring–First name.
infosarray–Contact info entries (email/phone/etc. objects).
last_namestring–Last name.
membershipsarray–Group/organization membership objects.
starredboolean–Whether the contact is starred.

No output schema declared.

No examples provided.

missive_create_draft ~241

Create a draft email/message. WARNING: setting send=true SENDS a real email immediately (send_at schedules it) instead of saving a draft. Attach to an existing thread with `conversation`. Missive: POST /drafts.

NameTypeReqDescription
add_assigneesarray–User ids to assign to the conversation.
add_shared_labelsarray–Shared label ids to apply.
bcc_fieldsarray–Bcc recipients.
bodystringyesThe message body (HTML) — required.
cc_fieldsarray–Cc recipients.
conversationstring–Attach the draft to an existing conversation id.
from_fieldobject–The sender ({address, name?}).
organizationstring–Organization id to send from.
referencesarray–Message-ID references (for threading).
sendboolean–If true, SEND the email immediately instead of saving a draft.
send_atnumber–Unix timestamp to schedule the send.
subjectstring–The subject line.
to_fieldsarray–Recipients ({address, name?}).

No output schema declared.

No examples provided.

missive_get_contact ~41

Get a single contact by id. Missive: GET /contacts/{id}.

NameTypeReqDescription
idstringyesThe resource id (a UUID-like string).

No output schema declared.

No examples provided.

missive_get_conversation ~43

Get a single conversation by id. Missive: GET /conversations/{id}.

NameTypeReqDescription
idstringyesThe resource id (a UUID-like string).

No output schema declared.

No examples provided.

missive_get_message ~60

Get a single message, including the full body. Missive: GET /conversations/{conversation_id}/messages/{id}.

NameTypeReqDescription
conversation_idstringyesThe conversation id the message belongs to.
idstringyesThe message id.

No output schema declared.

No examples provided.

missive_list_contact_books ~61

List contact books (address books). Missive: GET /contact_books.

NameTypeReqDescription
limitinteger–Max contact books to return (default 50, max 200).
offsetinteger–Number of records to skip (offset pagination).

No output schema declared.

No examples provided.

missive_list_contact_groups ~87

List contact groups or organizations within a contact book. Missive: GET /contact_groups.

NameTypeReqDescription
contact_bookstringyesThe contact book id (required).
kindstringyesWhich kind to list: "group" or "organization".
limitinteger–Max records to return.
offsetinteger–Number of records to skip (offset pagination).

No output schema declared.

No examples provided.

missive_list_contacts ~128

List contacts in a contact book. Missive: GET /contacts.

NameTypeReqDescription
contact_bookstringyesThe contact book id to list contacts from (required).
include_deletedboolean–Include deleted contacts.
limitinteger–Max contacts to return (default 50, max 200).
modified_sincenumber–Unix timestamp — only contacts modified since.
offsetinteger–Number of records to skip (offset pagination).
orderstring–Sort order (default "last_name").
searchstring–Free-text search over contacts.

No output schema declared.

No examples provided.

missive_list_conversation_comments ~81

List internal comments (team chat) on a conversation. Missive: GET /conversations/{id}/comments.

NameTypeReqDescription
idstringyesThe resource id (a UUID-like string).
limitinteger–Max records to return.
untilnumber–Unix timestamp cursor — return records older than this (offset-less pagination).

No output schema declared.

No examples provided.

missive_list_conversation_drafts ~79

List draft messages on a conversation. Missive: GET /conversations/{id}/drafts.

NameTypeReqDescription
idstringyesThe resource id (a UUID-like string).
limitinteger–Max records to return.
untilnumber–Unix timestamp cursor — return records older than this (offset-less pagination).

No output schema declared.

No examples provided.

missive_list_conversation_messages ~88

List the messages (emails) in a conversation. Missive: GET /conversations/{id}/messages.

NameTypeReqDescription
idstringyesThe resource id (a UUID-like string).
limitinteger–Max messages to return (default 10, max 10).
untilnumber–Unix timestamp cursor — return records older than this (offset-less pagination).

No output schema declared.

No examples provided.

missive_list_conversation_posts ~82

List posts (integration/app-generated items) on a conversation. Missive: GET /conversations/{id}/posts.

NameTypeReqDescription
idstringyesThe resource id (a UUID-like string).
limitinteger–Max records to return.
untilnumber–Unix timestamp cursor — return records older than this (offset-less pagination).

No output schema declared.

No examples provided.

missive_list_conversations ~268

List conversations (email/chat threads). Missive requires EXACTLY ONE mailbox-type filter — one of inbox / assigned / closed / flagged / snoozed / trashed / all / shared_label / team_inbox / team_all / organization. Missive: GET /conversations.

NameTypeReqDescription
allboolean–All conversations.
assignedboolean–Conversations assigned to you.
closedboolean–Closed conversations.
contact_organizationstring–Filter to a contact organization id.
emailstring–Filter to conversations involving this email address.
flaggedboolean–Flagged conversations.
inboxboolean–Conversations in your inbox.
limitinteger–Max conversations to return (default 25, max 50).
organizationstring–Filter to an organization id.
shared_labelstring–Conversations under a shared label id.
snoozedboolean–Snoozed conversations.
team_allstring–All of a team's conversations (team id).
team_inboxstring–Conversations in a team's inbox (team id).
trashedboolean–Trashed conversations.
untilnumber–Unix timestamp cursor — return records older than this (offset-less pagination).

No output schema declared.

No examples provided.

missive_list_organizations ~50

List organizations you belong to. Missive: GET /organizations.

NameTypeReqDescription
limitinteger–Max records to return.
offsetinteger–Number of records to skip (offset pagination).

No output schema declared.

No examples provided.

missive_list_responses ~62

List canned responses / templates. Missive: GET /responses.

NameTypeReqDescription
limitinteger–Max records to return.
offsetinteger–Number of records to skip (offset pagination).
organizationstring–Filter to an organization id.

No output schema declared.

No examples provided.

missive_list_shared_labels ~68

List shared labels (team-shared folders/tags). Missive: GET /shared_labels.

NameTypeReqDescription
limitinteger–Max records to return.
offsetinteger–Number of records to skip (offset pagination).
organizationstring–Filter to an organization id.

No output schema declared.

No examples provided.

missive_list_teams ~63

List teams in the organization(s). Missive: GET /teams.

NameTypeReqDescription
limitinteger–Max records to return.
offsetinteger–Number of records to skip (offset pagination).
organizationstring–Filter to an organization id.

No output schema declared.

No examples provided.

missive_list_users ~61

List users (team members). Missive: GET /users.

NameTypeReqDescription
limitinteger–Max records to return.
offsetinteger–Number of records to skip (offset pagination).
organizationstring–Filter to an organization id.

No output schema declared.

No examples provided.

missive_update_conversation ~212

Update a conversation — assign/unassign users, add/remove shared labels, close/reopen, move to inbox, or set subject/color/team. Missive: PATCH /conversations/{id}.

NameTypeReqDescription
add_assigneesarray–User ids to assign.
add_shared_labelsarray–Shared label ids to add.
add_to_inboxboolean–Move the conversation back to the inbox.
closeboolean–Close (archive) the conversation.
colorstring–Set the conversation color.
idstringyesThe resource id (a UUID-like string).
organizationstring–Organization id (context for the update).
remove_assigneesarray–User ids to unassign.
remove_shared_labelsarray–Shared label ids to remove.
reopenboolean–Reopen the conversation.
subjectstring–Set the conversation subject.
teamstring–Team id to move the conversation to.

No output schema declared.

No examples provided.

Install

How do I install the Missive MCP by usefulapi server?

Missive MCP by usefulapi is a hosted endpoint at https://missive.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 · missive.usefulapi.io

# add to Claude Code
claude mcp add --transport http io-usefulapi-missive 'https://missive.usefulapi.io/mcp'
Common questions

What is the Missive MCP by usefulapi server?

Missive MCP by usefulapi is listed in the public MCP registry as io.usefulapi/missive. Read email/chat conversations, messages, contacts and teams; draft, send and update threads. This page covers its hosted endpoint (https://missive.usefulapi.io/mcp).

Is the Missive MCP by usefulapi server safe to use?

Missive 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 Missive MCP by usefulapi server expose?

Missive MCP by usefulapi exposes 19 tools: missive_list_conversations, missive_get_conversation, missive_list_conversation_messages, missive_get_message, missive_list_conversation_comments, and 14 more. Their descriptions and schemas cost roughly 1,881 tokens of context every time the server is loaded.

Does the Missive MCP by usefulapi server require authentication?

Its publisher declares no required credentials for Missive 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 Missive MCP by usefulapi server still maintained?

Missive 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.

What did VerifyMCP test on the Missive MCP by usefulapi server?

VerifyMCP ran 4 checks on Missive MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about Missive MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.