Drag vs Front API + MCP

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.

Front API + MCP 73

The MCP server is OAuth 2.1 with PKCE and read, write and send scopes. Core API tokens are scoped to shared or private resources, and partner apps use per-resource OAuth scopes. No Dynamic Client Registration, so you register a confidential client yourself (28). Sending needs its own scope, permissions are checked at call time against the teammate's role, and destructiveHint asks clients to confirm each user-visible write (18). Email bodies are customer-written and we found no injection guidance (0). Every MCP call is attributed to the authorising teammate, but we didn't find an API audit log (7). SOC 2 Type II, ISO 27001, a public HackerOne bug bounty and a security.txt without an Expires field (20).

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.

Front API + MCP 77

Atlassian Statuspage at frontstatus.com with 16 components, one of them API and integrations (20). Read from the history feed (robots.txt closes /api/). In the 90 days from 4 August it lists a delay in resource audit log events for one EU cell (15 August), 2 hours 51 minutes of degraded app performance (31 August), Office 365 delays for some customers in two US regions (14 September), Office 365 and Gmail delays in three regions for about 4.5 hours (23 September), 15 minutes of elevated API errors in us-west-2 (27 September), failures on a subset of custom SMTP channels (5 October) and an AI output backlog (6 October). Each was one region, one channel type or degraded performance, so all read as minor (20). Core API limits are 50, 100 and 200 requests a minute by plan, search at 40 per cent, partner integrations 120 a minute, and MCP 100, 200 and 300 tool calls a minute (15). 429 carries retry-after and every response has limit, remaining and reset headers, and the page tells clients to wait Retry-After seconds before safely retrying. Draft updates on MCP take a version token, but there's no idempotency key on REST writes (12). No uptime SLA found (0). Neither the developer page (updated 22 October) nor the help centre article (edited 8 October) labels the MCP server beta, and the Core API is generally available (10). 20+20+15+12+0+10 = 77.

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.

Front API + MCP 80

Closed service under a SaaS services agreement (15). The privacy notice (effective 1 July 2026), the data processing addendum (updated 1 July 2026, return or deletion at termination, 30 days' notice of a new subprocessor) and the subprocessor list (effective 13 July 2026) agree, but no retention periods are stated and nothing on AI training was found (18). Some reference pages mark endpoints deprecated with no date, and the 14 October API news post deprecates the two burst headers with removal on 1 February 2027. No written deprecation policy (10). The subprocessor list names each entity, its processing activity and the countries where it processes, with US or EU hosting by account region (20). 15+18+10+20 = 63.

Drag 43

47 MCP tools load by default, with no toolsets (5). Search and filter tools by label, assignee or status, and bulk moves; paging controls were not documented (10 of 20). REST errors return error and message with standard codes, and MCP error shapes weren't documented (8 of 20). Every tool sets readOnlyHint and destructiveHint, with sends marked destructive and open-world; no idempotency keys (15 of 20). One URL for the hosted server; the docs say official SDKs and a CLI are coming soon (5 of 15). 5 + 10 + 8 + 15 + 5 = 43.

Front API + MCP 67

27 MCP tools, 16 read, 10 write and send_message (15), plus 3 because the read, write and send scopes let an operator cut what a token can do (18). Core API lists page with a token and limit, with search queries for conversations and contacts (18). Errors are thinly documented in the spec (12). MCP write tools that change what users see carry destructiveHint, and update_draft and delete_draft fail if the draft changed since it was read. No idempotency key on REST writes (14). No official SDK for the Core API (5).

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.

Front API + MCP 60

The Core API spec was last updated on 30 October 2026 and the rate-limit page on 29 October (30). Three dated API news posts since 4 August (24 September, 13 and 14 October) and spec changes on 9 separate days (20). Closed service with a dated API news category and a developer Q&A forum in the same community, and support through the product. Response times weren't measured (10). No official Core API SDK (0). No package to assess (0). 30+20+10+0+0 = 60.

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.

Front API + MCP 81

OpenAPI 3.0 for the Core API in a public repo, 246 operations on 147 paths, plus Postman collections (25). llms.txt with about 440 lines of links and Markdown copies of pages (10). Every operation has a description, and the MCP page explains each tool and when to request the send scope (16). 51 enums and typed parameters in the spec (12). 414 examples, but only 11 error responses across 246 operations and no 429 in the spec (8). No API versioning scheme or policy (the spec says 1.0.0), but the developer community's API news category carries dated posts (14 and 13 October and 24 September 2026 among them), and the spec repository changed on 9 days since 4 August (10). 25+10+16+12+8+10 = 81.