{ "data": { "similar": [ { "grade": "BB", "json": "https://www.anchorterminal.com/tools/customer-io.json", "name": "Customer.io", "score": 75.6, "shared": [ "marketing.profiles", "marketing.events", "marketing.segments", "marketing.campaigns", "marketing.journeys", "email.send", "email.templates" ], "slug": "customer-io" }, { "grade": "B", "json": "https://www.anchorterminal.com/tools/nitrosend.json", "name": "Nitrosend", "score": 69.4, "shared": [ "marketing.profiles", "marketing.events", "marketing.segments", "marketing.campaigns", "marketing.journeys", "email.send", "email.templates" ], "slug": "nitrosend" }, { "grade": "BB", "json": "https://www.anchorterminal.com/tools/klaviyo.json", "name": "Klaviyo API + MCP", "score": 73.8, "shared": [ "marketing.profiles", "marketing.events", "marketing.segments", "marketing.campaigns", "marketing.journeys", "email.templates" ], "slug": "klaviyo" }, { "grade": "B", "json": "https://www.anchorterminal.com/tools/omnisend.json", "name": "Omnisend", "score": 65.8, "shared": [ "marketing.profiles", "marketing.events", "marketing.segments", "marketing.campaigns", "marketing.journeys", "email.templates" ], "slug": "omnisend" }, { "grade": "B", "json": "https://www.anchorterminal.com/tools/moengage.json", "name": "MoEngage", "score": 65.7, "shared": [ "marketing.profiles", "marketing.events", "marketing.segments", "marketing.campaigns", "marketing.journeys", "email.templates" ], "slug": "moengage" }, { "grade": "C", "json": "https://www.anchorterminal.com/tools/mailchimp-marketing.json", "name": "Mailchimp Marketing API", "score": 60.2, "shared": [ "marketing.profiles", "marketing.events", "marketing.segments", "marketing.campaigns", "marketing.journeys", "email.templates" ], "slug": "mailchimp-marketing" } ], "tool": { "slug": "sequenzy", "name": "Sequenzy", "vendor": "Nic Tech Solutions, LLC", "vendorUrl": "https://www.sequenzy.com", "kind": "http-api", "category": "lifecycle-marketing", "summary": "Sequenzy is an email marketing and lifecycle automation platform for SaaS and ecommerce teams, with sequences, campaigns, transactional email, an agent inbox, push and SMS. It has a REST API, an MCP server, a CLI and a TypeScript SDK.", "url": "https://www.anchorterminal.com/tools/sequenzy", "markdownUrl": "https://www.anchorterminal.com/tools/sequenzy.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/sequenzy.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/sequenzy.json", "dns": "sequenzy.grade.anchorterminal.com", "repo": "https://github.com/Sequenzy/mcp", "transports": [ "http", "streamable-http", "stdio" ], "remoteUrl": "https://api.sequenzy.com/v1/mcp", "packages": [ { "registry": "npm", "name": "sequenzy" }, { "registry": "npm", "name": "@sequenzy/mcp" }, { "registry": "npm", "name": "@sequenzy/cli" } ], "auth": "mixed", "authNotes": "Workspace API keys (`seq_live_`) and account keys (`seq_user_`) sent as Bearer tokens, each with permission scopes such as `transactional:send`, `subscribers:tag` and explicit `*:delete`, and presets including read-only and drafts-only. Account keys keep the user's workspace role. Agents can also register through the `service_auth` OAuth flow, where the user confirms a code in a Sequenzy browser page.", "pricing": "freemium", "pricingNotes": "Free plan of 2,500 emails a month with unlimited contacts and API, MCP and CLI access, no card, with a Sequenzy footer. Paid plans by monthly email volume, $19 for 15,000, $29 for 30,000, $49 for 60,000, $99 for 120,000, up to $2,999 for 5 million. SMS add-on $16 a month with 1,000 credits.", "priceSummary": "$19 / mo", "where": "both", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in llms.txt, auth.md, the pricing page or the OpenAPI spec (checked 2026-11-06).", "endpoints": [] }, "toolCount": 306, "popularity": { "githubStars": null, "npmWeekly": 2363, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://docs.sequenzy.com", "llmsTxt": "https://www.sequenzy.com/llms.txt", "openapi": "https://docs.sequenzy.com/openapi.yaml", "registryName": "io.github.polnikale/sequenzy-mcp", "capabilities": [ "marketing.profiles", "marketing.events", "marketing.segments", "marketing.campaigns", "marketing.journeys", "email.send", "email.templates", "email.inbound" ], "tags": [ "hosted", "closed-source", "mcp", "remote-mcp", "mcp-registry", "oauth", "api-key", "openapi", "llms-txt", "webhooks", "idempotency", "smtp", "sms", "no-card", "free-tier", "typescript", "cli", "no-status-page" ], "lastRelease": "2026-11-06", "graded": true, "anchor": { "graded": true, "score": 63.7, "grade": "B", "agentReady": false, "rank": 504, "ranked": true, "rankOf": 1486, "categoryRank": 6, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 69, "maintenance": 78, "payments": 40, "reliability": 38, "schema": 95, "security": 67, "transparency": 67 }, "pending": [ "performance", "tasks" ], "breakdown": [ { "key": "reliability", "name": "Reliability", "weight": 16, "effectiveWeight": 20, "score": 38, "points": 7.6, "reason": "Graded with the hosted lines. No status page was found; none is linked from the site, llms.txt or docs, and status.sequenzy.com doesn't resolve (0). With no history to read, the incident line takes 5. 429 responses carry RateLimit-Limit and RateLimit-Remaining headers for a per-minute policy, and some routes state numbers (20 requests a minute per workspace for AI copy), but no table of limits per key was found (8 of 15). 429s carry Retry-After, sends take an `Idempotency-Key`, a reused key with a different body returns IDEMPOTENCY_KEY_REUSED, and the MCP docs say a retry hint alone doesn't make a write safe to repeat (15). No SLA found (0). No beta label on the API or MCP server (10). Total 38.", "checked": "2026-11-06" }, { "key": "performance", "name": "Performance", "weight": 10, "effectiveWeight": 0, "pending": true, "points": 0, "reason": "Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes." }, { "key": "schema", "name": "Schema \u0026 documentation", "weight": 13, "effectiveWeight": 16.25, "score": 95, "points": 15.44, "reason": "OpenAPI 3.1 at docs.sequenzy.com/openapi.yaml with 349 paths and 475 operations, all described (25). llms.txt on both hosts, llms-full.txt, auth.md, agents.md and Markdown twins of the docs (10). Operation and tool descriptions give purpose, the scope each needs and the alternative, such as the deprecated generate-sequence alias (18 of 20). Typed inputs, and tools reject undeclared arguments with an error naming the supported ones (13 of 15). Errors on nearly every operation (401 on 442, 404 on 330, 400 on 290) with examples, and a structured error with code, `howToFix` and `docsUrl` for tools (14 of 15). Version in the path and spec, and a dated changelog (15). Total 95.", "checked": "2026-11-06" }, { "key": "ergonomics", "name": "Agent ergonomics", "weight": 13, "effectiveWeight": 16.25, "score": 69, "points": 11.21, "reason": "The MCP tool reference lists about 306 tools, the over-30 band, and no toolsets, tool search or dynamic loading was found (5 of 25). List endpoints paginate and filter, and contact timelines use cursors (20). Errors carry a code, a human message, a fix and a docs link, with `retryAfterSeconds` when the API sent Retry-After (20). Idempotency keys on sends and event imports; MCP readOnlyHint and destructiveHint annotations weren't found in the published reference (14 of 20). Sensible defaults with a selected workspace; one official SDK (TypeScript) plus a CLI (10 of 15). Total 69.", "checked": "2026-11-06" }, { "key": "security", "name": "Security \u0026 auth", "weight": 14, "effectiveWeight": 17.5, "score": 67, "points": 11.73, "reason": "Workspace and account API keys with fine-grained permission scopes, presets and explicit `*:delete` rights, revocable in settings, plus an OAuth `service_auth` flow for agents with user confirmation (30). Read-only and drafts-only presets let an agent prepare mail without sending, and account keys keep the user's workspace role (20). The agent inbox and reply tracking give the agent inbound mail, and no prompt-injection guidance was found in the MCP, permissions or inbox docs (4 of 15). The DPA lists administrative audit logs and MCP events report replies and bounces; no per-call API log for the customer was found (8 of 15). A responsible disclosure address on the security page, no security.txt (404), bug bounty or certification (5 of 20). Total 67.", "checked": "2026-11-06" }, { "key": "payments", "name": "Payments \u0026 pricing", "weight": 10, "effectiveWeight": 12.5, "score": 40, "points": 5, "reason": "No x402, MPP or L402 (0). Prices are public as volume tiers from $19 for 15,000 emails to $2,999 for 5 million, without a per-email overage rate (10 of 20). Free plan of 2,500 emails a month with no card (20). Agents can register through `service_auth`, but the user has to confirm a code in a Sequenzy browser page, and plan payment is through Stripe (10 of 20). Total 40.", "checked": "2026-11-06" }, { "key": "tasks", "name": "Task success", "weight": 10, "effectiveWeight": 0, "pending": true, "points": 0, "reason": "Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored." }, { "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7, "effectiveWeight": 8.75, "score": 78, "points": 6.83, "reason": "sequenzy 2.1.56, @sequenzy/mcp 0.0.246 and @sequenzy/cli 0.0.202 were all published on 6 November 2026 (30). 18 SDK, 105 MCP and 93 CLI releases in the 90 days from 8 August, and dated changelog entries on most days (20). A closed service with a public changelog and support answered by the cofounders per the about page. GitHub issues weren't read, as the GitHub API refused our requests for its rate limit (12 of 15). Listed in the official MCP registry as io.github.polnikale/sequenzy-mcp, but the entry is at 0.0.36 against npm's 0.0.246, and the TypeScript SDK is current (10 of 15). MIT packages released daily, the MCP server and CLI still at 0.0.x (6 of 10). Total 78.", "checked": "2026-11-06" }, { "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7, "effectiveWeight": 8.75, "score": 67, "points": 5.86, "note": "editorial 64, provenance 70", "reason": "A closed service. The SDK, MCP server and CLI are MIT on npm. The terms (30 June 2026) don't name the contracting entity in their text or a governing jurisdiction; the footer names Nic Tech Solutions, LLC (15 of 30). Privacy policy of 16 September 2026 and a public DPA agree on processing, and the terms say data is deleted within 30 days of termination (24 of 30). Deprecated endpoints are marked and kept as compatibility aliases; no written deprecation policy with notice periods (10 of 20). The DPA names its core sub-processors with their purpose; data locations aren't stated (15 of 20). Total 64.", "checked": "2026-11-06" } ], "assessment": { "date": "2026-11-06", "basis": "public evidence", "confidence": "medium", "notes": { "ergonomics": "The MCP tool reference lists about 306 tools, the over-30 band, and no toolsets, tool search or dynamic loading was found (5 of 25). List endpoints paginate and filter, and contact timelines use cursors (20). Errors carry a code, a human message, a fix and a docs link, with `retryAfterSeconds` when the API sent Retry-After (20). Idempotency keys on sends and event imports; MCP readOnlyHint and destructiveHint annotations weren't found in the published reference (14 of 20). Sensible defaults with a selected workspace; one official SDK (TypeScript) plus a CLI (10 of 15). Total 69.", "maintenance": "sequenzy 2.1.56, @sequenzy/mcp 0.0.246 and @sequenzy/cli 0.0.202 were all published on 6 November 2026 (30). 18 SDK, 105 MCP and 93 CLI releases in the 90 days from 8 August, and dated changelog entries on most days (20). A closed service with a public changelog and support answered by the cofounders per the about page. GitHub issues weren't read, as the GitHub API refused our requests for its rate limit (12 of 15). Listed in the official MCP registry as io.github.polnikale/sequenzy-mcp, but the entry is at 0.0.36 against npm's 0.0.246, and the TypeScript SDK is current (10 of 15). MIT packages released daily, the MCP server and CLI still at 0.0.x (6 of 10). Total 78.", "payments": "No x402, MPP or L402 (0). Prices are public as volume tiers from $19 for 15,000 emails to $2,999 for 5 million, without a per-email overage rate (10 of 20). Free plan of 2,500 emails a month with no card (20). Agents can register through `service_auth`, but the user has to confirm a code in a Sequenzy browser page, and plan payment is through Stripe (10 of 20). Total 40.", "reliability": "Graded with the hosted lines. No status page was found; none is linked from the site, llms.txt or docs, and status.sequenzy.com doesn't resolve (0). With no history to read, the incident line takes 5. 429 responses carry RateLimit-Limit and RateLimit-Remaining headers for a per-minute policy, and some routes state numbers (20 requests a minute per workspace for AI copy), but no table of limits per key was found (8 of 15). 429s carry Retry-After, sends take an `Idempotency-Key`, a reused key with a different body returns IDEMPOTENCY_KEY_REUSED, and the MCP docs say a retry hint alone doesn't make a write safe to repeat (15). No SLA found (0). No beta label on the API or MCP server (10). Total 38.", "schema": "OpenAPI 3.1 at docs.sequenzy.com/openapi.yaml with 349 paths and 475 operations, all described (25). llms.txt on both hosts, llms-full.txt, auth.md, agents.md and Markdown twins of the docs (10). Operation and tool descriptions give purpose, the scope each needs and the alternative, such as the deprecated generate-sequence alias (18 of 20). Typed inputs, and tools reject undeclared arguments with an error naming the supported ones (13 of 15). Errors on nearly every operation (401 on 442, 404 on 330, 400 on 290) with examples, and a structured error with code, `howToFix` and `docsUrl` for tools (14 of 15). Version in the path and spec, and a dated changelog (15). Total 95.", "security": "Workspace and account API keys with fine-grained permission scopes, presets and explicit `*:delete` rights, revocable in settings, plus an OAuth `service_auth` flow for agents with user confirmation (30). Read-only and drafts-only presets let an agent prepare mail without sending, and account keys keep the user's workspace role (20). The agent inbox and reply tracking give the agent inbound mail, and no prompt-injection guidance was found in the MCP, permissions or inbox docs (4 of 15). The DPA lists administrative audit logs and MCP events report replies and bounces; no per-call API log for the customer was found (8 of 15). A responsible disclosure address on the security page, no security.txt (404), bug bounty or certification (5 of 20). Total 67.", "transparency": "A closed service. The SDK, MCP server and CLI are MIT on npm. The terms (30 June 2026) don't name the contracting entity in their text or a governing jurisdiction; the footer names Nic Tech Solutions, LLC (15 of 30). Privacy policy of 16 September 2026 and a public DPA agree on processing, and the terms say data is deleted within 30 days of termination (24 of 30). Deprecated endpoints are marked and kept as compatibility aliases; no written deprecation policy with notice periods (10 of 20). The DPA names its core sub-processors with their purpose; data locations aren't stated (15 of 20). Total 64." }, "sources": [ { "what": "llms.txt", "url": "https://www.sequenzy.com/llms.txt", "seen": "2026-11-06" }, { "what": "docs index", "url": "https://docs.sequenzy.com/llms.txt", "seen": "2026-11-06" }, { "what": "OpenAPI 3.1 spec", "url": "https://docs.sequenzy.com/openapi.yaml", "seen": "2026-11-06" }, { "what": "authentication and key scopes", "url": "https://docs.sequenzy.com/authentication.md", "seen": "2026-11-06" }, { "what": "MCP permissions", "url": "https://docs.sequenzy.com/concepts/mcp-permissions.md", "seen": "2026-11-06" }, { "what": "MCP tool reference", "url": "https://docs.sequenzy.com/concepts/mcp-tools.md", "seen": "2026-11-06" }, { "what": "agent auth", "url": "https://www.sequenzy.com/auth.md", "seen": "2026-11-06" }, { "what": "changelog", "url": "https://docs.sequenzy.com/changelog.md", "seen": "2026-11-06" }, { "what": "pricing", "url": "https://www.sequenzy.com/pricing", "seen": "2026-11-06" }, { "what": "terms", "url": "https://www.sequenzy.com/terms", "seen": "2026-11-06" }, { "what": "privacy policy", "url": "https://www.sequenzy.com/privacy", "seen": "2026-11-06" }, { "what": "DPA and sub-processors", "url": "https://www.sequenzy.com/dpa", "seen": "2026-11-06" }, { "what": "security page", "url": "https://www.sequenzy.com/security", "seen": "2026-11-06" }, { "what": "official MCP registry", "url": "https://registry.modelcontextprotocol.io/v0/servers?search=sequenzy", "seen": "2026-11-06" } ], "openQuestions": [ "No status page or incident history was found", "Per-key request limits aren't published as a table", "unchecked: GitHub issues and CI for the Sequenzy repositories, because the GitHub API refused our requests for its rate limit", "Whether MCP tools carry readOnlyHint or destructiveHint annotations wasn't stated in the reference" ] }, "negative": 0, "verdict": "Scoped keys with read-only and drafts-only presets, a 475-operation OpenAPI spec, idempotent sends and near-daily dated releases make it workable for an agent. The MCP server lists about 306 tools, which is heavy on context, and there is no status page, SLA or published request limit table.", "bestFor": "SaaS and ecommerce lifecycle email run from code or an agent, with billing-event triggers from Stripe, Paddle and others.", "strengths": [ "Every key and MCP grant carries permission scopes, with read-only and drafts-only presets and explicit delete permissions", "OpenAPI 3.1 with 475 described operations, llms.txt and Markdown twins of the docs", "Tool and API errors return a code, a fix and a docs link, and sends take an `Idempotency-Key`", "Free plan of 2,500 emails a month with no card and full API, MCP and CLI access", "Dated changelog entries almost every day, 353 since December 2025" ], "weaknesses": [ "About 306 MCP tools, with no toolsets or dynamic loading found", "No status page, incident history or SLA found", "Request rate limits appear only as response headers and a few per-route notes, with no published table", "The registry entry io.github.polnikale/sequenzy-mcp is at 0.0.36 while npm is at 0.0.246", "The terms' governing-law clause doesn't name a jurisdiction" ], "agentNotes": [ "Connect with a drafts-only or read-only key unless the task must send, and widen permissions only when an error names the missing scope", "Send an `Idempotency-Key` with each transactional send and reuse it unchanged after an uncertain result", "Read `structuredContent.error.code` and `howToFix` on a failed tool call before retrying; the client doesn't retry", "Call `get_account` and `select_company` first when the key can reach more than one workspace", "On 429 wait for Retry-After and read the RateLimit-Remaining header" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 63.7 } ], "editorialScores": { "ergonomics": 69, "maintenance": 78, "payments": 40, "reliability": 38, "schema": 95, "security": 67, "transparency": 64 }, "provenanceScore": 70, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 }, "scoreHistory": [ { "date": "2026-11-06", "grade": "B", "kind": "listed", "method": "0.7", "score": 63.7 } ] }, "connect": { "install": "npm install sequenzy", "claudeCode": "claude mcp add --scope user --env=SEQUENZY_API_KEY=seq_user_your_key_here sequenzy -- npx -y @sequenzy/mcp", "config": { "mcpServers": { "sequenzy": { "args": [ "-y", "@sequenzy/mcp" ], "command": "npx", "env": { "SEQUENZY_API_KEY": "seq_user_your_key_here" } } } } }, "letme": { "capability": "https://letme.dev/marketing.profiles", "tool": "https://letme.dev/sequenzy" }, "alsoIn": [ "email" ], "notable": [ "OpenAPI 3.1 spec with 349 paths and 475 operations, every one described, with 401 and 404 responses on most and an IDEMPOTENCY_KEY_REUSED error for reused keys (https://docs.sequenzy.com/openapi.yaml)", "Every API key and MCP connection is scoped, with presets from read-only and drafts-only to full access, and deletes need explicit `*:delete` permissions (https://docs.sequenzy.com/concepts/mcp-permissions.md)", "The MCP tool reference lists about 306 tools, and tool errors return a code, `howToFix` and a docs link (https://docs.sequenzy.com/concepts/mcp-tools.md)", "Dated changelog with 353 entries since 19 December 2025, the latest on 6 November 2026 (https://docs.sequenzy.com/changelog.md)", "No status page was found; status.sequenzy.com doesn't resolve, and none is linked from the site or docs" ], "area": "communication", "details": [ { "label": "Surface listed", "value": "The REST API at api.sequenzy.com, the MCP server (npm @sequenzy/mcp and the OAuth resource at api.sequenzy.com/v1/mcp), the CLI and the TypeScript SDK, read from docs.sequenzy.com, the OpenAPI spec, www.sequenzy.com, npm and the MCP registry on 6 November 2026. No account was made and no tool was called" }, { "label": "Category", "value": "Listed in lifecycle-marketing because its surface is sequences, campaigns, segments, events and subscriber data, with transactional email as one part; also shown in email" }, { "label": "Channels", "value": "Email, an inbox for replies and inbound mail, web and mobile push and in-app messages on every plan, SMS and MMS as a paid add-on" }, { "label": "Integrations", "value": "Stripe, Paddle, Lemon Squeezy, Polar, Shopify, WooCommerce, Clerk, Better Auth, Supabase, PostHog, Segment, Mixpanel, Amplitude and others" }, { "label": "Sub-processors", "value": "PlanetScale (database), Railway (Redis), Cloudflare (storage, DNS, CDN), AWS (sending and inbound), Stripe and PostHog, plus feature-dependent ones, per the DPA" }, { "label": "Legal entity", "value": "Nic Tech Solutions, LLC, Delaware, named in the site footer and contact page; the product is built in Ukraine" } ], "unitPrices": [ { "item": "15,000 emails", "unit": "month", "usd": 19 }, { "item": "60,000 emails", "unit": "month", "usd": 49 }, { "item": "120,000 emails", "unit": "month", "usd": 99 }, { "item": "300,000 emails", "unit": "month", "usd": 199 }, { "item": "SMS add-on", "unit": "month", "usd": 16, "note": "1,000 credits a month" } ], "provenance": { "legalEntity": "Nic Tech Solutions, LLC", "domain": "sequenzy.com", "domainRegistered": "2025-11-25", "endpointOnVendorDomain": true, "terms": "https://www.sequenzy.com/terms", "privacy": "https://www.sequenzy.com/privacy", "statusPage": "", "changelog": "https://docs.sequenzy.com/changelog", "securityTxt": "none", "checked": "2026-11-06", "notes": [ "The site footer and contact page name Nic Tech Solutions, LLC in Delaware. The terms (30 June 2026) say they're governed by the laws of the jurisdiction in which Sequenzy operates, without naming it.", "Privacy policy last updated 16 September 2026, security page 3 July 2026, and a public DPA with a named sub-processor list.", "www.sequenzy.com/robots.txt disallows /api/, /dashboard/ and app paths only; docs.sequenzy.com disallows /_next/ and /cdn-cgi/. Both carry Content-Signal ai-input=yes.", "RDAP gives sequenzy.com a registration date of 25 November 2025.", "/.well-known/security.txt returns 404; the security page gives security@sequenzy.com for disclosure. No status page found." ], "score": 70, "checks": [ { "check": "Legal entity named", "value": "Nic Tech Solutions, LLC", "points": 20, "max": 20, "state": "ok" }, { "check": "Domain age", "value": "sequenzy.com, registered 2025-11-25 (under a year)", "points": 0, "max": 15, "state": "no" }, { "check": "Endpoint on the vendor's domain", "value": "api.sequenzy.com", "points": 15, "max": 15, "state": "ok" }, { "check": "Terms of service", "value": "read, states 7 of the 7 things a reader expects", "points": 10, "max": 10, "state": "ok" }, { "check": "Privacy policy", "value": "read, states 8 of the 8 things a reader expects", "points": 10, "max": 10, "state": "ok" }, { "check": "Status page", "value": "not found", "points": 0, "max": 10, "state": "no" }, { "check": "Changelog", "value": "published", "points": 10, "max": 10, "state": "ok" }, { "check": "security.txt", "value": "not found", "points": 0, "max": 10, "state": "no" }, { "check": "People named", "value": "1 named with their role, 1 with a public profile", "points": 10, "max": 10, "state": "ok" }, { "check": "Support route", "value": "a support address, help pages", "points": 5, "max": 5, "state": "ok" } ], "policies": [ { "kind": "terms", "url": "https://www.sequenzy.com/terms", "state": "read", "readAt": "2026-11-06", "statedDate": "2026-06-30", "words": 1178, "points": 10, "max": 10, "expected": [ { "key": "terms.date", "label": "Gives the date it was last updated", "found": true, "quote": "Last updated: June 30, 2026", "says": "Last updated 2026-06-30" }, { "key": "terms.law", "label": "Names the governing law or courts", "found": true, "quote": "These Terms shall be governed by and construed in accordance with the laws of the jurisdiction in which Sequenzy operates, without regard to its conflict of law provisions." }, { "key": "terms.liability", "label": "States a limit on its liability", "found": true, "quote": "Our total liability shall not exceed the amount paid by you in the 12 months preceding the claim.", "says": "Capped at the fees paid in the 12 months before the claim" }, { "key": "terms.termination", "label": "Says how the agreement or account can be ended", "found": true, "quote": "- You may terminate your account at any time through account settings - We may suspend or terminate your account immediately and without notice for violation of these Terms, particularly the Anti-Spam Policy - Upon termination, your data will be deleted within 30 days - Accounts terminated for spam violations are not…" }, { "key": "terms.changes", "label": "Says how changes to the terms are announced", "found": true, "quote": "…including for accounts suspended due to policy violations - We reserve the right to change prices with 30 days notice - Failure to pay may result in account suspension ## 8.", "says": "Gives 30 days of notice before a change" }, { "key": "terms.use", "label": "Lists what users may not do", "found": true, "quote": "If you disagree with any part of these terms, you may not access the Service." }, { "key": "terms.sla", "label": "Refers to a service level or uptime commitment", "found": true, "quote": "We strive to provide reliable service but do not guarantee 100% uptime." } ], "toKnow": [ { "key": "terms.cutoff", "label": "Says access can be ended without notice or for any reason", "found": true, "quote": "We reserve the right to modify, suspend, or discontinue the Service at any time with reasonable notice." } ] }, { "kind": "privacy", "url": "https://www.sequenzy.com/privacy", "state": "read", "readAt": "2026-11-06", "statedDate": "2026-09-16", "words": 2125, "points": 10, "max": 10, "expected": [ { "key": "privacy.date", "label": "Gives the date it was last updated", "found": true, "quote": "Last updated: September 16, 2026", "says": "Last updated 2026-09-16" }, { "key": "privacy.collected", "label": "Says what personal data is collected", "found": true, "quote": "Learn how we collect, use, and protect your personal information.\" image: \"https://www.sequenzy.com/opengraph-image\" ---" }, { "key": "privacy.retention", "label": "Says how long data is kept", "found": true, "quote": "…entire lists at any time - Upon account termination, all subscriber data is permanently deleted within 30 days - Webflow subscriber events, including only the configured allowed form fields, have a five-year maximum analytics retention unless deleted earlier through the account or workspace deletion process.", "says": "Names a period of 30 days" }, { "key": "privacy.processors", "label": "Says who else receives the data", "found": true, "quote": "When you explicitly invoke those tools, they can accept third-party provider credentials and can return newly created API keys, webhook signing secrets, or credential-bearing inbound-webhook URLs." }, { "key": "privacy.sale", "label": "Says whether personal data is sold or shared for advertising", "found": true, "quote": "We may share your information in the following circumstances:" }, { "key": "privacy.rights", "label": "Says what rights people have over their data", "found": true, "quote": "If our visitor-identification tools process personal data for international company-level identification, you may also opt out under GDPR at [https://www.rb2b.com/rb2b-gdpr-opt-out](https://www.rb2b.com/rb2b-gdpr-opt-out)." }, { "key": "privacy.contact", "label": "Gives a privacy contact", "found": true, "quote": "Manage subscriber deletion in Sequenzy or contact privacy@sequenzy.com for a data deletion request.", "says": "privacy@sequenzy.com" }, { "key": "privacy.transfers", "label": "Says where data is transferred or stored", "found": true, "quote": "We ensure appropriate safeguards are in place when transferring data internationally, including standard contractual clauses where required.", "says": "Relies on standard contractual clauses" } ] } ] }, "humans": { "slug": "sequenzy", "checked": "2026-11-06", "company": "Nic Tech Solutions, LLC", "people": [ { "name": "Nic Polotnianko", "role": "Co-founder and CEO", "founder": true, "x": "https://x.com/nikpolale", "page": "/people/nic-polotnianko/" } ], "peopleNote": "The about page (last updated 24 September 2026) says Sequenzy was founded in 2025 by two cofounders and names Nic Polotnianko as co-founder and CEO, with his X account. The second cofounder isn't named on the pages read. The footer names Nic Tech Solutions, LLC in Delaware and says the product is built in Ukraine. No funding round, investor, total raised or valuation is mentioned on the about, contact, security or llms.txt pages, read again on 6 November 2026, so they are left out.", "companySocial": { "linkedin": "https://www.linkedin.com/company/sequenzy/", "x": "https://x.com/sequenzy_com", "github": "https://github.com/Sequenzy" }, "support": { "emails": [ "nic@sequenzy.com" ], "urls": [ "https://www.sequenzy.com/contact", "https://docs.sequenzy.com" ], "contactEmails": [ "security@sequenzy.com" ] }, "sources": [ "https://www.sequenzy.com/about", "https://www.sequenzy.com/contact", "https://www.sequenzy.com/llms.txt", "https://www.sequenzy.com/security" ], "ownership": { "status": "private", "checked": "2026-11-06", "sources": [ "https://www.sequenzy.com/about" ] } }, "pageJsonUrl": "https://www.anchorterminal.com/tools/sequenzy.json", "live": { "slug": "sequenzy", "probe": { "target": "https://api.sequenzy.com/v1/mcp", "method": "get", "lastAt": "2026-11-07T17:50:05.12344429Z", "lastOk": true, "lastStatus": 401, "lastMs": 633, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 428, "p95ms24h": 963, "samples24h": 195, "samples30d": 195, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 182, "ok": 182 } ] }, "versions": [ { "registry": "npm", "name": "@sequenzy/cli", "version": "0.0.202", "seenAt": "2026-11-07T00:04:47.709534287Z" }, { "registry": "npm", "name": "@sequenzy/mcp", "version": "0.0.246", "seenAt": "2026-11-07T00:04:46.382384788Z" }, { "registry": "npm", "name": "sequenzy", "version": "2.1.56", "seenAt": "2026-11-07T00:04:45.470371029Z" } ], "githubStars": 3, "npmWeekly": 2363, "securityTxt": { "url": "https://sequenzy.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:01:21.983534364Z" }, "llmsTxt": { "url": "https://www.sequenzy.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:33:54.221757235Z" }, "pages": [ { "url": "https://docs.sequenzy.com/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:07:55.051332773Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "c2d75327efad" }, { "url": "https://www.sequenzy.com/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:34:21.090752788Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "03a493105931" }, { "url": "https://www.sequenzy.com/terms", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:34:23.45384067Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "a816dc038eb6" } ], "updatedAt": "2026-11-07T17:50:05.12344429Z" } }, "verify": { "accepts": "a page on sequenzy.com or one of its subdomains, or the README at the root of github.com/Sequenzy/mcp", "badgeUrl": "https://www.anchorterminal.com/badges/sequenzy.svg", "body": { "slug": "sequenzy", "url": "the page with the badge or the link" }, "docs": "https://www.anchorterminal.com/builders/#verify", "effect": "none, it never changes a grade, rank or review", "endpoint": "https://www.anchorterminal.com/api/v1/verify", "listingUrl": "https://www.anchorterminal.com/tools/sequenzy", "mcpTool": "verify_listing", "recheck": "weekly; two failed checks in a row and it lapses, a later pass restores it", "snippets": { "html": "\u003ca href=\"https://www.anchorterminal.com/tools/sequenzy\"\u003e\u003cimg src=\"https://www.anchorterminal.com/badges/sequenzy.svg\" alt=\"Sequenzy on Anchor Terminal\" height=\"20\"\u003e\u003c/a\u003e", "markdown": "[![Sequenzy on Anchor Terminal](https://www.anchorterminal.com/badges/sequenzy.svg)](https://www.anchorterminal.com/tools/sequenzy)", "link": "\u003ca href=\"https://www.anchorterminal.com/tools/sequenzy\"\u003eSequenzy on Anchor Terminal\u003c/a\u003e" } } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/tools/sequenzy", "json": "https://www.anchorterminal.com/tools/sequenzy.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/tools/sequenzy.md", "mcp": "https://www.anchorterminal.com/mcp", "pricing": "https://www.anchorterminal.com/tools/sequenzy#pricing", "reviews": "https://www.anchorterminal.com/tools/sequenzy#reviews", "slim": "https://www.anchorterminal.com/tools/sequenzy.min.md" }, "markdown": "## Overview\n\n**Grade B · 63.7/100 · rank #504 of 1486 · #6 in Lifecycle marketing \u0026 customer engagement · not agent-ready · confidence medium**\n\n\nAlso listed in [Email delivery APIs](https://www.anchorterminal.com/categories/email.md).\n\n## Assessment\n\nScoped keys with read-only and drafts-only presets, a 475-operation OpenAPI spec, idempotent sends and near-daily dated releases make it workable for an agent. The MCP server lists about 306 tools, which is heavy on context, and there is no status page, SLA or published request limit table.\n\n## Facts\n\n| Field | Value |\n| --- | --- |\n| Vendor | Nic Tech Solutions, LLC (https://www.sequenzy.com) |\n| Kind | HTTP API |\n| Category | Lifecycle marketing \u0026 customer engagement (https://www.anchorterminal.com/categories/lifecycle-marketing) |\n| Transport | HTTP, Streamable HTTP, stdio |\n| Endpoint | `https://api.sequenzy.com/v1/mcp` |\n| Auth | OAuth or key · Workspace API keys (`seq_live_`) and account keys (`seq_user_`) sent as Bearer tokens, each with permission scopes such as `transactional:send`, `subscribers:tag` and explicit `*:delete`, and presets including read-only and drafts-only. Account keys keep the user's workspace role. Agents can also register through the `service_auth` OAuth flow, where the user confirms a code in a Sequenzy browser page. |\n| Pricing | Freemium ($19 / mo) · Free plan of 2,500 emails a month with unlimited contacts and API, MCP and CLI access, no card, with a Sequenzy footer. Paid plans by monthly email volume, $19 for 15,000, $29 for 30,000, $49 for 60,000, $99 for 120,000, up to $2,999 for 5 million. SMS add-on $16 a month with 1,000 credits. |\n| x402 | No · No x402, MPP or L402 in llms.txt, auth.md, the pricing page or the OpenAPI spec (checked 2026-11-06). |\n| Licence | unknown |\n| Tools exposed | 306 |\n| Packages | npm: `sequenzy`; npm: `@sequenzy/mcp`; npm: `@sequenzy/cli` |\n| MCP registry name | `io.github.polnikale/sequenzy-mcp` |\n| Source | https://github.com/Sequenzy/mcp |\n| Docs | https://docs.sequenzy.com |\n| llms.txt | https://www.sequenzy.com/llms.txt |\n| Last release | 2026-11-06 |\n| npm downloads / week | 2,363 |\n| Surface listed | The REST API at api.sequenzy.com, the MCP server (npm @sequenzy/mcp and the OAuth resource at api.sequenzy.com/v1/mcp), the CLI and the TypeScript SDK, read from docs.sequenzy.com, the OpenAPI spec, www.sequenzy.com, npm and the MCP registry on 6 November 2026. No account was made and no tool was called |\n| Category | Listed in lifecycle-marketing because its surface is sequences, campaigns, segments, events and subscriber data, with transactional email as one part; also shown in email |\n| Channels | Email, an inbox for replies and inbound mail, web and mobile push and in-app messages on every plan, SMS and MMS as a paid add-on |\n| Integrations | Stripe, Paddle, Lemon Squeezy, Polar, Shopify, WooCommerce, Clerk, Better Auth, Supabase, PostHog, Segment, Mixpanel, Amplitude and others |\n| Sub-processors | PlanetScale (database), Railway (Redis), Cloudflare (storage, DNS, CDN), AWS (sending and inbound), Stripe and PostHog, plus feature-dependent ones, per the DPA |\n| Legal entity | Nic Tech Solutions, LLC, Delaware, named in the site footer and contact page; the product is built in Ukraine |\n| Capabilities | marketing.profiles, marketing.events, marketing.segments, marketing.campaigns, marketing.journeys, email.send, email.templates, email.inbound |\n| Tags | hosted, closed-source, mcp, remote-mcp, mcp-registry, oauth, api-key, openapi, llms-txt, webhooks, idempotency, smtp, sms, no-card, free-tier, typescript, cli, no-status-page |\n| JSON | https://www.anchorterminal.com/api/v1/tools/sequenzy.json |\n\n## Score breakdown (methodology v0.7, October 2026 research run)\n\nAssessed 2026-11-06 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. \"This run\" is each category's share of the 100 points.\n\n| Category | Weight | This run | Score (0–100) | Points |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 20 | 38 | 7.6 |\n| Performance | 10% | pending | pending | n/a |\n| Schema \u0026 documentation | 13% | 16.2 | 95 | 15.4 |\n| Agent ergonomics | 13% | 16.2 | 69 | 11.2 |\n| Security \u0026 auth | 14% | 17.5 | 67 | 11.7 |\n| Payments \u0026 pricing | 10% | 12.5 | 40 | 5.0 |\n| Task success | 10% | pending | pending | n/a |\n| Maintenance \u0026 community | 7% | 8.8 | 78 | 6.8 |\n| Transparency \u0026 trust (editorial 64, provenance 70) | 7% | 8.8 | 67 | 5.9 |\n| Negative events | up to −15 | up to −15 | none recorded | 0 |\n| **Total** | | | | **63.7 → B** |\n\n### Why each score\n\n- Reliability 38 (checked 2026-11-06): Graded with the hosted lines. No status page was found; none is linked from the site, llms.txt or docs, and status.sequenzy.com doesn't resolve (0). With no history to read, the incident line takes 5. 429 responses carry RateLimit-Limit and RateLimit-Remaining headers for a per-minute policy, and some routes state numbers (20 requests a minute per workspace for AI copy), but no table of limits per key was found (8 of 15). 429s carry Retry-After, sends take an `Idempotency-Key`, a reused key with a different body returns IDEMPOTENCY_KEY_REUSED, and the MCP docs say a retry hint alone doesn't make a write safe to repeat (15). No SLA found (0). No beta label on the API or MCP server (10). Total 38.\n- Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes.\n- Schema \u0026 documentation 95 (checked 2026-11-06): OpenAPI 3.1 at docs.sequenzy.com/openapi.yaml with 349 paths and 475 operations, all described (25). llms.txt on both hosts, llms-full.txt, auth.md, agents.md and Markdown twins of the docs (10). Operation and tool descriptions give purpose, the scope each needs and the alternative, such as the deprecated generate-sequence alias (18 of 20). Typed inputs, and tools reject undeclared arguments with an error naming the supported ones (13 of 15). Errors on nearly every operation (401 on 442, 404 on 330, 400 on 290) with examples, and a structured error with code, `howToFix` and `docsUrl` for tools (14 of 15). Version in the path and spec, and a dated changelog (15). Total 95.\n- Agent ergonomics 69 (checked 2026-11-06): The MCP tool reference lists about 306 tools, the over-30 band, and no toolsets, tool search or dynamic loading was found (5 of 25). List endpoints paginate and filter, and contact timelines use cursors (20). Errors carry a code, a human message, a fix and a docs link, with `retryAfterSeconds` when the API sent Retry-After (20). Idempotency keys on sends and event imports; MCP readOnlyHint and destructiveHint annotations weren't found in the published reference (14 of 20). Sensible defaults with a selected workspace; one official SDK (TypeScript) plus a CLI (10 of 15). Total 69.\n- Security \u0026 auth 67 (checked 2026-11-06): Workspace and account API keys with fine-grained permission scopes, presets and explicit `*:delete` rights, revocable in settings, plus an OAuth `service_auth` flow for agents with user confirmation (30). Read-only and drafts-only presets let an agent prepare mail without sending, and account keys keep the user's workspace role (20). The agent inbox and reply tracking give the agent inbound mail, and no prompt-injection guidance was found in the MCP, permissions or inbox docs (4 of 15). The DPA lists administrative audit logs and MCP events report replies and bounces; no per-call API log for the customer was found (8 of 15). A responsible disclosure address on the security page, no security.txt (404), bug bounty or certification (5 of 20). Total 67.\n- Payments \u0026 pricing 40 (checked 2026-11-06): No x402, MPP or L402 (0). Prices are public as volume tiers from $19 for 15,000 emails to $2,999 for 5 million, without a per-email overage rate (10 of 20). Free plan of 2,500 emails a month with no card (20). Agents can register through `service_auth`, but the user has to confirm a code in a Sequenzy browser page, and plan payment is through Stripe (10 of 20). Total 40.\n- Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored.\n- Maintenance \u0026 community 78 (checked 2026-11-06): sequenzy 2.1.56, @sequenzy/mcp 0.0.246 and @sequenzy/cli 0.0.202 were all published on 6 November 2026 (30). 18 SDK, 105 MCP and 93 CLI releases in the 90 days from 8 August, and dated changelog entries on most days (20). A closed service with a public changelog and support answered by the cofounders per the about page. GitHub issues weren't read, as the GitHub API refused our requests for its rate limit (12 of 15). Listed in the official MCP registry as io.github.polnikale/sequenzy-mcp, but the entry is at 0.0.36 against npm's 0.0.246, and the TypeScript SDK is current (10 of 15). MIT packages released daily, the MCP server and CLI still at 0.0.x (6 of 10). Total 78.\n- Transparency \u0026 trust 67 (checked 2026-11-06): A closed service. The SDK, MCP server and CLI are MIT on npm. The terms (30 June 2026) don't name the contracting entity in their text or a governing jurisdiction; the footer names Nic Tech Solutions, LLC (15 of 30). Privacy policy of 16 September 2026 and a public DPA agree on processing, and the terms say data is deleted within 30 days of termination (24 of 30). Deprecated endpoints are marked and kept as compatibility aliases; no written deprecation policy with notice periods (10 of 20). The DPA names its core sub-processors with their purpose; data locations aren't stated (15 of 20). Total 64.\n\nFix list, everything this grade says the listing lacks, the biggest gain first (14 items). What it covers is at https://www.anchorterminal.com/fixes/sequenzy.md (JSON https://www.anchorterminal.com/fixes/sequenzy.json). The whole list for a coding agent comes from `POST https://www.anchorterminal.com/api/v1/fix-list` with `{\"listing\": \"sequenzy\", \"plan\": \"read\"}`, free while the beta runs\n\n### What we couldn't check\n\n- No status page or incident history was found\n- Per-key request limits aren't published as a table\n- unchecked: GitHub issues and CI for the Sequenzy repositories, because the GitHub API refused our requests for its rate limit\n- Whether MCP tools carry readOnlyHint or destructiveHint annotations wasn't stated in the reference\n\n### Sources\n\n- llms.txt: \u003chttps://www.sequenzy.com/llms.txt\u003e (seen 2026-11-06)\n- docs index: \u003chttps://docs.sequenzy.com/llms.txt\u003e (seen 2026-11-06)\n- OpenAPI 3.1 spec: \u003chttps://docs.sequenzy.com/openapi.yaml\u003e (seen 2026-11-06)\n- authentication and key scopes: \u003chttps://docs.sequenzy.com/authentication.md\u003e (seen 2026-11-06)\n- MCP permissions: \u003chttps://docs.sequenzy.com/concepts/mcp-permissions.md\u003e (seen 2026-11-06)\n- MCP tool reference: \u003chttps://docs.sequenzy.com/concepts/mcp-tools.md\u003e (seen 2026-11-06)\n- agent auth: \u003chttps://www.sequenzy.com/auth.md\u003e (seen 2026-11-06)\n- changelog: \u003chttps://docs.sequenzy.com/changelog.md\u003e (seen 2026-11-06)\n- pricing: \u003chttps://www.sequenzy.com/pricing\u003e (seen 2026-11-06)\n- terms: \u003chttps://www.sequenzy.com/terms\u003e (seen 2026-11-06)\n- privacy policy: \u003chttps://www.sequenzy.com/privacy\u003e (seen 2026-11-06)\n- DPA and sub-processors: \u003chttps://www.sequenzy.com/dpa\u003e (seen 2026-11-06)\n- security page: \u003chttps://www.sequenzy.com/security\u003e (seen 2026-11-06)\n- official MCP registry: \u003chttps://registry.modelcontextprotocol.io/v0/servers?search=sequenzy\u003e (seen 2026-11-06)\n\n## Score history\n\nEvery move of a score since the listing was graded, newest first, with its cause. A score can't move without an entry here. JSON: https://www.anchorterminal.com/api/v1/tools/sequenzy/history.json\n\n- 2026-11-06: graded 63.7 B (methodology 0.7)\n\n## Who's behind it (provenance 70/100, checked 2026-11-06)\n\n| Check | Finding | Points |\n| --- | --- | --- |\n| Legal entity named | Nic Tech Solutions, LLC | 20/20 |\n| Domain age | sequenzy.com, registered 2025-11-25 (under a year) | 0/15 |\n| Endpoint on the vendor's domain | api.sequenzy.com | 15/15 |\n| Terms of service | read, states 7 of the 7 things a reader expects | 10/10 |\n| Privacy policy | read, states 8 of the 8 things a reader expects | 10/10 |\n| Status page | not found | 0/10 |\n| Changelog | published | 10/10 |\n| security.txt | not found | 0/10 |\n| People named | 1 named with their role, 1 with a public profile | 10/10 |\n| Support route | a support address, help pages | 5/5 |\n\nThe site footer and contact page name Nic Tech Solutions, LLC in Delaware. The terms (30 June 2026) say they're governed by the laws of the jurisdiction in which Sequenzy operates, without naming it.\n\nPrivacy policy last updated 16 September 2026, security page 3 July 2026, and a public DPA with a named sub-processor list.\n\nwww.sequenzy.com/robots.txt disallows /api/, /dashboard/ and app paths only; docs.sequenzy.com disallows /_next/ and /cdn-cgi/. Both carry Content-Signal ai-input=yes.\n\nRDAP gives sequenzy.com a registration date of 25 November 2025.\n\n/.well-known/security.txt returns 404; the security page gives security@sequenzy.com for disclosure. No status page found.\n\n### Terms and privacy, as read\n\nA reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice.\n\n**Terms of service** (https://www.sequenzy.com/terms), read 2026-11-06, dated 2026-06-30, states 7 of the 7 things a reader expects.\n\n- To know. Says access can be ended without notice or for any reason. \"We reserve the right to modify, suspend, or discontinue the Service at any time with reasonable notice.\"\n- Gives the date it was last updated. Last updated 2026-06-30.\n- States a limit on its liability. Capped at the fees paid in the 12 months before the claim.\n- Says how changes to the terms are announced. Gives 30 days of notice before a change.\n\n**Privacy policy** (https://www.sequenzy.com/privacy), read 2026-11-06, dated 2026-09-16, states 8 of the 8 things a reader expects.\n\n- Gives the date it was last updated. Last updated 2026-09-16.\n- Says how long data is kept. Names a period of 30 days.\n- Gives a privacy contact. privacy@sequenzy.com.\n- Says where data is transferred or stored. Relies on standard contractual clauses.\n\n## Humans behind the project (researched 2026-11-06 from public pages, not part of the grade)\n\n### Key people\n\n- Nic Polotnianko, Co-founder and CEO. X: https://x.com/nikpolale\n- Note: The about page (last updated 24 September 2026) says Sequenzy was founded in 2025 by two cofounders and names Nic Polotnianko as co-founder and CEO, with his X account. The second cofounder isn't named on the pages read. The footer names Nic Tech Solutions, LLC in Delaware and says the product is built in Ukraine. No funding round, investor, total raised or valuation is mentioned on the about, contact, security or llms.txt pages, read again on 6 November 2026, so they are left out.\n- Nic Tech Solutions, LLC: LinkedIn https://www.linkedin.com/company/sequenzy/ X https://x.com/sequenzy_com GitHub https://github.com/Sequenzy\n\n### Getting support\n\n- Support email: nic@sequenzy.com\n- Help: https://www.sequenzy.com/contact\n- Help: https://docs.sequenzy.com\n- Sources: https://www.sequenzy.com/about, https://www.sequenzy.com/contact, https://www.sequenzy.com/llms.txt, https://www.sequenzy.com/security\n\n## Live (updated 2026-11-07 17:50 UTC)\n\n- Right now: up, HTTP 401, 633 ms, checked 2026-11-07 17:50 UTC (get on `https://api.sequenzy.com/v1/mcp`, asks for auth)\n- Uptime 24h 100.0% (195 probes) · 30 days 100.0% (195 probes) · p50 428 ms · p95 963 ms\n- npm `@sequenzy/cli` 0.0.202\n- npm `@sequenzy/mcp` 0.0.246\n- npm `sequenzy` 2.1.56\n- security.txt: none\n- Watching changelog \u003chttps://docs.sequenzy.com/changelog\u003e\n- Watching privacy \u003chttps://www.sequenzy.com/privacy\u003e\n- Watching terms \u003chttps://www.sequenzy.com/terms\u003e\n- Always current: https://www.anchorterminal.com/api/v1/live/sequenzy.json\n\n## Probe metrics\n\nNot measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score.\n\n## Prices\n\n| Item | Price | Unit | Note |\n| --- | --- | --- | --- |\n| 15,000 emails | $19 | per month (plan) | |\n| 60,000 emails | $49 | per month (plan) | |\n| 120,000 emails | $99 | per month (plan) | |\n| 300,000 emails | $199 | per month (plan) | |\n| SMS add-on | $16 | per month (plan) | 1,000 credits a month |\n\nAcross all listings: https://www.anchorterminal.com/prices/index.md\n\n## Strengths\n\n- Every key and MCP grant carries permission scopes, with read-only and drafts-only presets and explicit delete permissions\n- OpenAPI 3.1 with 475 described operations, llms.txt and Markdown twins of the docs\n- Tool and API errors return a code, a fix and a docs link, and sends take an `Idempotency-Key`\n- Free plan of 2,500 emails a month with no card and full API, MCP and CLI access\n- Dated changelog entries almost every day, 353 since December 2025\n\n## Weaknesses\n\n- About 306 MCP tools, with no toolsets or dynamic loading found\n- No status page, incident history or SLA found\n- Request rate limits appear only as response headers and a few per-route notes, with no published table\n- The registry entry io.github.polnikale/sequenzy-mcp is at 0.0.36 while npm is at 0.0.246\n- The terms' governing-law clause doesn't name a jurisdiction\n\n\n\n## Before you call it (notes for agents)\n\n1. Connect with a drafts-only or read-only key unless the task must send, and widen permissions only when an error names the missing scope\n2. Send an `Idempotency-Key` with each transactional send and reuse it unchanged after an uncertain result\n3. Read `structuredContent.error.code` and `howToFix` on a failed tool call before retrying; the client doesn't retry\n4. Call `get_account` and `select_company` first when the key can reach more than one workspace\n5. On 429 wait for Retry-After and read the RateLimit-Remaining header\n\n## Connect\n\nInstall:\n\n```bash\nnpm install sequenzy\n```\n\nClaude Code:\n\n```bash\nclaude mcp add --scope user --env=SEQUENZY_API_KEY=seq_user_your_key_here sequenzy -- npx -y @sequenzy/mcp\n```\n\nMCP client configuration:\n\n```json\n{\n \"mcpServers\": {\n \"sequenzy\": {\n \"args\": [\n \"-y\",\n \"@sequenzy/mcp\"\n ],\n \"command\": \"npx\",\n \"env\": {\n \"SEQUENZY_API_KEY\": \"seq_user_your_key_here\"\n }\n }\n }\n}\n```\n\nThrough letme: https://letme.dev/sequenzy. letme answers with the pick and how to call it direct. How it works: https://www.anchorterminal.com/letme/index.md\n\n## Similar tools\n\nRanked by shared capabilities, then score. Same-category tools with no shared capability key are listed last.\n\n| Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown |\n| --- | --- | --- | --- | --- | --- | --- |\n| Customer.io | BB | 75.6 | 57 | marketing.profiles, marketing.events, marketing.segments, marketing.campaigns, marketing.journeys, email.send, email.templates | no | https://www.anchorterminal.com/tools/customer-io.md |\n| Nitrosend | B | 69.4 | 248 | marketing.profiles, marketing.events, marketing.segments, marketing.campaigns, marketing.journeys, email.send, email.templates | no | https://www.anchorterminal.com/tools/nitrosend.md |\n| Klaviyo API + MCP | BB | 73.8 | 97 | marketing.profiles, marketing.events, marketing.segments, marketing.campaigns, marketing.journeys, email.templates | no | https://www.anchorterminal.com/tools/klaviyo.md |\n| Omnisend | B | 65.8 | 398 | marketing.profiles, marketing.events, marketing.segments, marketing.campaigns, marketing.journeys, email.templates | no | https://www.anchorterminal.com/tools/omnisend.md |\n| MoEngage | B | 65.7 | 403 | marketing.profiles, marketing.events, marketing.segments, marketing.campaigns, marketing.journeys, email.templates | no | https://www.anchorterminal.com/tools/moengage.md |\n| Mailchimp Marketing API | C | 60.2 | 660 | marketing.profiles, marketing.events, marketing.segments, marketing.campaigns, marketing.journeys, email.templates | no | https://www.anchorterminal.com/tools/mailchimp-marketing.md |\n\n## Panel reviews (0)\n\nReviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): .\n\nDesk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md\n\n## Notable\n\n- OpenAPI 3.1 spec with 349 paths and 475 operations, every one described, with 401 and 404 responses on most and an IDEMPOTENCY_KEY_REUSED error for reused keys (source: \u003chttps://docs.sequenzy.com/openapi.yaml\u003e)\n- Every API key and MCP connection is scoped, with presets from read-only and drafts-only to full access, and deletes need explicit `*:delete` permissions (source: \u003chttps://docs.sequenzy.com/concepts/mcp-permissions.md\u003e)\n- The MCP tool reference lists about 306 tools, and tool errors return a code, `howToFix` and a docs link (source: \u003chttps://docs.sequenzy.com/concepts/mcp-tools.md\u003e)\n- Dated changelog with 353 entries since 19 December 2025, the latest on 6 November 2026 (source: \u003chttps://docs.sequenzy.com/changelog.md\u003e)\n- No status page was found; status.sequenzy.com doesn't resolve, and none is linked from the site or docs\n\n- #6 of 12 in Best lifecycle marketing and customer engagement platforms for AI agents: https://www.anchorterminal.com/best/lifecycle-marketing/index.md\n- All 66 lifecycle marketing comparisons: https://www.anchorterminal.com/compare/lifecycle-marketing/index.md\n\n- #13 of 20 in Best email delivery APIs for AI agents: https://www.anchorterminal.com/best/email/index.md\n- All 174 email comparisons: https://www.anchorterminal.com/compare/email/index.md\n\n## Compare\n\n- [ActiveCampaign vs Sequenzy](https://www.anchorterminal.com/compare/activecampaign-vs-sequenzy.md): E 43.9 vs B 63.7\n- [Braze vs Sequenzy](https://www.anchorterminal.com/compare/braze-vs-sequenzy.md): C 61.8 vs B 63.7\n- [CleverTap vs Sequenzy](https://www.anchorterminal.com/compare/clevertap-vs-sequenzy.md): D 50.4 vs B 63.7\n- [Customer.io vs Sequenzy](https://www.anchorterminal.com/compare/customer-io-vs-sequenzy.md): BB 75.6 vs B 63.7\n- [Iterable vs Sequenzy](https://www.anchorterminal.com/compare/iterable-vs-sequenzy.md): C 56.3 vs B 63.7\n- [Klaviyo API + MCP vs Sequenzy](https://www.anchorterminal.com/compare/klaviyo-vs-sequenzy.md): BB 73.8 vs B 63.7\n- [Mailchimp Marketing API vs Sequenzy](https://www.anchorterminal.com/compare/mailchimp-marketing-vs-sequenzy.md): C 60.2 vs B 63.7\n- [MoEngage vs Sequenzy](https://www.anchorterminal.com/compare/moengage-vs-sequenzy.md): B 65.7 vs B 63.7\n- [Nitrosend vs Sequenzy](https://www.anchorterminal.com/compare/nitrosend-vs-sequenzy.md): B 69.4 vs B 63.7\n- [Omnisend vs Sequenzy](https://www.anchorterminal.com/compare/omnisend-vs-sequenzy.md): B 65.8 vs B 63.7\n- [Dreamlit vs Sequenzy](https://www.anchorterminal.com/compare/dreamlit-vs-sequenzy.md): C 57 vs B 63.7\n\n## Verify this listing\n\nFor the vendor. The badge or a plain link to this page verifies the listing, from a page on sequenzy.com or one of its subdomains, or the README at the root of github.com/Sequenzy/mcp. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{\"slug\": \"sequenzy\", \"url\": \"…\"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify\n\nHTML badge:\n\n```html\n\u003ca href=\"https://www.anchorterminal.com/tools/sequenzy\"\u003e\u003cimg src=\"https://www.anchorterminal.com/badges/sequenzy.svg\" alt=\"Sequenzy on Anchor Terminal\" height=\"20\"\u003e\u003c/a\u003e\n```\n\nMarkdown badge, for a README:\n\n```markdown\n[![Sequenzy on Anchor Terminal](https://www.anchorterminal.com/badges/sequenzy.svg)](https://www.anchorterminal.com/tools/sequenzy)\n```\n\nPlain link:\n\n```html\n\u003ca href=\"https://www.anchorterminal.com/tools/sequenzy\"\u003eSequenzy on Anchor Terminal\u003c/a\u003e\n```\n\n## Share this listing\n\nFor the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Sequenzy is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score.\n\n- Dark: https://www.anchorterminal.com/assets/share/sequenzy-dark.png\n- Light: https://www.anchorterminal.com/assets/share/sequenzy-light.png\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-07", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Terminal", "url": "https://www.anchorterminal.com/tools/" }, { "name": "Lifecycle marketing \u0026 customer engagement", "url": "https://www.anchorterminal.com/categories/lifecycle-marketing" }, { "name": "Sequenzy", "url": "" } ], "description": "Sequenzy is an email marketing and lifecycle automation platform for SaaS and ecommerce teams, with sequences, campaigns, transactional email, an agent inbox, push and SMS. It has a REST API, an MCP server, a CLI and a TypeScript SDK.", "facts": [ "rank #504 of 1486", "OAuth or key auth", "0 desk reviews" ], "h1": "Sequenzy", "image": "https://www.anchorterminal.com/assets/og/tools-sequenzy.png", "path": "/tools/sequenzy", "published": "2026-10-01", "section": "tools", "title": "Sequenzy review (2026): pricing, alternatives and grade B", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/tools/sequenzy" }, "tokens": { "markdown": 6450, "slim": 1630 }, "version": 1 }