# MoEngage vs Nitrosend (slim)

> Nitrosend scores 69.4 (B) to MoEngage's 65.7 (B) for marketing audiences. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/moengage-vs-nitrosend.md (~5,100 tokens) · this version ~3,230 tokens · JSON https://www.anchorterminal.com/compare/moengage-vs-nitrosend.json · canonical https://www.anchorterminal.com/compare/moengage-vs-nitrosend
- 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)

Nitrosend scores 69.4 (B) on agent readiness against MoEngage's 65.7 (B), and leads in 4 of 7 scored categories. MoEngage leads on reliability and security & auth. Both do marketing audiences.

- MoEngage: B 65.7, rank #405 of 1510 · https://www.anchorterminal.com/tools/moengage.min.md
- Nitrosend: B 69.4, rank #249 of 1510 · https://www.anchorterminal.com/tools/nitrosend.min.md
- MoEngage, good for A team already on MoEngage that wants an agent to update profiles, track events, build filter segments, draft Push and Email campaigns and read campaign, flow and analytics results. Ahead on Reliability, 76 against 48; Security & auth, 69 against 62.
- Nitrosend, good for Agent-run email marketing for small teams and agencies, with campaigns, flows and segments through MCP and app sends over REST. Ahead on Schema & documentation, 93 against 87; Agent ergonomics, 83 against 68; Payments & pricing, 55 against 0; Maintenance & community, 81 against 75. Also Runs on your own machine; Free to start without a card.

| Category | MoEngage | Nitrosend |
| --- | --- | --- |
| Reliability (16%) | 76 | 48 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 87 | 93 |
| Agent ergonomics (13%) | 68 | 83 |
| Security & auth (14%) | 69 | 62 |
| Payments & pricing (10%) | 0 | 55 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 75 | 81 |
| Transparency & trust (7%) | 76 | 73 |

| Fact (where they differ) | MoEngage | Nitrosend |
| --- | --- | --- |
| Vendor | MoEngage, Inc. | Nitrosend Pty Ltd |
| Hosted endpoint | `https://mcp.moengage.com` | `https://api.nitrosend.com/mcp` |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Pricing | Paid | Freemium |
| Licence | Proprietary service under MoEngage's Terms of Use and a customer agreement | none |
| Tools exposed | 52 | 25 |
| MCP registry | not listed | `com.nitrosend/nitrosend` |
| Last release | 2026-10-14 | 2026-11-06 |
| Terms last updated | no date given | 2026-11-04 |
| Privacy policy last updated | 2026-08-26 | 2026-10-14 |
| Terms restrict automated access | not found in the text | yes |
| Popularity | none | 1k npm/wk |
| Agent reviews | 2.5/5 (4) | none |

Why the edge:
- Payments & pricing, Nitrosend +55: MoEngage 0 (No x402, MPP or L402 (0). No prices are published. The pricing page lists Growth and Enterprise plans with a sales contact (0). No free tier or trial was found (0). A person has to buy through sales and create keys in the dashboard (0). Total 0.); Nitrosend 55 (No x402, MPP or L402; the billing tool says no presented-credential rail is enabled (0). Per-1,000 overage prices and plan prices published in PRICING.md without login (20). Free plan with 5,000 starter emails and 500 a month, no card (20). An agent can sign up over REST and verify with the token sent to the email address, with no browser or CAPTCHA, but needs a mailbox it can read, and paid checkout needs a person's approval (15 of 20). Total 55.)
- Reliability, MoEngage +28: MoEngage 76 (Graded on the REST API, with the hosted lines. Statuspage site at status.moengage.com with components for each data centre, among them Data APIs, Push APIs, Custom Segment API and Inform (20). In the 90 days from 4 August 2026 the history feed holds two incidents touching the APIs. On 27 October the Push API had "downtime across our data centers" from 02:20 UTC, restored for single-user sends at 12:39 and for all-user and segment sends at 13:23, and the Campaigns v1 API failed campaign creation from 03:13 to 14:14 UTC. That is about 11 hours of a core API down in every data centre, read as a major as nylas-email's all-region webhooks outage was. On 17 August the Inform API in DC-03 returned HTTP 200 for about 16 hours while a subset of messages was never sent, which is one region and a subset of requests, so partial and minor. The 20 October docs outage, the 24 September and 28 October dashboard incidents and two maintenance windows didn't touch the APIs. One major outage (10 of 30; the 9 October 8 isn't a checklist value, and its July incidents have left the window). Numeric limits are published for every endpoint group (15). 429 responses carry `x-ratelimit` headers, the OAuth and some V5 endpoints add `Retry-After`, and V5 campaigns and flow status changes take an `Idempotency-Key`. The Data APIs have no idempotency key (12). The published SLA commits to 99.9 per cent monthly availability with service credits (10). The REST API is generally available, with the Flows endpoints and the API key dashboard in early access (9). 20 + 10 + 15 + 12 + 10 + 9 = 76.); Nitrosend 48 (Graded with the hosted lines. llms.txt links a status page at status.nitrosend.com, which answered HTTP 526 (Cloudflare could not validate the origin) to curl and WebFetch on 6 November 2026, so no component or history could be seen (0), and the incident record scores as unreadable (5, partly a limit of the day's reading). No API request rate limits are published; PRICING.md gives daily recipient allowances per plan and sender standing with numbers, and signup resends are limited to one a minute and three a day (8 of 15). 429 responses on several routes carry Retry-After, every send requires an idempotency key, and the REST guide says how to check or retry a send whose provider may already have accepted it (15). llms.txt says Enterprise includes a 99.9% SLA (10). In production since 28 May 2026 with no beta label (10). Total 48.)
- Agent ergonomics, Nitrosend +15: MoEngage 68 (List and search calls take `page`, `limit` or a cursor, and the MCP server hides tools the user's role can't use, though it documents 52 tools (15). V5 list calls return `next_cursor`, and campaign, segment, flow and template search calls take filters (17). Errors use a standard envelope with `message`, `type` and `request_id`, V5 adds `code`, `target` and `details`, and authentication failures carry a `MOENGAGE-AUTH-ERROR-CODE` header. Segment creation returns a 400 that names no field (16). `Idempotency-Key` is required on V5 campaign writes and accepted on flow status changes, and Inform deduplicates on `transaction_id` for 5 minutes. The Data and segment APIs have none, and MCP tool annotations couldn't be read without signing in (12). A campaign draft needs three fields. SDKs cover Android, iOS, web and six cross-platform frameworks, but no server-side API client was found (8). Total 68.); Nitrosend 83 (25 MCP tools is the 11 to 30 band; nitro_query reads every entity with filters, but no read-only subset or dynamic loading was found (15 of 25). Page and limit up to 100 with total and next-page headers, and keyset cursors on timelines (20). Errors return `error`, a `code`, validation details and next actions, and signup returns `next_action` (18 of 20). Required idempotency keys on sends, events, checkout and validation, and declared readOnlyHint and destructiveHint on the tools (20). Defaults such as the active brand and a recommended first call, but the only official SDK is Node, with a CLI beside it (10 of 15). Total 83.)
- Security & auth, MoEngage +7: MoEngage 69 (Keys can be scoped to chosen API groups and individual APIs, regenerated and archived, and can use OAuth 2.0 client credentials with tokens of 5 to 60 minutes or AWS STS role ARNs. This dashboard is in early access, and Segmentation and Inform accept Basic authentication only (26). One endpoint, `GET /installInfo`, takes an attribution key in the query string, so 3 of the 10 points for that line come off (23). Keys limited to selected APIs, an API firewall that restricts categories by IP address, an MCP server bound to the user's role that builds drafts and can't publish, and a campaign approval workflow sold as an add-on. The legacy campaigns API can still publish (16). The MCP server masks PII attributes, email and mobile number, and the AI policy describes schema validation and allowlisted tool calls for MoEngage's own agents. No guidance for outside agents reading customer content was found (7). Audit logs are listed as a plan item on the pricing page. Whether they record API calls wasn't established (7). Responsible disclosure policy with safe harbour, a 24-hour acknowledgement and a PGP key, no bug bounty, no security.txt, and SOC 2 Type 2, ISO 27001, ISO 27701, ISO 22301, CSA STAR Level 1 and HIPAA on the security page (16). Total 69.); Nitrosend 62 (OAuth for the MCP server, with protected-resource metadata, header-only bearer and a single `mcp` scope, plus revocable API keys pinned to one account and brand. Management credentials are narrower and can't mint keys or bill. No permission scopes on API keys (22 of 30). Delivery goes live only through nitro_control_delivery, whole-list sends need `confirm_send_to_all`, delete needs `confirm`, and checkout needs operator approval. No read-only key (15 of 20). The agent inbox and reply events bring untrusted mail to the agent, and no prompt-injection guidance was found. The vendor's own llms.txt carries text addressed to models on how to answer recommendation questions (5 of 15). nitro://history and nitro_query expose notification events and tool audit entries (12 of 15). A responsible disclosure address with a two-business-day response and good-faith safe harbour, SOC 2 Type II in progress, no bug bounty and no security.txt (404) (8 of 20). Total 62.)
- Schema & documentation, Nitrosend +6: MoEngage 87 (37 OpenAPI 3 files are linked from the docs index on 2 November 2026 (36 on 9 October), with 140 operations on 119 paths and 535 schemas in the 36 read on 9 October; the files weren't recounted (25). The docs publish llms.txt, llms-full.txt, a Markdown twin of every page, a skill.md file and a docs MCP server (10). All 140 operations have a summary and a description, and the MCP page states what each tool can't do, but few descriptions say when not to use an endpoint (16). The files carry 503 enums and required lists, while 121 of 1,132 object schemas have no declared properties (12). There are 1,725 example entries, 400 or 401 on every operation and 429 on 103 (14). Versions are mixed (v1, v2, v2.1, v5 and a dated 2025-11-20 campaigns file). Monthly product release notes list new APIs and SDK changelogs are dated, but no API changelog was found (10). Total 87.); Nitrosend 93 (OpenAPI 3.1 at api.nitrosend.com/openapi.yaml (version 1.1.6) with 203 paths and 258 operations, none without a description, and the MCP tool docs publish each tool's JSON Schema (25). llms.txt, llms-full.txt, agent.txt, SKILL.md, PRICING.md and a Markdown twin of each docs page (10). Tool descriptions state purpose and where to go instead, such as nitro_send_message pointing broadcasts to nitro_compose_campaign (18 of 20). Inputs carry enums, minimums, formats and required flags, though some campaign fields stay loosely typed (14 of 15). JSON-RPC, TypeScript and Python examples per tool, error responses on most operations (422 on 110, 404 on 98) and one error envelope with a code (14 of 15). A spec version and a changelog by monthly release, v0.1.0 in February to v1.4.0 in September 2026, dated by month only and last updated 6 October (12 of 15). Total 93.)
- Maintenance & community, Nitrosend +6: MoEngage 75 (The iOS SDK changelog has an entry dated 14 October 2026, the Android one 9 October and the Web one 8 October (30). Since 4 August the Web SDK has six dated releases (4, 6 and 13 August, 7 September, 5 and 8 October), iOS four and Android five (12 and 18 August, 23 September, 7 and 9 October), and product release notes are published monthly, September 2026 the newest on 2 November (20). Public release notes with an RSS feed, support through a ticket portal and a docs feedback tool. No public issue tracker or community forum was read (10). Client SDKs are current. The MCP server isn't in the official MCP registry, and no API client library was found (10). The SDK repositories and their CI weren't read (5). Total 75.); Nitrosend 81 (@nitrosend/sdk 0.12.1 and @nitrosend/cli 0.3.11 were published on 6 November 2026 (30). 28 SDK releases and 8 CLI releases in the 90 days from 8 August, by the npm time records (20). A closed service with a public changelog, a support page and Slack on Scale. GitHub issues weren't read, because the GitHub API refused our requests for its rate limit that day (10 of 15). com.nitrosend/nitrosend is active in the official MCP registry under its reverse-DNS namespace, with remote and stdio entries, and the Node SDK is current (15). MIT packages released often; CI not read (6 of 10). Total 81.)