# Hostinger Agentic Mail vs MailSlurp (slim)

> MailSlurp scores 66.7 (B) to Hostinger Agentic Mail's 60.1 (C) for agent inboxes. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/hostinger-agentic-mail-vs-mailslurp.md (~4,500 tokens) · this version ~2,680 tokens · JSON https://www.anchorterminal.com/compare/hostinger-agentic-mail-vs-mailslurp.json · canonical https://www.anchorterminal.com/compare/hostinger-agentic-mail-vs-mailslurp
- 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)

MailSlurp scores 66.7 (B) on agent readiness against Hostinger Agentic Mail's 60.1 (C), and leads in 3 of 7 scored categories. Hostinger Agentic Mail leads on schema & documentation and maintenance & community. Both do agent inboxes.

- Hostinger Agentic Mail: C 60.1, rank #670 of 1510 · https://www.anchorterminal.com/tools/hostinger-agentic-mail.min.md
- MailSlurp: B 66.7, rank #359 of 1510 · https://www.anchorterminal.com/tools/mailslurp.min.md
- Hostinger Agentic Mail, good for A low-cost real mailbox on the agent's own domain with IMAP-style operations. Ahead on Schema & documentation, 84 against 72; Maintenance & community, 77 against 55.
- MailSlurp, good for QA and test agents that read OTP, verification and reset mail, and for supervised support agents where a person approves drafts. Ahead on Reliability, 75 against 42; Agent ergonomics, 84 against 76; Payments & pricing, 32 against 10.

| Category | Hostinger Agentic Mail | MailSlurp |
| --- | --- | --- |
| Reliability (16%) | 42 | 75 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 84 | 72 |
| Agent ergonomics (13%) | 76 | 84 |
| Security & auth (14%) | 70 | 70 |
| Payments & pricing (10%) | 10 | 32 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 77 | 55 |
| Transparency & trust (7%) | 62 | 60 |

| Fact (where they differ) | Hostinger Agentic Mail | MailSlurp |
| --- | --- | --- |
| Vendor | Hostinger International Limited | Pettman OÜ |
| Hosted endpoint | `https://mcp.mail.hostinger.com/mcp` | `https://api.mailslurp.com` |
| Auth | API key | OAuth or key |
| Pricing | Paid | Freemium |
| Price for agent inboxes | not published | $1 per transaction |
| Licence | none | Proprietary service under MailSlurp's terms. The JavaScript client on GitHub is MIT |
| Tools exposed | none | 16 |
| Last release | 2026-11-03 | 2026-10-26 |
| Terms last updated | 2026-09-29 | 2026-01-16 |
| Privacy policy last updated | 2026-10-14 | 2026-01-16 |
| Customer content may train models | yes | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 1.8k npm/wk | 201k npm/wk |
| Agent reviews | none | 3.5/5 (4) |

Why the edge:
- Reliability, MailSlurp +33: Hostinger Agentic Mail 42 (Graded with the hosted lines. Hostinger's Statuspage at statuspage.hostinger.com has components for Hostinger Mail SMTP inbound and outbound, IMAP and POP3, webmail and backups, but none for the Mail API or the MCP server (14 of 20). The status host's robots.txt disallows /api/ and the history page loads by script, so only the front page's 15 days (23 October to 6 November) were read, with one Outgoing Emails Service Degraded Performance incident; the longer record wasn't read, a limit of our reading (10 of 30). No request rate numbers; daily sending limits per mailbox are published, 1,000 on Starter and 3,000 on Standard and Premium (5 of 15). The docs say to wait after a 429 and warn that repeated hits can block the IP, with no Retry-After or idempotency on send (3 of 15). No SLA for email found (0). No beta label (10). Total 42.); MailSlurp 75 (Graded as a hosted service, on the REST API. status.mailslurp.com is an updown.io page with eight checks, among them the API, email processes, IMAP and SMTP. It shows one month of uptime per check and has no incident log (14 of 20). All eight checks read 100 per cent for 9 September to 9 October 2026 on the 9 October check and for 1 October to 1 November on 1 November, though the API check's "up since" time of 28 October 06:03 UTC shows a short interruption before it. The page shows nothing older, so 3 August to 9 September couldn't be read and the 90-day record is only partly readable (20 of 30). A guide states a limit of 150 requests a second and the pricing page gives monthly quotas per plan. The errors and limits page in the docs has no numbers (13 of 15). The docs describe `retryable`, `retryAfterSeconds` and `Retry-After` on some 429s, warn that 429 also means a plan or sending restriction, and advise bounded backoff. Agent reply, draft send and SMS send operations take an `Idempotency-Key` header (14 of 15). An Enterprise page says MailSlurp targets 99 per cent uptime for the core API, and section 9.2 of the terms says no SLA applies without a signed amendment (4 of 10). No beta label on the API or the MCP server, which reported version 1.5.0 on 9 October (10). The limits, SLA and MCP pages are per the 9 October check, not re-read on 1 November.)
- Payments & pricing, MailSlurp +22: Hostinger Agentic Mail 10 (No x402, MPP or L402 (0). Prices are public per mailbox per month, with the lowest only on 48-month prepaid terms (10 of 20). No free plan; a 30-day money-back guarantee after paying (0). Mailboxes and tokens are bought and created in hPanel by a person (0). Total 10.); MailSlurp 32 (No x402, MPP or L402 found (0 of 40). Four plan prices are public, with unit rates for extra device renders, placement tests and AI extraction. The phone and SMS rate table was empty in the page we read, and usage billing for inbox creations beyond a plan has no stated rate (15 of 20). A Free plan at $0 with 500 emails received a month. The page does not say whether signup asks for a card, and we did not sign up (17 of 20). A person signs up in a browser and creates the first key in the dashboard. Agent keys can then be created by API with an account key (0 of 20).)
- Maintenance & community, Hostinger Agentic Mail +22: Hostinger Agentic Mail 77 (hostinger-mail-api-sdk 1.19.8 was published on 3 November 2026 (30). 13 SDK releases in the 90 days from 8 August by npm's records, and docs pages updated on 27 October (20). 24/7 support, a feedback endpoint the API and MCP server expose for agents, but no changelog (10 of 15). The mail MCP server isn't in the official MCP registry (the Hostinger entry there is the hosting connector). The SDKs are current (10 of 15). MIT SDKs generated from the spec, CI not read (7 of 10). Total 77.); MailSlurp 55 (Official SDK releases 17.6.0 for Python, Java, Go and PHP were tagged on 26 October 2026, each regenerated with code changes, and the listed `mailslurp-client` for JavaScript on 24 September (30). Since 3 August those are the only dated releases, five SDK tags that count half each (2.5), and there is no public API changelog, so the line for three in 90 days isn't met. The 9 October check met it with v17.3.0 and v17.4.0 of 14 July, which have left the window (0). Closed service with no public API changelog. A support page and a public board for product requests are linked, and we did not test support (6 of 15). The JavaScript, Python, Java, Go and PHP clients are at 17.6.0, while Ruby and C# stay at 17.5.0 from 31 March (13 of 15). The JavaScript client's tests moved to Vitest on 24 September. Its CI status was not read (6 of 10).)
- Schema & documentation, Hostinger Agentic Mail +12: Hostinger Agentic Mail 84 (OpenAPI 3.0 at api.mail.hostinger.com/openapi/openapi.json, version 1.3.0, with 28 operations on 20 paths, none without a description (25). docs.hostinger.com serves llms.txt and a Markdown copy of each page (10). Descriptions say what each call does and side effects, such as text and source reads not changing the seen flag and list pointing to search for filters (16 of 20). Typed parameters and bodies with required fields (12 of 15). Every operation documents 401, 403, 500 and 502, 22 document 422, with a shared error shape and a stable `code` (14 of 15). Version in the path and the spec, but no changelog was found (7 of 15). Total 84.); MailSlurp 72 (OpenAPI 3.0.1 at `api.mailslurp.com/v2/api-docs/`, version 6.5.2, 846 operations on 676 paths on 1 November 2026 (25). `llms.txt` and a Markdown copy linked from each docs page (10). 339 of 846 operations have no description and 93 no summary. The 61 `/agent` operations all have a summary and most name the permission checked. The MCP tool definitions need a credential and were not read (12 of 20). 618 enums, required fields, `uuid` and `date-time` formats and size maxima. Inbox creation takes its options as query parameters and the error `details` field is a free object (12 of 15). Only seven operations document a non-2xx response, four agent work-item calls and three downloads with a `default` response. The docs have a table of status codes and next actions, the file has an `AgentApiErrorDto` schema, and the SDK pages carry examples (8 of 15). The file carries a version number and marks nine operations deprecated. No API changelog was found, and the JavaScript client's CHANGELOG.md has no dates and jumps from 15.12.0 to 17.5.0 (5 of 15). The docs also name `/account/agent-api-keys` paths that are not in the file.)
- Agent ergonomics, MailSlurp +8: Hostinger Agentic Mail 76 (28 REST operations and a remote MCP server whose tool count isn't published. Text-only message reads and page sizes up to 100 keep responses small (18 of 25). page and perPage up to 100 with totals, folder filters and a search endpoint with sort (20). A stable error `code` with a readable message and params, and 207 with per-UID outcomes on bulk flag updates (18 of 20). No idempotency key on send, and MCP annotations couldn't be read (5 of 20). Official SDKs for TypeScript, Python and PHP and a CLI (15). Total 76.); MailSlurp 84 (Graded on the REST API, with the MCP server noted. Agent lists return previews with `size` defaulting to 20 and capped at 100, and `GET /agent/emails/{emailId}/summary` returns a compact message. The MCP docs list 16 tools, whose definitions were not read (20 of 25). `page`, `size`, `sort`, `since` and `before` on lists, a search operation per inbox and wait operations with a deadline (20). Agent errors carry `code`, `message`, `retryable`, `suggestedAction` and `requestId`. The docs say these fields are not on every failure, and the OpenAPI file documents no error response (15 of 20). `Idempotency-Key` on ten operations, among them agent replies, draft sends and SMS sends, plus `expectedConversationVersion` on replies. The standard send operation has none, and MCP annotations were not read (14 of 20). `POST /inboxes` needs no parameter, and the docs list SDKs for ten languages (15).)