email-agent-mcp vs Unipile

email-agent-mcp 42

Apache-2.0 with a LICENSE file (30). SECURITY.md says tokens and mail are handled locally over stdio with no network listener, and the broker README says mail never reaches the broker and refresh tokens aren't stored. The broker has no published privacy policy (22 of 30). No deprecation policy (0). No telemetry was found in the README or package manifests, and none is stated either way (10 of 20). Total 62.

Unipile 72

Closed service with public terms under French law. The SDK and MCP repositories carry MIT licence files (15). The privacy policy of 28 September 2026 gives storage by API version and channel, deletion within 30 days of termination and a DPA on request. The security page says no data leaves the EU while the policy lists proxy sub-processors in the United States and Singapore, so the statements don't fully agree. A new FAQ on the security page says the non-EU proxies are optional encrypted transit points that can't read the data, while the privacy policy still lists them as sub-processors under transfer safeguards (20). The docs say v1 has no deprecation date, and no deprecation policy was found. The terms let changes take effect on publication (6). Eight sub-processors listed with country, data location and transfer safeguard, and hosting named as Scaleway and OVH in France (18).

email-agent-mcp 67

OAuth to the person's own provider with the scopes each profile needs, tokens in the OS keychain, and an observe profile with Microsoft read scopes only. Gmail uses gmail.readonly and gmail.compose, and its code exchange and refreshes relay through a UseJunior-hosted broker that holds the client secret and says it stores no refresh tokens (25 of 30). Send allowlists, delete off by default behind an operator variable and a caller flag, inbox rules that block forwarding and deletion, and protected system folders (20). Receive allowlists limit whose mail the agent acts on; no guidance on treating message bodies as untrusted was found (9 of 15). No log of tool calls beyond the mailbox's own history (3 of 15). SECURITY.md with private reporting and acknowledgement within 3 business days, semgrep in CI; no bug bounty or advisories (10 of 20). Total 67.

Unipile 42

One access token in X-API-KEY reaches every connected account, with no scopes in v1. End users connect Gmail and Outlook through OAuth on the customer's own app. The MCP page (updated 30 October 2026) no longer says headers can be passed as query parameters, and no documented query-string route for the token was found, so the 5 taken off on 8 October is restored (20). Google's gmail.modify scope can be left out and hosted auth accepts custom scopes, but there is no read-only token or confirmation step. Scoped keys are in the v2 beta only (6). Mail bodies are untrusted content and no injection guidance was found in the v1 docs. The v2 MCP page tells users to give the client a scoped key (2). The security page mentions logged and auditable internal access. No per-request log for the operator was found in the v1 docs (2). SOC 2 Type II with the report on request, annual third-party penetration tests and Google's CASA Tier 2, with no security.txt (404 on 4 November), disclosure policy or bug bounty found (12).

email-agent-mcp 50

Graded with the lines for local packages and stdio MCP servers. Installs from the official npm package email-agent-mcp with npx, CI runs on Node 20 (20). A CI workflow with Vitest tests, Codecov and a spec-coverage gate; the run results weren't readable through GitHub's API that day, so partial (20 of 25). Open crash and regression issues couldn't be read because GitHub's API refused our requests for its rate limit (0, unchecked). Semver tags from v0.1.7 to v0.5.0 and auto-categorised GitHub Releases as the changelog, with no breaking changes marked in what we read (10 of 15). Pre-1.0 (0). Total 50.

Unipile 72

Graded on the v1 REST API with the hosted lines. Status page at status.unipile.com on OpenStatus with components per provider and per API cluster and an events history (20). From 6 August to 4 November 2026 the history shows LinkedIn Classic Search returning incomplete results from 9 to 17 August, WhatsApp account connection unavailable for 3 hours on 17 August, the API-4 cluster unavailable for about 70 minutes on 20 August, v2 beta real-time sync degraded on 24 September, Instagram chat listing failing for 20 hours on 7 and 8 October, temporary 503 answers for part of API-4's requests during the 1 November migration, and the api46 server down for customers hosted on it from 19:38 to 23:13 UTC on 3 November. Each hit one provider, one cluster or one server, so minor only, as this run reads partial incidents (20). The 21 and 30 July platform incidents left the window. Unipile states no request limit of its own on v1 ("We don't enforce any limits on our side"), and the provider limits page gives provider figures such as 500 emails a day for Gmail and 5,000 recipients a day for Microsoft 365. Figures for limits other than the product's own take 10, as openai-decisions-api (10). On provider routes such as LinkedIn invitations, 429 is typed errors/too_many_requests with "Please try again later" and an optional retry_after field, while the mail references list no 429 and no backoff guidance was found. Sends accept an Idempotency-Key that returns the original result on a retry, and webhooks retry five times. Safe retries on the main write with partial 429 guidance take 12, as middesk (12). The terms say SLA commitments aren't in the standard offering and need a custom plan, with no SLA published for any tier (0). v1 is generally available (10). 20+20+10+12+0+10 = 72.

email-agent-mcp 60

Free, Apache-2.0 software with nothing to buy, scored 20 + 20 + 20 by the self-hosted rule. No payment protocol (0 of 40). Total 60.

Unipile 40

No x402, MPP or L402 (0). Per-account prices are public, from 55 dollars a month for up to 10 accounts down to 3.50 dollars an account above 5,000, with no charge per request (20). A 7-day trial with no card (20). A person has to sign up in a browser and connect each mailbox (0).

email-agent-mcp 79

27 tools in the full profile, the 11 to 30 band, plus the observe profile as a read-only subset (20 of 25). List and search tools filter and page; we read the tool table, not every parameter (16 of 20). Errors are sanitised and use stable reasons such as NOT_SUPPORTED, failing closed before a Gmail mutation (15 of 20). readOnlyHint and destructiveHint on the tools in source; sends take no idempotency key (16 of 20). One npx command and a setup wizard for OAuth and mailbox choice; TypeScript only (12 of 15). Total 79.

Unipile 73

meta_only drops bodies from mail lists and limit sizes the page. The MCP server has 5 compact tools (20). Cursor pagination, a full-text search and filters for folder, sender, recipient, thread and date (18). Errors carry title, detail and a typed type, with no retry guidance per type (14). Idempotency-Key on send only, not on drafts or updates, held at 14 as for a key on one route (knock 16, magicbell 14). The 8 October reading of the MCP annotations came from a tools/list call to the server, which this run treats as a probe, so it is dropped as evidence (14). Only account_id is required to list mail. The v1 SDK is Node only, and the Python client is for the v2 beta (7).

email-agent-mcp 84

v0.5.0 was tagged and published on 5 November 2026 (30). Nine npm releases in the 90 days from 8 August, v0.3.0 to v0.5.0 (20). Pull requests up to #234 merged in the history, all by the one maintainer; issue responses couldn't be read through GitHub's API that day (10 of 25). io.github.UseJunior/email-agent-mcp is in the official MCP registry with 0.5.0 marked latest (15). CI, commitlint, semgrep and Codecov workflows (9 of 10). Total 84.

Unipile 79

Every dated source of the vendor's own was counted. The v1 changelog's latest entry is dated 13 October 2026, 22 days before this check (30). In the 90 days from 6 August the changelog has that one entry, and the v2 beta Node SDK was tagged nine times (14 August to 29 October, v2.32.0 to v2.63.0), counted at half as SDK tags, which together reach three (20). A Slack community, live chat and detailed status updates, for a closed service (10). Listed in the official MCP registry as com.unipile/unipile-mcp 1.0.0 since 29 September 2026 (15). The v1 Node SDK's last tag is v1.9.3 from 21 May 2025, with Dependabot added in May 2026; npm wasn't reachable on 4 November (4).