Onboarding request: Sequenzy email marketing MCP

[polnikale]

Requesting GitHub MCP Registry onboarding for Sequenzy, following the OSS-registry-first process in discussion #1257.

• Verified active registry name: io.github.polnikale/sequenzy-mcp
• Latest published registry version: 0.0.80, status: active, isLatest: true as checked today.
• Registry lookup: https://registry.modelcontextprotocol.io/v0.1/servers?search=sequenzy
• Remote transport: Streamable HTTP at https://api.sequenzy.com/v1/mcp
• Authentication: each customer uses their own Sequenzy OAuth authorization or API key.
• Public repository: https://github.com/Sequenzy/mcp
• License: MIT
• Local npm package: @sequenzy/mcp (stdio, SEQUENZY_API_KEY). The latest active registry version currently describes the remote endpoint.

Sequenzy lets agents manage email contacts, segments, campaigns, automation sequences, transactional email, and analytics for SaaS and ecommerce. A typical workflow is to draft an onboarding sequence, target a saved segment, and inspect performance. The service has a free tier; the MCP implementation is open source.

GitHub registry check https://api.mcp.github.com/v0.1/servers?search=sequenzy currently returns zero entries.

For accuracy: the public repository and release configuration are moving to the organization namespace io.github.Sequenzy/mcp, but that name is not currently returned by the official registry lookup. This request uses the verified active personal namespace above rather than claiming the migration is complete. Please advise if that namespace transition should be completed before curation.