MCP servers › xyz.mailgi › mailgi

MCP server · registry snapshot 2026-11-01 · last tested 2026-11-01

xyz.mailgi/mailgi

by mailgi.xyz · domain (the registry's namespace rule)repository owner on GitHub: Mailgi (organization)Source ↗Website ↗

Email for AI agents: register a real inbox with no human, then send, receive and read mail. — the publisher's description

4 of 5 record checks metRead-only · tools listed 2026-11-01version 1.0.0TypeScriptstreamable HTTP67 tools

Summary

xyz.mailgi/mailgi is a remote MCP server listed in the official MCP registry at version 1.0.0, under the namespace of the domain mailgi.xyz. Its linked repository is github.com/Mailgi/mailgi; GitHub reports its owner as Mailgi, an organization. On 2026-11-01 ProtocolProbe connected to it in read-only mode and read its inventory: 67 tools, 1 resource and 0 prompts.

Record checks

4 of 5 record checks met · 4 do not apply

met: Registry entry is active and says how to run it
met: Source repository link opens
met: Repository is not archived
met: Code pushed to the repository in the 90 days before our check
not met: Repository publishes a security policy (SECURITY.md)
not applicable: Package names its licence with a standard (SPDX) identifier
not applicable: The version the registry lists can be installed and is not withdrawn
not applicable: npm package carries build provenance (attestation)
not applicable: No known critical or high advisory in the package or its dependencies

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: 0 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Operate this server? Correct a fact · README badge · Run the checks yourself

Key facts

Runs: remote (hosted by the publisher)
Transport: streamable HTTP
Your own values: none declared (not a guarantee)
Sign-in: none needed to open a session
Repository: public
Tools: 67
Last tested: 2026-11-01

Tool list size

10,587 tokens on Claude Opus 5.5

Added to every request that loads this server's tools (67 tools). Counted with Anthropic's token counter on 2026-11-01, from the tool list we read on 2026-11-01. Median across 25,738 counted servers: 2,858 tokens. How it is counted

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-11-01 (api.mailgi.xyz), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (1.0.0).

Add to your client

Observed fact

This server accepted a session without any credential and lists 25 tools whose name or declaration suggests they change data (agent_delete, mail_send, mail_delete, mail_move, mail_set_flags and 20 more). That is our reading of the names; we did not call them. Source: our connection, 2026-11-01.

How fresh this is

Live-tested: yes, a real session (not a text-only review)
Last tested: 2026-11-01
Mode: read-only (no tool calls)
Latest version: 1.0.0, published 2026-11-01 (registry, as of the 2026-11-01 snapshot)
First listed version: 2026-11-01 (earliest version still in the registry; older removed versions would be earlier)
Registry data: snapshot 2026-11-01
Package and repository: checked 2026-11-01
Engine: mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry; repository link does not open; repository archived; no push in over 365 days. Does not apply: listed version cannot be installed or is withdrawn. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

New in the registry: not in the list of 2026-10-31, listed on 2026-11-01 with version 1.0.0 (published 2026-11-01).

Source: the official MCP Registry list on 2026-10-31 and on 2026-11-01.

What it is

What does this server offer?

Observed inventory

67tools

1resources

0prompts

None of its 67 tools are described as changing anything. For 67 the reading was uncertain, so no mark is shown.

register_agenton 181 other servers
“Creates a new agent with its own email address and returns its API key, shown once.”
Publisher declares: read-only no · destructive no · idempotent no
4 inputs
- labelstring“A name for your own reference.”
- domainTokenstring“Registration token for an organization's domain.”
- localPartstring“Chosen address before the @, used with domainToken.”
- didstring“Optional did:key DID; only changes the alias address.”
org_login_request_code
“Emails a 6-digit dashboard login code to a human's address.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
1 input, 1 required
- emailstringrequired
org_login_verify
“Exchanges an emailed login code for a dashboard session token.”
Publisher declares: read-only no · destructive no · idempotent no
2 inputs, 2 required
- emailstringrequired
- codestringrequired
topup_lookup
“Shows which wallet a top-up for a Mailgi address would credit, and the allowed amounts.”
Publisher declares: read-only yes · open-world no
1 input, 1 required
- addressstringrequired“The agent's email or alias address.”
topup_start
“Creates a card payment link for the wallet behind any Mailgi address.”
Publisher declares: read-only no · destructive no · idempotent no
2 inputs, 2 required
- addressstringrequired“The agent's email or alias address.”
- amountUsdnumberrequired“USD, within the range from topup_lookup.”
topup_status
“Returns whether a top-up payment has been paid and credited.”
Publisher declares: read-only yes · open-world no
1 input, 1 required
- sessionIdstringrequired“Checkout session ID from the payment link.”
healthon 95 other servers
“Checks that the Mailgi API, its database and the mail server are up.”
Publisher declares: read-only yes · open-world no
Takes no inputs.
agent_get
“Returns this agent's profile: its addresses, label and domain.”
Publisher declares: read-only yes · open-world no
Takes no inputs.
agent_usage
“Returns this agent's daily send and API counters; the latest day is partial.”
Publisher declares: read-only yes · open-world no
2 inputs
- fromstring“ISO date, inclusive.”
- to“ISO date, inclusive.”
agent_deleteon 1 other server
“Permanently deletes this agent, its mailbox and all its API keys.”
Publisher declares: read-only no · destructive yes
Takes no inputs.
mail_liston 1 other server
“Lists message headers in the mailbox, newest first by default; filter by folder with mailboxId.”
Publisher declares: read-only yes · open-world no
4 inputs
- mailboxIdstring“Folder ID from mailbox_list.”
- limitinteger“Max messages to return.”
- positioninteger“Zero-based offset for pagination.”
- sortstring“Sort by receivedAt.”
mail_geton 1 other server
“Returns one message with its full text and HTML body.”
Publisher declares: read-only yes · open-world no
1 input, 1 required
- idstringrequired“Message ID from mail_list.”

Show 55 more tools

mail_sendon 5 other servers
“Sends an email from this agent's address.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
7 inputs, 2 required
- toarrayrequired“Recipient addresses.”
- ccarray
- bccarray
- subjectstringrequired
- textBodystring“Plain-text body.”
- htmlBodystring“HTML body.”
- replyTostring“Reply-To address.”
mail_deleteon 1 other server
“Moves a message to the Trash folder.”
Publisher declares: read-only no · destructive no · idempotent yes
1 input, 1 required
- idstringrequired
mail_moveon 2 other servers
“Moves a message to another folder.”
Publisher declares: read-only no · destructive no · idempotent yes
2 inputs, 2 required
- idstringrequired
- mailboxIdstringrequired“Destination folder ID from mailbox_list.”
mail_set_flags
“Marks a message as seen or unseen, flagged or unflagged.”
Publisher declares: read-only no · destructive no · idempotent yes
3 inputs, 1 required
- idstringrequired
- seenboolean
- flaggedboolean
mailbox_liston 2 other servers
“Lists all folders, including Inbox, Sent and Trash.”
Publisher declares: read-only yes · open-world no
Takes no inputs.
mailbox_createon 1 other server
“Creates a folder, optionally nested under another.”
Publisher declares: read-only no · destructive no · idempotent no
2 inputs, 1 required
- namestringrequired“Folder name.”
- parentIdstring“Parent folder ID for nesting.”
mailbox_rename
“Renames a folder.”
Publisher declares: read-only no · destructive no · idempotent yes
2 inputs, 2 required
- idstringrequired
- namestringrequired
mailbox_deleteon 1 other server
“Deletes a custom folder.”
Publisher declares: read-only no · destructive yes
1 input, 1 required
- idstringrequired
apikey_list
“Lists this agent's API keys.”
Publisher declares: read-only yes · open-world no
Takes no inputs.
apikey_create
“Creates another API key for this agent.”
Publisher declares: read-only no · destructive no · idempotent no
2 inputs
- labelstring
- expiresAtstring“ISO 8601 expiry date-time.”
apikey_revoke
“Revokes an API key immediately.”
Publisher declares: read-only no · destructive yes
1 input, 1 required
- keyIdstringrequired
billing_geton 2 other servers
“Returns the wallet this agent spends from: balance, prices and how to top up.”
Publisher declares: read-only yes · open-world no
Takes no inputs.
billing_topupon 2 other servers
“Creates a card payment link for this agent's wallet.”
Publisher declares: read-only no · destructive no · idempotent no
1 input, 1 required
- amountUsdnumberrequired“USD; the minimum is in billing_get.”
billing_transactions
“Lists the wallet ledger, newest first.”
Publisher declares: read-only yes · open-world no
2 inputs
- limitinteger
- offsetinteger
webhook_list
“Lists this agent's webhook endpoints.”
Publisher declares: read-only yes · open-world no
Takes no inputs.
webhook_createon 1 other server
“Registers an HTTPS URL to be notified when mail arrives.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
2 inputs, 1 required
- urlstringrequired“HTTPS URL to POST notifications to.”
- eventTypesarray“Defaults to ["mail.received"].”
webhook_delete
“Deletes a webhook endpoint.”
Publisher declares: read-only no · destructive yes
1 input, 1 required
- idstringrequired
webhook_deliveries
“Lists recent delivery attempts for a webhook endpoint.”
Publisher declares: read-only yes · open-world no
1 input, 1 required
- idstringrequired
webhook_resend
“Queues a delivery attempt to be sent again.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
2 inputs, 2 required
- idstringrequired
- deliveryIdstringrequired
webhook_enable
“Re-enables a webhook endpoint that was switched off after repeated failures.”
Publisher declares: read-only no · destructive no · idempotent yes
1 input, 1 required
- idstringrequired
org_me
“Returns the signed-in user and the organizations they belong to.”
Publisher declares: read-only yes · open-world no
Takes no inputs.
org_logout
“Revokes the current dashboard session token.”
Publisher declares: read-only no · destructive no · idempotent yes
Takes no inputs.
org_list
“Lists the organizations the signed-in user belongs to.”
Publisher declares: read-only yes · open-world no
Takes no inputs.
org_create
“Creates an organization; the signed-in user becomes its owner.”
Publisher declares: read-only no · destructive no · idempotent no
2 inputs, 1 required
- namestringrequired
- slugstring
org_get
“Returns one organization.”
Publisher declares: read-only yes · open-world no
1 input, 1 required
- orgIdstringrequired“Organization ID from org_list.”
org_rename
“Renames an organization.”
Publisher declares: read-only no · destructive no · idempotent yes
2 inputs, 2 required
- orgIdstringrequired“Organization ID from org_list.”
- namestringrequired
org_member_list
“Lists an organization's members and their roles.”
Publisher declares: read-only yes · open-world no
1 input, 1 required
- orgIdstringrequired“Organization ID from org_list.”
org_member_set_role
“Changes a member's role.”
Publisher declares: read-only no · destructive yes · idempotent yes
3 inputs, 3 required
- orgIdstringrequired“Organization ID from org_list.”
- userIdstringrequired
- rolestringrequired
org_member_remove
“Removes a member from the organization, or leaves it when userId is your own.”
Publisher declares: read-only no · destructive yes
2 inputs, 2 required
- orgIdstringrequired“Organization ID from org_list.”
- userIdstringrequired
org_invite_create
“Emails an invitation to join the organization.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
3 inputs, 2 required
- orgIdstringrequired“Organization ID from org_list.”
- emailstringrequired
- rolestring
org_invite_list
“Lists pending invitations.”
Publisher declares: read-only yes · open-world no
1 input, 1 required
- orgIdstringrequired“Organization ID from org_list.”
org_invite_revoke
“Revokes a pending invitation.”
Publisher declares: read-only no · destructive yes
2 inputs, 2 required
- orgIdstringrequired“Organization ID from org_list.”
- inviteIdstringrequired
invite_accept
“Accepts an organization invitation with the token from the invite email.”
Publisher declares: read-only no · destructive no · idempotent yes
1 input, 1 required
- tokenstringrequired
domain_attach
“Attaches a custom domain and returns the DNS records to publish.”
Publisher declares: read-only no · destructive no · idempotent no
2 inputs, 2 required
- orgIdstringrequired“Organization ID from org_list.”
- domainstringrequired“e.g.”
domain_liston 2 other servers
“Lists an organization's custom domains.”
Publisher declares: read-only yes · open-world no
1 input, 1 required
- orgIdstringrequired“Organization ID from org_list.”
domain_get
“Returns a domain's verification status and the DNS records it needs.”
Publisher declares: read-only yes · open-world no
2 inputs, 2 required
- orgIdstringrequired“Organization ID from org_list.”
- domainIdstringrequired“Domain ID from domain_list.”
domain_verifyon 1 other server
“Re-checks the domain's DNS records and verifies it if they are correct.”
Publisher declares: read-only no · destructive no · idempotent yes
2 inputs, 2 required
- orgIdstringrequired“Organization ID from org_list.”
- domainIdstringrequired“Domain ID from domain_list.”
domain_detach
“Detaches a custom domain from the organization.”
Publisher declares: read-only no · destructive yes
2 inputs, 2 required
- orgIdstringrequired“Organization ID from org_list.”
- domainIdstringrequired“Domain ID from domain_list.”
domain_inbox_list
“Lists the inboxes (agents) on a domain.”
Publisher declares: read-only yes · open-world no
2 inputs, 2 required
- orgIdstringrequired“Organization ID from org_list.”
- domainIdstringrequired“Domain ID from domain_list.”
domain_inbox_create
“Creates an inbox with a chosen address on a domain.”
Publisher declares: read-only no · destructive no · idempotent no
4 inputs, 3 required
- orgIdstringrequired“Organization ID from org_list.”
- domainIdstringrequired“Domain ID from domain_list.”
- localPartstringrequired“e.g.”
- labelstring
domain_inbox_delete
“Removes an inbox and its mail from a domain.”
Publisher declares: read-only no · destructive yes
3 inputs, 3 required
- orgIdstringrequired“Organization ID from org_list.”
- domainIdstringrequired“Domain ID from domain_list.”
- agentIdstringrequired
regtoken_create
“Creates a token that lets an agent register its own address on this domain.”
Publisher declares: read-only no · destructive no · idempotent no
3 inputs, 2 required
- orgIdstringrequired“Organization ID from org_list.”
- domainIdstringrequired“Domain ID from domain_list.”
- labelstring
regtoken_list
“Lists a domain's registration tokens.”
Publisher declares: read-only yes · open-world no
2 inputs, 2 required
- orgIdstringrequired“Organization ID from org_list.”
- domainIdstringrequired“Domain ID from domain_list.”
regtoken_revoke
“Revokes a registration token.”
Publisher declares: read-only no · destructive yes
3 inputs, 3 required
- orgIdstringrequired“Organization ID from org_list.”
- domainIdstringrequired“Domain ID from domain_list.”
- tokenIdstringrequired
org_usage
“Returns daily send, receive and API counters across the organization.”
Publisher declares: read-only yes · open-world no
4 inputs, 1 required
- orgIdstringrequired“Organization ID from org_list.”
- fromstring“ISO date, inclusive.”
- tostring“ISO date, inclusive.”
- breakdownstring“Split each day by agent.”
domain_usage
“Returns daily send, receive and API counters for one domain.”
Publisher declares: read-only yes · open-world no
5 inputs, 2 required
- orgIdstringrequired“Organization ID from org_list.”
- domainIdstringrequired“Domain ID from domain_list.”
- fromstring“ISO date, inclusive.”
- tostring“ISO date, inclusive.”
- breakdownstring“Split each day by agent.”
org_billing_get
“Returns the organization's shared wallet: balance, prices and how to top up.”
Publisher declares: read-only yes · open-world no
1 input, 1 required
- orgIdstringrequired“Organization ID from org_list.”
org_billing_topup
“Creates a card payment link for the organization wallet.”
Publisher declares: read-only no · destructive no · idempotent no
2 inputs, 2 required
- orgIdstringrequired“Organization ID from org_list.”
- amountUsdnumberrequired
org_billing_transactions
“Lists the organization wallet ledger, newest first.”
Publisher declares: read-only yes · open-world no
3 inputs, 1 required
- orgIdstringrequired“Organization ID from org_list.”
- limitinteger
- offsetinteger
org_webhook_list
“Lists webhook endpoints across the organization's inboxes.”
Publisher declares: read-only yes · open-world no
1 input, 1 required
- orgIdstringrequired“Organization ID from org_list.”
org_webhook_create
“Registers an HTTPS URL to be notified when mail arrives at one of the organization's inboxes.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
4 inputs, 3 required
- orgIdstringrequired“Organization ID from org_list.”
- agentIdstringrequired“Inbox ID from domain_inbox_list.”
- urlstringrequired“HTTPS URL to POST notifications to.”
- eventTypesarray
org_webhook_delete
“Deletes a webhook endpoint.”
Publisher declares: read-only no · destructive yes
2 inputs, 2 required
- orgIdstringrequired“Organization ID from org_list.”
- idstringrequired
org_webhook_deliveries
“Lists recent delivery attempts for a webhook endpoint.”
Publisher declares: read-only yes · open-world no
2 inputs, 2 required
- orgIdstringrequired“Organization ID from org_list.”
- idstringrequired
org_webhook_resend
“Queues a delivery attempt to be sent again.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
3 inputs, 3 required
- orgIdstringrequired“Organization ID from org_list.”
- idstringrequired
- deliveryIdstringrequired
org_webhook_enable
“Re-enables a webhook endpoint that was switched off after repeated failures.”
Publisher declares: read-only no · destructive no · idempotent yes
2 inputs, 2 required
- orgIdstringrequired“Organization ID from org_list.”
- idstringrequired

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-01.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description: 62% of 122
Tools with a description: 100% of 67
Typical description length: 57 characters

The tool set

Counted from the listing

Tools: 67
Size of the list: about 8,802 tokens for an agent to load (characters ÷ 4)
Naming: 66 of 67 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 67 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none, comparing tools within groups of 40. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-11-01 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai

Settings → Connectors → Add custom connector, then paste:
https://api.mailgi.xyz/mcp

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "mailgi": {
      "url": "https://api.mailgi.xyz/mcp"
    }
  }
}

VS Code · .vscode/mcp.json

{
  "servers": {
    "mailgi": {
      "type": "http",
      "url": "https://api.mailgi.xyz/mcp"
    }
  }
}

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"mailgi","type":"http","url":"https://api.mailgi.xyz/mcp"}'

Claude Code

claude mcp add --transport http mailgi https://api.mailgi.xyz/mcp

Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)

{
  "mcpServers": {
    "mailgi": {
      "type": "streamableHttp",
      "url": "https://api.mailgi.xyz/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}

Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project

{
  "mcpServers": {
    "mailgi": {
      "httpUrl": "https://api.mailgi.xyz/mcp"
    }
  }
}

OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project

[mcp_servers.mailgi]
url = "https://api.mailgi.xyz/mcp"

Zed · Zed settings file (command: zed: open settings file)

{
  "context_servers": {
    "mailgi": {
      "url": "https://api.mailgi.xyz/mcp"
    }
  }
}

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 --server-url https://api.mailgi.xyz/mcp --transport http

Optional settings the entry also lists (left out above): Authorization.
The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Remote endpoint api.mailgi.xyz/mcp	Session opened	matches	our test · 2026-11-01
No credential declared as required	Opened a session without any credential	matches	our test · 2026-11-01
Repository github.com/Mailgi/mailgi	Opens publicly	matches	api.github.com · 2026-11-01

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace: xyz.mailgi
GitHub owner: an organization (Mailgi)

Repository: github.com/Mailgi/mailgi
Stars: 0
Repository age: 31–90 days
Last push: 0–30 days ago
Archived: no
Security policy: none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)

Source: the registry entry and api.github.com · 2026-11-01; security policy read from GitHub · 2026-11-01.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

4 of 5 record checks met · 4 do not apply

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: 0 stars (ranked from 10)

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
MetSource repository link opensThe linked GitHub repository is public.
MetRepository is not archivedNot archived.
MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.What changes this check: GitHub's documentation describes adding a SECURITY.md from the repository's security settings: under Reporting, Security policy, Start setup. GitHub: adding a security policy
Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-01 (security policy 2026-11-01). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about xyz.mailgi/mailgi

Answered from the data above

Who publishes xyz.mailgi/mailgi?

The registry ties the namespace xyz.mailgi to the domain mailgi.xyz; only its owner can publish under it. Its linked repository is github.com/Mailgi/mailgi; GitHub reports its owner as Mailgi, an organization. These are facts from the registry and GitHub, not a rating.

Is xyz.mailgi/mailgi safe to install?

We do not rate servers as safe or unsafe. 4 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does xyz.mailgi/mailgi need an API key or sign-in?

It opened a session without any credential on 2026-11-01. The registry entry declares no required credential; no declaration is not a guarantee.

Has xyz.mailgi/mailgi been security tested?

Partly. 3 of the 14 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. ProtocolProbe publishes no security verdict for a named server.

Does xyz.mailgi/mailgi publish a security policy?

We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.

Where is the source code of xyz.mailgi/mailgi?

In github.com/Mailgi/mailgi, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-11-01

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: exercised
Fake assistant turns: not applicable
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not run · our policy
Consent handling: not testable from outside
Sign-in metadata: not applicable

3 exercised11 not run (reason given)4 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 3 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 3

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
12Hidden content
audience-hidingChecks resources that hide content from the user.exercised

Not run, with the reason · 11

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside

Does not apply to this server · 4

13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable

Source: our own test, 2026-11-01, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted a read-only session with the server's remote endpoint
895 msConnected after 0 redirects. No credential was sent or needed.
Read the inventory: 67 tools, 1 resource, 0 prompts.
4,320 msFinished: 3 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

pending: added in the weekly update

listed 2026-11-01; not classified yet

Pricing modelAI-classified

pending: added in the weekly update

the website is not read yet

Programming language

TypeScript

api.github.com · 2026-11-01

Hosting type

remote (hosted by the publisher)

registry · 2026-11-01

MCP capability

resources, tools

our test · 2026-11-01

Transport

streamable HTTP

registry · 2026-11-01

Required credentials

none declared

registry · 2026-11-01 · no declaration is not a guarantee

Package registry

does not apply

remote-only server: no package is shipped, so there is no package registry

Freshness

0–30 days

registry updatedAt · 2026-11-01

Lifecycle status

active

registry · 2026-11-01

License class

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Integrity hash

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Signature / provenance

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Dependency advisories

does not apply

ships no package, so there are no dependencies to audit

Popularity

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Publisher signals

owner: an organization · repository age: 31–90 days · stars: 0–9

api.github.com · 2026-11-01

Maintenance

active

api.github.com · 2026-11-01

Environment

the publisher's infrastructure

where it runs, from the hosting type · 2026-11-01

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “xyz.mailgi/mailgi: MCP server record.” Data checked 2026-11-01. https://protocolprobe.com/mcp/servers/xyz.mailgi/mailgi

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/xyz.mailgi/mailgi)](https://protocolprobe.com/mcp/servers/xyz.mailgi/mailgi)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology