Ractermx MCP Server

@ractermx/mcp-server npm v4.0.0

Published by @ractermx — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server for managing RacterMX email forwarding via AI assistants

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/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 = 96/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 − 4 = 96. 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
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

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 3

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

Untrusted-input tools ([get_compliance_export_status, download_compliance_export]) co-exist with external-action tools ([send_email, create_webhook, update_webhook, delete_webhook, test_webhook, rotate_webhook_secret, retry_webhook_delivery, initiate_domain_transfer, create_alert_rule, update_alert_rule]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.

Evidence: untrusted [get_compliance_export_status, download_compliance_export] → sinks [send_email, create_webhook, update_webhook, delete_webhook, test_webhook, rotate_w

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

Location: flow get_compliance_export_status → send_email

medium Unconstrained URL/host parameter "url" on "create_webhook"MTC-CAP-007

Tool "create_webhook" takes a URL/host parameter "url" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).

Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.

Location: tool create_webhook · inputSchema.properties.url

medium Unconstrained URL/host parameter "url" on "update_webhook"MTC-CAP-007

Tool "update_webhook" takes a URL/host parameter "url" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).

Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.

Location: tool update_webhook · inputSchema.properties.url

Tools 131

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

  • create_alert_rulenetwork egress
  • create_webhooknetwork egress
  • delete_webhooknetwork egress
  • download_compliance_exportingests untrusted input
  • get_compliance_export_statusingests untrusted input
  • initiate_domain_transfernetwork egress
  • retry_webhook_deliverynetwork egress
  • rotate_webhook_secretnetwork egress
  • send_emailnetwork egress
  • test_webhooknetwork egress
Show 121 more tools ↓
  • update_alert_rulenetwork egress
  • update_webhooknetwork egress
  • acknowledge_driftno sensitive capability
  • add_blocklist_entryno sensitive capability
  • add_domainno sensitive capability
  • apply_dmarc_policyno sensitive capability
  • apply_security_fixno sensitive capability
  • assign_tags_to_domainno sensitive capability
  • bulk_move_domainsno sensitive capability
  • bulk_update_aliasesno sensitive capability
  • cancel_domain_transferno sensitive capability
  • check_shared_alias_availabilityno sensitive capability
  • create_aliasno sensitive capability
  • create_api_keyno sensitive capability
  • create_domain_smtp_credentialno sensitive capability
  • create_organizationno sensitive capability
  • create_routing_ruleno sensitive capability
  • create_shared_aliasno sensitive capability
  • create_smtp_credentialno sensitive capability
  • create_tagno sensitive capability
  • create_zone_recordno sensitive capability
  • delete_alert_ruleno sensitive capability
  • delete_aliasno sensitive capability
  • delete_domainno sensitive capability
  • delete_notificationno sensitive capability
  • delete_organizationno sensitive capability
  • delete_routing_ruleno sensitive capability
  • delete_shared_aliasno sensitive capability
  • delete_smtp_credentialno sensitive capability
  • delete_tagno sensitive capability
  • delete_zone_recordno sensitive capability
  • disable_anonymous_replyno sensitive capability
  • disable_wildcardno sensitive capability
  • enable_wildcardno sensitive capability
  • export_aliasesno sensitive capability
  • export_dmarc_reportno sensitive capability
  • generate_security_reportno sensitive capability
  • get_account_contextno sensitive capability
  • get_alert_ruleno sensitive capability
  • get_alert_rule_historyno sensitive capability
  • get_aliasno sensitive capability
  • get_alias_activityno sensitive capability
  • get_alias_statisticsno sensitive capability
  • get_check_catalogno sensitive capability
  • get_daily_statisticsno sensitive capability
  • get_dashboardno sensitive capability
  • get_dmarc_complianceno sensitive capability
  • get_dmarc_reportno sensitive capability
  • get_dmarc_sourcesno sensitive capability
  • get_domainno sensitive capability
  • get_domain_dns_recordsno sensitive capability
  • get_domain_healthno sensitive capability
  • get_domain_statisticsno sensitive capability
  • get_email_logno sensitive capability
  • get_mail_flowno sensitive capability
  • get_notification_preferencesno sensitive capability
  • get_quotano sensitive capability
  • get_rate_limit_statusno sensitive capability
  • get_reputation_blacklistsno sensitive capability
  • get_reputation_deliverabilityno sensitive capability
  • get_reputation_ipsno sensitive capability
  • get_reputation_recommendationsno sensitive capability
  • get_reputation_scoreno sensitive capability
  • get_reputation_trendsno sensitive capability
  • get_retention_policyno sensitive capability
  • get_routing_ruleno sensitive capability
  • get_security_checksno sensitive capability
  • get_security_historyno sensitive capability
  • get_security_scoreno sensitive capability
  • get_statisticsno sensitive capability
  • get_statistics_by_domainno sensitive capability
  • get_webhook_secretno sensitive capability
  • invite_to_organizationno sensitive capability
  • list_alert_rulesno sensitive capability
  • list_aliasesno sensitive capability
  • list_all_aliasesno sensitive capability
  • list_all_smtp_credentialsno sensitive capability
  • list_anonymous_repliesno sensitive capability
  • list_api_keysno sensitive capability
  • list_blocklistno sensitive capability
  • list_dmarc_reportsno sensitive capability
  • list_domainsno sensitive capability
  • list_email_logsno sensitive capability
  • list_notificationsno sensitive capability
  • list_organization_domainsno sensitive capability
  • list_organization_membersno sensitive capability
  • list_organizationsno sensitive capability
  • list_routing_rulesno sensitive capability
  • list_shared_aliasesno sensitive capability
  • list_shared_domainsno sensitive capability
  • list_smtp_credentialsno sensitive capability
  • list_tagsno sensitive capability
  • list_webhook_delivery_logsno sensitive capability
  • list_webhooksno sensitive capability
  • list_zone_recordsno sensitive capability
  • mark_all_notifications_readno sensitive capability
  • mark_notification_readno sensitive capability
  • move_domain_to_organizationno sensitive capability
  • regenerate_shared_alias_smtpno sensitive capability
  • remove_blocklist_entryno sensitive capability
  • remove_organization_memberno sensitive capability
  • remove_tag_from_domainno sensitive capability
  • reorder_routing_rulesno sensitive capability
  • reset_smtp_passwordno sensitive capability
  • revoke_api_keyno sensitive capability
  • searchno sensitive capability
  • set_check_overrideno sensitive capability
  • set_notification_preferencesno sensitive capability
  • set_smtp_reply_fromno sensitive capability
  • test_alert_ruleno sensitive capability
  • trigger_compliance_exportno sensitive capability
  • trigger_security_scanno sensitive capability
  • update_aliasno sensitive capability
  • update_domainno sensitive capability
  • update_organizationno sensitive capability
  • update_retention_policyno sensitive capability
  • update_routing_ruleno sensitive capability
  • update_shared_aliasno sensitive capability
  • update_tagno sensitive capability
  • update_zone_recordno sensitive capability
  • verify_domain_dnsno 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 2

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
v4.0.0 latest A 96/100 3 1.13.0 2026-09-07
v3.0.1 A 96/100 3 1.12.1 2026-08-03

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 · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/ractermx-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/ractermx-mcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/ractermx-mcp-server"><img src="https://mcptrustchecker.com/registry/ractermx-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/ractermx-mcp-server/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 @ractermx/mcp-server --online

Use the free API → How scoring works

More in API Development