Email infrastructure for AI agents — transactional sending, marketing campaigns, and lifecycle automation over a single contact graph. **Built so an agent can verify its own work.** Every "did that actually work?" question has a tool that answers honestly: render a template without sending it, read a delivery back from the log, replay a signed webhook against your endpoint, run a workflow and see each step it executed. **Tools document how they fail, not just what they accept.** A `200` does not mean delivered. A batch send returns `200` even when every message failed. `volanea_track_event` reports which workflows it actually triggered — an empty list means your event name has a typo, which is otherwise indistinguishable from a working integration. **Safe by default.** Test keys render and log but never deliver, even by accident. Campaigns are created as drafts — there is deliberately no tool that sends one. Cleanup previews unless you confirm, and only ever touches artifacts it created itself. ### What's here - **Discover** — project status, REST API reference, resource listings - **Build** — templates, segments, workflows, campaign drafts, webhook endpoints, sending domains - **Verify** — template rendering, test sends, delivery log, workflow runs, webhook deliveries, and whether a specific address can actually be mailed Bring your own Volanea API key. Use an `sk_test_…` key while building: everything renders and logs, nothing is delivered.
MCP readiness
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 70.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ
| Valid MCP handshake | 10/10 | initialize and tools/list both answered. |
| Live MCP endpoint | 24/25 | Endpoint answers the MCP initialize handshake (2918 ms); slow response -1. |
| Protocol revision | 8/10 | Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28. |
| Signed descriptor | n/a | No MCP standard defines a signed server descriptor. |
| Uptime (30 days) | 15/15 | 30/30 probes succeeded over 30 days (100%). |
| Tool declaration | 10/10 | Lists 27 tool(s) with descriptions. |
| Verified identity | 5/10 | Publisher declared (repository, package or homepage); claim this listing to verify domain control. |
| Freshness + modern flags | 0/5 | not seen in a source for over 30 days. |
| Auth declaration | 2/5 | Declares credential scheme: smithery_api_key. |
Compared with peers
Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.
- Readiness
- Higher than 55% of peers
- This listing 82 · peer median 81
- Latency
- Faster than 6% of peers
- This listing 1,112 ms · peer median 326 ms
Where it loses the most points, and how to win them back
- Verified identity −5
— Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
- Freshness + modern flags −5
— Keep the listing current in the registry or source it comes from.
Now: not seen in a source for over 30 days.
- Auth declaration −3
— State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.
Listed in
Directories this entry was found in.
How to connect
https://server.smithery.ai/pnkjvshsht1/volanea/mcpcurl -X POST https://server.smithery.ai/pnkjvshsht1/volanea/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'