Mailgi
REMOTE · API.MAILGI.XYZ
Email for AI agents: register a real inbox with no human, then send, receive and read mail.
Available components
Last scanned (20 hours ago)
Scores higher than 53% of remote servers
Unreachable for 1 day in a row. Last reached 3 Nov 2026.
Category Communication
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Authorization: fail → unverified ▼ security
- Stability: 0.07 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 1 Nov 26 66
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://api.mailgi.xyz/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.mailgi.xyz. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | present | 3599, 18130 | 8, 8 | Verified |
| mailgi.xyz. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.mailgi.xyz/mcp | Unreachable | ||
| http (plaintext) | http://api.mailgi.xyz/mcp | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
org_webhook_deliveries List organization webhook deliveries ~41
Lists recent delivery attempts for a webhook endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| orgId | string | yes | Organization ID from org_list. |
No output schema declared.
No examples provided.
org_webhook_enable Re-enable organization webhook ~44
Re-enables a webhook endpoint that was switched off after repeated failures.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| orgId | string | yes | Organization ID from org_list. |
No output schema declared.
No examples provided.
org_webhook_list List organization webhooks ~32
Lists webhook endpoints across the organization's inboxes.
| Name | Type | Req | Description |
|---|---|---|---|
| orgId | string | yes | Organization ID from org_list. |
No output schema declared.
No examples provided.
org_webhook_resend Resend organization webhook delivery ~49
Queues a delivery attempt to be sent again.
| Name | Type | Req | Description |
|---|---|---|---|
| deliveryId | string | yes | – |
| id | string | yes | – |
| orgId | string | yes | Organization ID from org_list. |
No output schema declared.
No examples provided.
register_agent Register an agent ~93
Creates a new agent with its own email address and returns its API key, shown once.
| Name | Type | Req | Description |
|---|---|---|---|
| did | string | – | Optional did:key DID; only changes the alias address. |
| domainToken | string | – | Registration token for an organization's domain. Requires localPart. |
| label | string | – | A name for your own reference. |
| localPart | string | – | Chosen address before the @, used with domainToken. |
No output schema declared.
No examples provided.
regtoken_create Create registration token ~61
Creates a token that lets an agent register its own address on this domain. Shown once.
| Name | Type | Req | Description |
|---|---|---|---|
| domainId | string | yes | Domain ID from domain_list. |
| label | string | – | – |
| orgId | string | yes | Organization ID from org_list. |
No output schema declared.
No examples provided.
regtoken_list List registration tokens ~42
Lists a domain's registration tokens.
| Name | Type | Req | Description |
|---|---|---|---|
| domainId | string | yes | Domain ID from domain_list. |
| orgId | string | yes | Organization ID from org_list. |
No output schema declared.
No examples provided.
regtoken_revoke Revoke registration token ~50
Revokes a registration token.
| Name | Type | Req | Description |
|---|---|---|---|
| domainId | string | yes | Domain ID from domain_list. |
| orgId | string | yes | Organization ID from org_list. |
| tokenId | string | yes | – |
No output schema declared.
No examples provided.
topup_lookup Look up a top-up ~42
Shows which wallet a top-up for a Mailgi address would credit, and the allowed amounts.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The agent's email or alias address. |
No output schema declared.
No examples provided.
topup_start Start a top-up ~62
Creates a card payment link for the wallet behind any Mailgi address. Give it to a human to pay.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The agent's email or alias address. |
| amountUsd | number | yes | USD, within the range from topup_lookup. |
No output schema declared.
No examples provided.
topup_status Check a top-up ~36
Returns whether a top-up payment has been paid and credited.
| Name | Type | Req | Description |
|---|---|---|---|
| sessionId | string | yes | Checkout session ID from the payment link. |
No output schema declared.
No examples provided.
webhook_create Create webhook ~54
Registers an HTTPS URL to be notified when mail arrives. The signing secret is shown once.
| Name | Type | Req | Description |
|---|---|---|---|
| eventTypes | array | – | Defaults to ["mail.received"]. |
| url | string | yes | HTTPS URL to POST notifications to. |
No output schema declared.
No examples provided.
webhook_delete Delete webhook ~20
Deletes a webhook endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
webhook_deliveries List webhook deliveries ~26
Lists recent delivery attempts for a webhook endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
webhook_enable Re-enable webhook ~29
Re-enables a webhook endpoint that was switched off after repeated failures.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
webhook_list List webhooks ~15
Lists this agent's webhook endpoints.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
webhook_resend Resend webhook delivery ~34
Queues a delivery attempt to be sent again.
| Name | Type | Req | Description |
|---|---|---|---|
| deliveryId | string | yes | – |
| id | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Mailgi MCP server?
Mailgi is a hosted endpoint at https://api.mailgi.xyz/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.mailgi.xyz
claude mcp add --transport http xyz-mailgi-mailgi 'https://api.mailgi.xyz/mcp'
What is the Mailgi MCP server?
Mailgi is an MCP server listed in the public MCP registry as xyz.mailgi/mailgi. Email for AI agents: register a real inbox with no human, then send, receive and read mail. This page covers its hosted endpoint (https://api.mailgi.xyz/mcp).
Is the Mailgi MCP server safe to use?
Mailgi scores 67 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Mailgi MCP server expose?
Mailgi exposes 67 tools: register_agent, org_login_request_code, org_login_verify, topup_lookup, topup_start, and 62 more. Their descriptions and schemas cost roughly 2,734 tokens of context every time the server is loaded.
Does the Mailgi MCP server require authentication?
Its publisher declares no required credentials for Mailgi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Mailgi MCP server still maintained?
Mailgi is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 3 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.