Switchboard (ArsenalPAC) MCP Server

switchboard-mcp-server npm v1.0.5

Published by arsenalpac — 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.

Model Context Protocol (MCP) server for Switchboard API - enables AI assistants to access broadcast messaging, email campaigns, and contact management for progressive campaigns

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/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
High
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 = 93/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 − 7 = 93. 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
−6 capability blast radius (high) — 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 2

high Dynamic evaluation of a non-literal value (build/index.js)MTC-SRC-010

In the server's implementation (`build/index.js:897`): Evaluating a runtime value as code (rather than a fixed literal) executes whatever reaches it — a direct RCE primitive, and almost never necessary in legitimate code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: const zodSchema = eval(zodSchemaString); if (typeof zodSchema?.parse !== 'function') { throw n

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server build/index.js

high Dynamic code execution in server code (build/index.js)MTC-SRC-001

In the server's implementation (`build/index.js:897`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: const zodSchema = eval(zodSchemaString); if (typeof zodSchema?.parse !== 'function') { throw n

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server build/index.js

Tools 36

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

  • create_email_list_v1_email_lists_postno sensitive capability
  • create_email_v1_emails_postno sensitive capability
  • create_label_v1_labels_postno sensitive capability
  • create_phone_list_v1_phone_lists_postno sensitive capability
  • create_phone_v1_phones_postno sensitive capability
  • edit_label_v1_labels__label_id__patchno sensitive capability
  • export_blasts_v1_email_blasts_export_postno sensitive capability
  • export_broadcasts_v1_broadcasts_export_postno sensitive capability
  • Export_Email_Blast_Messages_v1_email_blasts__blast_id__email_messages_export_postno sensitive capability
  • export_email_list_v1_email_lists__email_list_id__export_postno sensitive capability
Show 26 more tools ↓
  • export_emails_v1_emails_export_postno sensitive capability
  • export_inbox_v1_inbox_export_postno sensitive capability
  • export_messages_v1_broadcasts__broadcast_id__phone_messages_export_postno sensitive capability
  • export_phone_list_v1_phone_lists__phone_list_id__export_postno sensitive capability
  • export_phones_v1_phones_export_postno sensitive capability
  • get_broadcast_phone_messages_v1_broadcasts__broadcast_id__phone_messages_getno sensitive capability
  • get_broadcast_v1_broadcasts__broadcast_id__getno sensitive capability
  • get_email_blast_messages_v1_email_blasts__blast_id__email_messages_getno sensitive capability
  • get_email_blast_v1_email_blasts__blast_id__getno sensitive capability
  • get_email_list_v1_email_lists__email_list_id__getno sensitive capability
  • get_job_v1_jobs__job_id__getno sensitive capability
  • get_jobs_v1_jobs__getno sensitive capability
  • get_label_v1_labels__label_id__getno sensitive capability
  • get_phone_list_v1_phone_lists__phone_list_id__getno sensitive capability
  • list_broadcasts_v1_broadcasts_getno sensitive capability
  • list_email_blasts_v1_email_blasts_getno sensitive capability
  • list_email_lists_v1_email_lists_getno sensitive capability
  • list_emails_v1_emails_getno sensitive capability
  • list_labels_v1_labels_getno sensitive capability
  • list_phone_lists_v1_phone_lists_getno sensitive capability
  • list_phones_v1_phones_getno sensitive capability
  • update_labels_v1_email_lists__email_list_id__update_labels_postno sensitive capability
  • update_labels_v1_emails_update_labels_postno sensitive capability
  • update_labels_v1_phone_lists__phone_list_id__update_labels_postno sensitive capability
  • update_labels_v1_phones_update_labels_postno sensitive capability
  • whoami_v1_whoami_getno sensitive capability

What this scan could not see

Versions 1

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
v1.0.5 latest A 93/100 2 1.13.0 2026-09-07

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

Use the free API → How scoring works

Other implementations of Switchboard 5

Independent packages implementing the same tool, scanned with the same engine. Compare all 6 side by side →

More in Business & CRM