Hostinger Agentic Mail vs InboxAPI

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.

InboxAPI 28

Graded on the MCP tools. The 9 October contract reading came from an unauthenticated tools/list call to the hosted endpoint, a request to the product's own endpoint, and is struck. No published document gives the server's input schemas. The tools reference lists 17 tool names with one-line descriptions, which isn't a contract, and the CLI source defines schemas only for its three local tools (0). llms.txt is published (10). The reference's one-liners say what each tool does, and a few say how, such as get_thread taking any Message-ID, with nothing on when not to call them (8 of 20). With the schemas struck, no typed inputs, enums or constraints are published (0). The docs show one sample response, for spotlighting, and no error reference (5 of 15). Releases are tagged with empty notes, there is no changelog, and the hosted tools carry no version (5 of 15). 0 + 10 + 8 + 0 + 5 + 5 = 28.

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.

InboxAPI 53

Graded as a hosted service. No x402, MPP or L402 in the docs, the tool list or the CLI source (0 of 40). The home page and FAQ say the service is free with no usage tiers, and that paid plans are planned with no price given. Send quota numbers aren't published (15 of 20). No card and no trial period (20). The CLI creates the account by proof-of-work on first use with no person involved. Owner verification, which needs a person to read a six-digit code, lifts trial restrictions the docs don't describe (18 of 20). Re-read on 4 November, the home page still says "Completely Free" with paid plans "coming soon".

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.

InboxAPI 43

Four versions were tagged on 22 September 2026 and none since (git ls-remote, 4 November). v0.3.20 carries the archive-email alias and other CLI changes since v0.3.19 (25 May), so recency is 43 days (20 of 30, 30 on 9 October). The 90-day line counts dated entries from 6 August, v0.3.20 (full), v0.3.21 (a test fix and release-workflow change, packaging-only, half), and v0.3.22 and v0.3.23, tagged on the same commit as v0.3.21 (half each), 2.5 in all, short of three (0 of 20; the line is 20 or 0). Issues and pull requests per the 9 October reading, not re-read (15 of 25). The 9 October MCP registry search came from its JSON API, which this run doesn't use, and is struck; no entry is credited (0 of 15). CI and CodeQL configured, CI passing on 22 September per the 9 October reading, npm trusted publishing, Cargo.toml on the default branch still at 0.3.14 (8 of 10). 20 + 0 + 15 + 0 + 8 = 43.

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.

InboxAPI 61

The CLI source hides nine auth and encryption tools from MCP clients (five blocked, four internal) and adds local whoami, report_bug and request_feature. The tools reference names 17 tools and the README speaks of 21 tool definitions, so an agent sees between 11 and 30 (15 of 25, plus 2 for the hidden auth tools and the plain-text default, 17). The 28 KB size of the definitions came from the struck tools/list reading and is dropped. The reference describes paginated get_emails, search by sender, subject or date range, and a count tool. Bodies can't be searched (17 of 20, per 9 October, kept). No error codes are documented. The CLI source returns plain messages for refused recipients and rate limits (8 of 20). Sends take no idempotency key. The CLI adds readOnlyHint and destructiveHint to the tools and retries a call once after a token refresh (10 of 20). A send needs three fields and setup needs no configuration. There is no SDK, only the CLI, whose subcommands print JSON (9 of 15). 17 + 17 + 8 + 10 + 9 = 61.

Hostinger Agentic Mail 70

Named tokens scoped to one order and to all or selected mailboxes, with separate SMTP/IMAP and webhook-management permissions, shown once and revocable one by one. The MCP server advertises protected-resource metadata on its 401 but documents bearer tokens only (25 of 30). Outgoing allow and block lists, with the block list winning, and mailbox-level scoping. Deletes are permanent and no read-only permission was named (14 of 20). Inbound mail is untrusted content; the docs advise the allow list for autonomous agents but give no prompt-injection guidance for message content (6 of 15). Email Logs record delivery statuses, sign-in attempts per protocol and an audit trail of mailbox setting changes, and webhooks show the last 20 deliveries (10 of 15). A valid security.txt, a HackerOne bug bounty and a responsible disclosure policy; no certification was checked (15 of 20). Total 70.

InboxAPI 57

The CLI holds an access and a refresh token in a local file written with mode 0600 and puts the token into each call, so the model never handles it. Tokens cover the whole account with no scopes, travel in the request body, and can be revoked one at a time or all at once from the CLI (20 of 30). There is no read-only mode. The CLI refuses forward_email without confirm, refuses new recipients unless a flag the model can set itself is passed, and keeps five auth and encryption tools out of MCP. The service caps an account at five external recipients (12 of 20). Inbound mail gets one of four trust levels and untrusted text is datamarked with a per-request marker, tool descriptions warn against following email content, and outbound mail containing a JWT is rejected, per the docs (14 of 15). get_sent_emails shows delivery status and an optional Claude Code hook writes a local activity log. No server-side audit log was found (6 of 15). security.txt returns 404, and no disclosure policy, bounty or certification was found. The repository runs CodeQL and publishes to npm with provenance (5 of 20). Re-read on 4 November, security.txt still answers 404, the repository has no SECURITY.md, and osv.dev lists no advisory for inboxapi or @inboxapi/cli.

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.

InboxAPI 33

Graded as a hosted service, because the mail runs on InboxAPI's servers and the CLI is a bridge to them. No status page was found on the site or in the repository (0 of 20), so there is no readable incident history (5 of 30). The limits page, re-read on 4 November, gives 100 requests a minute, 20 a minute on auth calls and five external recipient slots, and says daily and hourly send quotas are enforced without giving numbers (11 of 15, an in-between value kept and flagged). A 429 carries Retry-After per the limits page, which says to wait that many seconds before retrying, and the CLI source adds the wait to the tool error. Sends take no idempotency key (10 of 15). A rate-limit header read from a response on 9 October came from a request to the product's own endpoint and is struck; the award never rested on it. No SLA, and the terms guarantee no availability (0). Nothing on the site marks the service beta, while the CLI is at 0.3.23 and the README says functions may change without notice (7 of 10, in-between, kept and flagged). 0 + 5 + 11 + 10 + 0 + 7 = 33.