Shipmail MCP Server

shipmail-mcp npm v0.7.15 Source verified

Published by shipmail-to — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

Official Model Context Protocol (MCP) server for Shipmail, a business email provider with REST API, webhooks, and custom-domain inboxes for AI agents.

Trust grade
A
97/100
Last scanned get badge →
Trust
A · 97/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 97/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 3 = 97. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 1

medium Untrusted input can drive an external actionMTC-FLOW-005

Untrusted-input tools ([shipmail_get_domain, shipmail_get_mailbox, shipmail_create_mailbox_export, shipmail_get_mailbox_export, shipmail_get_mailbox_import, shipmail_get_mailbox_rule, shipmail_get_mailbox_inbox_thread, shipmail_get_mailbox_inbox_message, shipmail_read_mailbox_inbox_attachment, shipmail_get_message, shipmail_list_threads, shipmail_get_thread, shipmail_get_member, shipmail_get_webhook, shipmail_get_webhook_delivery, shipmail_get_newsletter, shipmail_get_audience, shipmail_get_audience_feed, shipmail_get_subscriber, shipmail_get_calendar_event, shipmail_get_automation, shipmail_get_booking_page]) co-exist with external-action tools ([shipmail_create_inbox_reply_draft, shipmail_prepare_staged_attachment_upload, shipmail_send_message, shipmail_list_webhooks, shipmail_get_webhook, shipmail_create_webhook, shipmail_update_webhook, shipmail_delete_webhook, shipmail_rotate_webhook_secret, shipmail_test_webhook, shipmail_list_webhook_deliveries, shipmail_get_webhook_delivery, shipmail_replay_webhook_delivery]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.

Evidence: untrusted [shipmail_get_domain, shipmail_get_mailbox, shipmail_create_mailbox_export, shipmail_get_mailbox_export, shipmail_get_mailbox_import, shipmail_get_mai

Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.

Location: flow shipmail_get_domain → shipmail_create_inbox_reply_draft

Tools 150

Each tool and what it can reach — statically extracted from the published source.

  • shipmail_get_webhookingests untrusted inputnetwork egress
  • shipmail_get_webhook_deliveryingests untrusted inputnetwork egress
  • shipmail_create_inbox_reply_draftnetwork egress
  • shipmail_create_mailbox_exportingests untrusted input
  • shipmail_create_webhooknetwork egress
  • shipmail_delete_webhooknetwork egress
  • shipmail_get_audienceingests untrusted input
  • shipmail_get_audience_feedingests untrusted input
  • shipmail_get_automationingests untrusted input
  • shipmail_get_booking_pageingests untrusted input
Show 140 more tools ↓
  • shipmail_get_calendar_eventingests untrusted input
  • shipmail_get_domainingests untrusted input
  • shipmail_get_mailboxingests untrusted input
  • shipmail_get_mailbox_exportingests untrusted input
  • shipmail_get_mailbox_importingests untrusted input
  • shipmail_get_mailbox_inbox_messageingests untrusted input
  • shipmail_get_mailbox_inbox_threadingests untrusted input
  • shipmail_get_mailbox_ruleingests untrusted input
  • shipmail_get_memberingests untrusted input
  • shipmail_get_messageingests untrusted input
  • shipmail_get_newsletteringests untrusted input
  • shipmail_get_subscriberingests untrusted input
  • shipmail_get_threadingests untrusted input
  • shipmail_list_threadsingests untrusted input
  • shipmail_list_webhook_deliveriesnetwork egress
  • shipmail_list_webhooksnetwork egress
  • shipmail_prepare_staged_attachment_uploadnetwork egress
  • shipmail_read_mailbox_inbox_attachmentingests untrusted input
  • shipmail_replay_webhook_deliverynetwork egress
  • shipmail_rotate_webhook_secretnetwork egress
  • shipmail_send_messagenetwork egress
  • shipmail_test_webhooknetwork egress
  • shipmail_update_webhooknetwork egress
  • shipmail_add_subscriberno sensitive capability
  • shipmail_add_subscribers_batchno sensitive capability
  • shipmail_cancel_mailbox_importno sensitive capability
  • shipmail_cancel_newsletterno sensitive capability
  • shipmail_cancel_scheduled_messageno sensitive capability
  • shipmail_compose_message_with_fileno sensitive capability
  • shipmail_consume_partner_mailbox_credential_grantno sensitive capability
  • shipmail_create_audienceno sensitive capability
  • shipmail_create_automationno sensitive capability
  • shipmail_create_booking_pageno sensitive capability
  • shipmail_create_calendar_eventno sensitive capability
  • shipmail_create_domainno sensitive capability
  • shipmail_create_mailboxno sensitive capability
  • shipmail_create_mailbox_app_passwordno sensitive capability
  • shipmail_create_mailbox_folderno sensitive capability
  • shipmail_create_mailbox_forwardingno sensitive capability
  • shipmail_create_mailbox_importno sensitive capability
  • shipmail_create_mailbox_ruleno sensitive capability
  • shipmail_create_newsletterno sensitive capability
  • shipmail_create_newsletter_from_changelogno sensitive capability
  • shipmail_create_partner_organizationno sensitive capability
  • shipmail_create_reply_scanno sensitive capability
  • shipmail_delete_audienceno sensitive capability
  • shipmail_delete_booking_pageno sensitive capability
  • shipmail_delete_calendar_eventno sensitive capability
  • shipmail_delete_domainno sensitive capability
  • shipmail_delete_inbox_messageno sensitive capability
  • shipmail_delete_mailboxno sensitive capability
  • shipmail_delete_mailbox_folderno sensitive capability
  • shipmail_delete_mailbox_forwardingno sensitive capability
  • shipmail_delete_mailbox_ruleno sensitive capability
  • shipmail_get_calendar_availabilityno sensitive capability
  • shipmail_get_domain_dns_recordsno sensitive capability
  • shipmail_get_mailbox_delivery_routingno sensitive capability
  • shipmail_get_partner_organizationno sensitive capability
  • shipmail_get_partner_usageno sensitive capability
  • shipmail_get_reply_scanno sensitive capability
  • shipmail_get_scheduled_messageno sensitive capability
  • shipmail_get_subscriber_by_emailno sensitive capability
  • shipmail_inject_sandbox_inboundno sensitive capability
  • shipmail_list_audiencesno sensitive capability
  • shipmail_list_automationsno sensitive capability
  • shipmail_list_booking_pagesno sensitive capability
  • shipmail_list_calendar_eventsno sensitive capability
  • shipmail_list_domainsno sensitive capability
  • shipmail_list_mailbox_app_passwordsno sensitive capability
  • shipmail_list_mailbox_foldersno sensitive capability
  • shipmail_list_mailbox_forwardingno sensitive capability
  • shipmail_list_mailbox_identitiesno sensitive capability
  • shipmail_list_mailbox_importsno sensitive capability
  • shipmail_list_mailbox_inbox_messagesno sensitive capability
  • shipmail_list_mailbox_inbox_threadsno sensitive capability
  • shipmail_list_mailbox_rulesno sensitive capability
  • shipmail_list_mailboxesno sensitive capability
  • shipmail_list_membersno sensitive capability
  • shipmail_list_message_analyticsno sensitive capability
  • shipmail_list_messagesno sensitive capability
  • shipmail_list_newsletter_assetsno sensitive capability
  • shipmail_list_newsletter_domainsno sensitive capability
  • shipmail_list_newsletter_sender_identitiesno sensitive capability
  • shipmail_list_newslettersno sensitive capability
  • shipmail_list_partner_mailbox_credential_grantsno sensitive capability
  • shipmail_list_partner_organizationsno sensitive capability
  • shipmail_list_reply_scan_resultsno sensitive capability
  • shipmail_list_scheduled_messagesno sensitive capability
  • shipmail_list_subscribersno sensitive capability
  • shipmail_list_suppressionsno sensitive capability
  • shipmail_move_inbox_messageno sensitive capability
  • shipmail_prepare_newsletter_asset_uploadno sensitive capability
  • shipmail_preview_newsletterno sensitive capability
  • shipmail_register_newsletter_assetno sensitive capability
  • shipmail_remove_subscriberno sensitive capability
  • shipmail_remove_suppressionno sensitive capability
  • shipmail_reply_to_inbox_messageno sensitive capability
  • shipmail_reply_to_inbox_threadno sensitive capability
  • shipmail_reply_to_messageno sensitive capability
  • shipmail_reply_to_threadno sensitive capability
  • shipmail_resend_partner_ownership_invitationno sensitive capability
  • shipmail_reset_mailbox_passwordno sensitive capability
  • shipmail_restore_mailbox_importno sensitive capability
  • shipmail_resubscribe_subscriberno sensitive capability
  • shipmail_resume_mailboxno sensitive capability
  • shipmail_resume_mailbox_importno sensitive capability
  • shipmail_resume_newsletterno sensitive capability
  • shipmail_revoke_audience_feedno sensitive capability
  • shipmail_revoke_mailbox_app_passwordno sensitive capability
  • shipmail_rotate_audience_feedno sensitive capability
  • shipmail_run_automationno sensitive capability
  • shipmail_run_newsletter_preflightno sensitive capability
  • shipmail_schedule_newsletterno sensitive capability
  • shipmail_search_domainsno sensitive capability
  • shipmail_send_inbox_reply_draftno sensitive capability
  • shipmail_send_newsletter_testno sensitive capability
  • shipmail_set_auto_replyno sensitive capability
  • shipmail_set_spam_filterno sensitive capability
  • shipmail_statusno sensitive capability
  • shipmail_suspend_mailboxno sensitive capability
  • shipmail_undo_mailbox_importno sensitive capability
  • shipmail_unsubscribe_subscriberno sensitive capability
  • shipmail_update_audienceno sensitive capability
  • shipmail_update_audience_feedno sensitive capability
  • shipmail_update_automationno sensitive capability
  • shipmail_update_booking_pageno sensitive capability
  • shipmail_update_calendar_eventno sensitive capability
  • shipmail_update_domainno sensitive capability
  • shipmail_update_inbox_messageno sensitive capability
  • shipmail_update_inbox_thread_attentionno sensitive capability
  • shipmail_update_mailboxno sensitive capability
  • shipmail_update_mailbox_delivery_routingno sensitive capability
  • shipmail_update_mailbox_folderno sensitive capability
  • shipmail_update_mailbox_ruleno sensitive capability
  • shipmail_update_newsletterno sensitive capability
  • shipmail_update_partner_organizationno sensitive capability
  • shipmail_update_scheduled_messageno sensitive capability
  • shipmail_update_subscriberno sensitive capability
  • shipmail_upload_newsletter_asset_with_fileno sensitive capability
  • shipmail_verify_domainno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

What this scan could not see

Versions 10

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.7.15 latest A 97/100 1 1.13.0 2026-09-07
v0.7.14 A 97/100 1 1.13.0 2026-09-01
v0.7.13 A 97/100 1 1.13.0 2026-08-30
v0.7.3 A 97/100 1 1.13.0 2026-08-28
v0.7.2 A 97/100 1 1.12.1 2026-08-02
Show 5 more versions ↓
v0.5.10 A 97/100 1 1.12.1 2026-07-29
v0.5.9 A 97/100 1 1.12.1 2026-07-28
v0.5.7 A 97/100 1 1.12.1 2026-07-27
v0.5.4 A 97/100 1 1.12.1 2026-07-27
v0.4.0 A 97/100 1 1.10.0 2026-07-25

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 97/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/shipmail-mcp/badge.svg)](https://mcptrustchecker.com/registry/shipmail-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/shipmail-mcp"><img src="https://mcptrustchecker.com/registry/shipmail-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/shipmail-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan shipmail-mcp --online

Use the free API → How scoring works

More in API Development