# Drag vs Missive API + MCP (slim)

> Missive scores 53.5 (D) to Drag's 40 (E) for support conversations. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/drag-vs-missive.md (~4,750 tokens) · this version ~2,530 tokens · JSON https://www.anchorterminal.com/compare/drag-vs-missive.json · canonical https://www.anchorterminal.com/compare/drag-vs-missive
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Missive API + MCP scores 53.5 (D) on agent readiness against Drag's 40 (E), and leads in 5 of 7 scored categories. Drag leads on schema & documentation. Both do support conversations.

- Drag: E 40, rank #1330 of 1510 · https://www.anchorterminal.com/tools/drag.min.md
- Missive API + MCP: D 53.5, rank #945 of 1510 · https://www.anchorterminal.com/tools/missive.min.md
- Drag, good for Small teams running support@ or sales@ in Gmail who want an agent to triage, label, assign and draft replies. Ahead on Schema & documentation, 71 against 52. Also Runs on your own machine; Open source.
- Missive API + MCP, good for Small teams that already run their mail in Missive and want an agent to triage, label, post internal notes and draft replies for a person to send. Ahead on Reliability, 60 against 28; Security & auth, 61 against 23; Maintenance & community, 50 against 43; Transparency & trust, 77 against 49.

| Category | Drag | Missive API + MCP |
| --- | --- | --- |
| Reliability (16%) | 28 | 60 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 71 | 52 |
| Agent ergonomics (13%) | 43 | 46 |
| Security & auth (14%) | 23 | 61 |
| Payments & pricing (10%) | 30 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 43 | 50 |
| Transparency & trust (7%) | 49 | 77 |

| Fact (where they differ) | Drag | Missive API + MCP |
| --- | --- | --- |
| Kind | MCP server | HTTP API |
| Vendor | DragApp.com Ltd | Missive |
| Hosted endpoint | `https://app.dragapp.com/mcp` | `https://public.missiveapp.com/v1` |
| Transports | Streamable HTTP, stdio | HTTP, Streamable HTTP |
| Auth | API key | OAuth or key |
| Licence | none | Proprietary service under Missive's Terms and Conditions |
| Tools exposed | 47 | none |
| MCP registry | `com.dragapp/mcp-server` | not listed |
| Last release | 2026-08-13 | 2026-09-24 |
| Terms last updated | 2026-10-13 | 2024-04-15 |
| Privacy policy last updated | 2026-09-03 | 2026-03-27 |
| Terms restrict automated access | yes | not found in the text |

Why the edge:
- Security & auth, Missive API + MCP +38: Drag 23 (One API key per user that the docs say grants full access to the workspace, revocable in settings; the hosted server wraps it in an OAuth 2.1 flow with PKCE, but the key remains the access token (10). No read-only key or scopes; the server instructions tell the model to confirm sends when intent is unclear, and ChatGPT's plugin asks before sending (5 of 20). Tools return email and WhatsApp text from outside senders, and no prompt-injection guidance was found (0). No audit log of API or MCP actions found (0). Google CASA Tier 2, and the trust centre lists SOC 2 and GDPR, but no security.txt (404) or disclosure policy was found (8 of 20). 10 + 5 + 0 + 0 + 8 = 23.); Missive API + MCP 61 (The REST API takes a personal access token with no scopes that reaches every account the user can open, sent only in the `Authorization` header. The MCP server uses OAuth with PKCE, automatic client registration, the `resource` parameter, eight permissions and 30-day access that the user can revoke. Scored between the two (22). MCP read permissions are separate from write ones and drafting from sending, but the docs say MCP writes run immediately with no server-side confirmation, and admins cannot restrict apps or permissions (12). The MCP docs tell users to make the client ask before running tools and to check the redirect URL. No prompt-injection guidance was found for message content (4). A connected-apps list shows scopes, last IP and last use, API posts leave a visible trace, and the feature list claims an audit trail of every action. No per-call API log was found (7). security.txt is valid until 13 July 2027, there is a disclosure programme with discretionary rewards, and Missive states SOC 2 Type II with the report on request. No public advisories page was found (16).)
- Reliability, Missive API + MCP +32: Drag 28 (Graded as a hosted service on the MCP server at app.dragapp.com/mcp and REST API v2. No status page is linked and status.dragapp.com failed the TLS handshake (0). No readable incident history (5). The REST docs say rate limits apply without numbers; the hosted MCP server's source defaults to 60 calls a minute per key (5 of 15). The REST docs say to retry a 429 with exponential backoff, with no idempotency guidance for sends (8 of 15). No SLA found (0). Neither surface is labelled beta (10). 0 + 5 + 5 + 8 + 0 + 10 = 28.); Missive API + MCP 60 (Graded as a hosted service. status.missiveapp.com is a PagerDuty status page with eight components, one of them REST API, per the 8 October check, not re-read on 4 November because its robots.txt request answers with the status app's HTML page (20). The incident history was not read on either date (5). REST limits are 5 concurrent requests, 300 a minute and 900 per 15 minutes, and MCP limits are 60 a minute and 600 an hour per user (15). A 429 carries `Retry-After` and three `X-RateLimit` headers and the docs give pacing guidance, but no idempotency key or safe-retry guidance for draft and message writes was found (10). No SLA is published. The security FAQ lists uptime figures for 2020 to 2023 only, per the 8 October check (0). The REST API is generally available and the MCP server left beta on 28 August 2026 (10).)
- Transparency & trust, Missive API + MCP +28: Drag 49 (Closed service under terms naming DragApp.com Ltd, with the MCP server under MIT (20 of 30). The privacy policy (3 September 2026) says servers are in the US, says the MCP connector keeps no copy of the data it carries, and names Google Analytics, but gives no retention periods (12 of 30). No deprecation policy or dated notices found (0). Hosting at AWS in Virginia is stated and the trust centre has a subprocessor section we could not open past its root page (10 of 20). 20 + 12 + 0 + 10 = 42.); Missive API + MCP 77 (Closed service under Terms and Conditions last updated 15 April 2024, which name Heliom inc. and Quebec law (15). The privacy policy of 27 March 2026 says staff do not read user data without consent or a security need (per the 8 October check), the terms keep data retrievable for 30 days after termination, and a DPA is available on request. No general retention periods are given. The security page now names AWS and Crunchy Bridge, in line with the sub-processor list, where on 8 October it named Heroku. The line keeps its earlier partial value (20). No deprecation policy was found, and the terms let Missive modify or terminate API access with or without notice (4). The GDPR page, last updated 15 July 2025, lists 13 sub-processors with locations and an RSS feed, and the security FAQ says all servers run in AWS us-east-1, per the 8 October check (18).)
- Schema & documentation, Drag +19: Drag 71 (No OpenAPI or other contract for REST v2 was found. Every MCP tool carries a JSON input schema in the open-source server (20 of 25). llms.txt for the site (10). Tool descriptions say which ID to pass, which tool to call first and when WhatsApp free text fails, and the server instructions add tips (17 of 20). Inputs are typed in the schemas, with IDs as strings and few enums (10 of 15). The REST docs show request and response examples for 24 endpoints and a shared error shape with 401, 429 and 500 (9 of 15). REST is v2, but no changelog was found; versions are visible only on npm and in the repository (5 of 15). 20 + 10 + 17 + 10 + 9 + 5 = 71.); Missive API + MCP 52 (No OpenAPI or other machine-readable contract was found in the developer docs, and the MCP tool definitions were not read because mcp.missiveapp.com disallows every path in robots.txt (0). The docs publish llms.txt and a Markdown twin of every page (10). The endpoints reference covers 44 method and path forms and says when to use posts, drafts or the silent conversation update (14). Parameters are in tables with types, defaults, maximums and required marks, not in a schema (8). Request and response examples are plentiful, but errors are limited to a few 400 and 404 cases with no error format (8). The path is versioned `/v1` and the dated changelog names API changes, though the WhatsApp identifier change marked breaking in the docs has no changelog entry we found (12).)
- Maintenance & community, Missive API + MCP +7: Drag 43 (@dragapp/mcp-server 0.7.0 on npm on 13 August 2026, 85 days before this check; the repository had a commit on 6 November and its package.json reads 0.12.0 with no matching release (20). Only one dated release in the 90 days from 8 August, and no changelog (0). 43 commits since 6 July 2026 by the CTO; issues were not read (8 of 25). Domain-verified com.dragapp/mcp-server namespace, but the entry stops at 0.1.5 and lists only the stdio package, not the hosted remote (10 of 15). A secret-scan workflow and a tarball check before publish; no tests in CI (5 of 10). 20 + 0 + 8 + 10 + 5 = 43.); Missive API + MCP 50 (Graded on the REST API and MCP server, so changelog entries about app functions the API doesn't serve are not counted. The newest entry naming the API or the MCP server is version 11.36.0 on 24 September 2026, which made the MCP server available on trial, 41 days before this check. Versions 11.37.0 (8 October), 11.37.1 (20 October) and 11.38.0 (23 October) cover app functions only (20). Four dated entries since 6 August name API or MCP server changes, on 14 August (`add_default_signature` on drafts), 28 August (MCP server out of beta), 10 September (signature variables in drafts made through the API and MCP server) and 24 September (20). Support is by email, there is a public feedback board and the changelog names API fixes, with no public issue tracker (10). No official SDK was found (0). There is no package to assess (0).)