sendmux-mcp@2.2.0
VERIFIED· not startedPublisher claims: "Email inbox API and outbound sending tools for AI Agents." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
INTERNAL_API_SECRETPOSTHOG_PROJECT_TOKENSENDMUX_API_KEYSENDMUX_MCP_ALLOW_UNAUTHENTICATED_HTTPSENDMUX_MCP_AUTHORIZATION_SERVERSSENDMUX_MCP_HTTP_BEARER_TOKENSENDMUX_MCP_OAUTH_ISSUERor--mailbox-api-key/--management-api-key/--sending-api-key/--http-bearer-token/--allow-unauthenticated-httpConfiguration, not credentials: ENVIRONMENT, OPENAPI_INPUT_DIR, POSTHOG_ENVIRONMENT, POSTHOG_HOST, SENDMUX_APP_BASE_URL, SENDMUX_LIVE_E2E_APP_BASE_URL, SENDMUX_LIVE_E2E_SENDING_BASE_URL, SENDMUX_MCP_ALLOWED_ORIGINS, SENDMUX_MCP_APP_OPENAPI, SENDMUX_MCP_APP_ORIGIN, SENDMUX_MCP_HOST, SENDMUX_MCP_JWKS_URI, SENDMUX_MCP_OPENAPI_INPUT_DIR, SENDMUX_MCP_PATH, SENDMUX_MCP_PORT, SENDMUX_MCP_PROXY_URL, SENDMUX_MCP_RELEASE, SENDMUX_MCP_RESOURCE_BASE_URL, SENDMUX_MCP_RETRY_BASE_DELAY_SECONDS, SENDMUX_MCP_RETRY_MAX_ATTEMPTS, SENDMUX_MCP_RETRY_MAX_DELAY_SECONDS, SENDMUX_MCP_RETRY_MAX_ELAPSED_SECONDS, SENDMUX_MCP_SCOPES_SUPPORTED, SENDMUX_MCP_SENDING_OPENAPI, SENDMUX_MCP_STATELESS_HTTP, SENDMUX_MCP_SURFACES, SENDMUX_MCP_TIMEOUT_SECONDS, SENDMUX_MCP_TRANSPORT, SENDMUX_SENDING_BASE_URL, SENDMUX_STAGING_APP_BASE_URL, SENDMUX_STAGING_SMTP_BASE_URL- Where it talks to
- sendmux.ai (its own)Also posthog.com — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names posthog.com as well as its own vendor. The guard injects INTERNAL_API_SECRET, POSTHOG_PROJECT_TOKEN, SENDMUX_API_KEY, SENDMUX_MCP_ALLOW_UNAUTHENTICATED_HTTP, SENDMUX_MCP_AUTHORIZATION_SERVERS, SENDMUX_MCP_HTTP_BEARER_TOKEN, SENDMUX_MCP_OAUTH_ISSUER only into requests to sendmux.ai (and its subdomains) and refuses the rest.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-18 and scored it 93/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
No findings across 6,911 lines in 28 files.
Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for sendmux-mcp@2.2.0 as of 29 min ago. This is the package itself, not its dependencies.