Warp (Ringer) MCP Server

warp-mcp npm v1.1.0 Source verified

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

MCP server for the Ringer WARP platform — SIP trunking, numbers, porting, messaging, billing, and CDR analytics

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 99 − 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 − 1.2 = 99. What the published surface and source actually contain:

PointsWhat was foundCategory
−1.2 Package runs install-time scripts MTC-SUP-010 supply-chain

2. Client adoption risk — 99 − 6 = 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

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 7

critical Completed toxic-flow trifecta across toolsMTC-FLOW-002

This server (without client built-ins) exposes a complete data-exfiltration chain: cdr_export_csv → num_update_sms → msg_get. Untrusted input is ingested, private data is read, and it can be sent to an external sink via the agent composing the tools (→). Static analysis proves the primitive exists, not that a specific run will occur.

Fix: Remove one leg of the trifecta: isolate untrusted-input tools from secret-reading tools and from egress tools, or require human approval between them.

Location: flow cdr_export_csv → num_update_sms → msg_get

high Read-and-egress in one tool: "num_update_sms"MTC-FLOW-003

Tool "num_update_sms" can both read sensitive data and send data to an external destination. Even without an explicit untrusted-input leg, this is a single-call data-exfiltration path if the model is ever manipulated.

Fix: Separate reading from sending; require explicit user confirmation before egress of file/secret contents.

Location: flow num_update_sms

medium Unconstrained URL/host parameter "inbound_webhook_url" on "num_update_sms"MTC-CAP-007

Tool "num_update_sms" takes a URL/host parameter "inbound_webhook_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 num_update_sms · inputSchema.properties.inbound_webhook_url

medium Unconstrained URL/host parameter "fallback_inbound_url" on "num_update_sms"MTC-CAP-007

Tool "num_update_sms" takes a URL/host parameter "fallback_inbound_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 num_update_sms · inputSchema.properties.fallback_inbound_url

low Shell/command execution in packaging/dev tooling (dist/setup.js)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`dist/setup.js:3`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: ecFileSync } from "node:child_process"; import { stdin, stdout } from "node:process"; import { CONFIG_DIR, CONFIG_FILE,

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 dist/setup.js

low Shell/command execution in packaging/dev tooling (postinstall.js)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`postinstall.js:4`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: ecFileSync } from "node:child_process"; import { fileURLToPath } from "node:url"; import { join, dirname } from "node:pa

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 postinstall.js

low Package runs install-time scripts (postinstall)MTC-SUP-010

"warp-mcp" executes postinstall script(s) at install time. An install hook runs at install time; most are routine build/setup, but review what it does before trusting it.

Evidence: node postinstall.js

Fix: Review the scripts; install with --ignore-scripts where possible and vet what they do.

Location: package warp-mcp

Tools 135

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

  • num_update_smsnetwork egressreads sensitive data
  • cdr_export_csvingests untrusted input
  • msg_getnetwork egress
  • msg_list_numbersnetwork egress
  • msg_list_use_casesingests untrusted input
  • msg_remove_numbersnetwork egress
  • msg_sendnetwork egress
  • num_delete_sms_confignetwork egress
  • num_getnetwork egress
  • num_listingests untrusted input
Show 125 more tools ↓
  • num_ordernetwork egress
  • num_update_metadatanetwork egress
  • port_download_documentingests untrusted input
  • acct_get_balanceno sensitive capability
  • acct_get_capacityno sensitive capability
  • acct_get_utilizationno sensitive capability
  • acct_list_scopesno sensitive capability
  • bill_get_balanceno sensitive capability
  • bill_get_invoiceno sensitive capability
  • bill_get_invoice_htmlno sensitive capability
  • bill_list_invoicesno sensitive capability
  • bill_list_ledgerno sensitive capability
  • cdr_get_dashboard_statsno sensitive capability
  • cdr_get_detailsno sensitive capability
  • cdr_get_statisticsno sensitive capability
  • cdr_get_trendsno sensitive capability
  • key_getno sensitive capability
  • key_get_auditno sensitive capability
  • key_get_audit_allno sensitive capability
  • key_listno sensitive capability
  • msg_assign_numbersno sensitive capability
  • msg_create_brandno sensitive capability
  • msg_create_campaignno sensitive capability
  • msg_delete_brandno sensitive capability
  • msg_elect_cnpno sensitive capability
  • msg_get_brandno sensitive capability
  • msg_get_campaignno sensitive capability
  • msg_get_mno_statusno sensitive capability
  • msg_get_sharing_statusno sensitive capability
  • msg_get_statsno sensitive capability
  • msg_get_throughput_estimateno sensitive capability
  • msg_get_use_case_requirementsno sensitive capability
  • msg_link_brandno sensitive capability
  • msg_link_campaignno sensitive capability
  • msg_listno sensitive capability
  • msg_list_brandsno sensitive capability
  • msg_list_campaign_numbersno sensitive capability
  • msg_list_campaignsno sensitive capability
  • msg_list_carriersno sensitive capability
  • msg_list_dcasno sensitive capability
  • msg_list_entity_typesno sensitive capability
  • msg_list_verticalsno sensitive capability
  • msg_lookup_brandno sensitive capability
  • msg_lookup_campaignno sensitive capability
  • msg_nudge_cnpno sensitive capability
  • msg_resubmit_campaignno sensitive capability
  • msg_update_brandno sensitive capability
  • msg_update_campaignno sensitive capability
  • net_get_ingress_ipsno sensitive capability
  • net_get_vendor_ipsno sensitive capability
  • num_bulk_orderno sensitive capability
  • num_bulk_routeno sensitive capability
  • num_delete_voice_configno sensitive capability
  • num_get_port_out_pinno sensitive capability
  • num_releaseno sensitive capability
  • num_remove_port_out_pinno sensitive capability
  • num_searchno sensitive capability
  • num_set_port_out_pinno sensitive capability
  • num_update_voiceno sensitive capability
  • port_activateno sensitive capability
  • port_add_noteno sensitive capability
  • port_add_tnsno sensitive capability
  • port_auto_fixno sensitive capability
  • port_cancel_requestno sensitive capability
  • port_create_requestno sensitive capability
  • port_delete_documentno sensitive capability
  • port_delete_draftno sensitive capability
  • port_execute_transferno sensitive capability
  • port_generate_loano sensitive capability
  • port_get_error_groupsno sensitive capability
  • port_get_historyno sensitive capability
  • port_get_progressno sensitive capability
  • port_get_requestno sensitive capability
  • port_get_statisticsno sensitive capability
  • port_list_documentsno sensitive capability
  • port_list_notesno sensitive capability
  • port_list_requestsno sensitive capability
  • port_lookup_company_detailsno sensitive capability
  • port_lookup_einno sensitive capability
  • port_previewno sensitive capability
  • port_preview_transferno sensitive capability
  • port_resubmit_requestno sensitive capability
  • port_revalidate_tnsno sensitive capability
  • port_set_auto_activationno sensitive capability
  • port_set_group_detailsno sensitive capability
  • port_submit_requestno sensitive capability
  • port_supplement_due_dateno sensitive capability
  • port_upload_documentno sensitive capability
  • port_validate_ein_formatno sensitive capability
  • port_validate_requestno sensitive capability
  • port_verify_tin_nameno sensitive capability
  • team_create_roleno sensitive capability
  • team_delete_roleno sensitive capability
  • team_duplicate_roleno sensitive capability
  • team_get_roleno sensitive capability
  • team_list_membersno sensitive capability
  • team_list_rolesno sensitive capability
  • team_remove_memberno sensitive capability
  • team_update_member_roleno sensitive capability
  • team_update_roleno sensitive capability
  • trunk_add_ip_aclno sensitive capability
  • trunk_createno sensitive capability
  • trunk_create_credentialno sensitive capability
  • trunk_create_endpointno sensitive capability
  • trunk_deleteno sensitive capability
  • trunk_delete_credentialno sensitive capability
  • trunk_delete_endpointno sensitive capability
  • trunk_delete_ip_aclno sensitive capability
  • trunk_getno sensitive capability
  • trunk_get_cascade_previewno sensitive capability
  • trunk_get_endpointno sensitive capability
  • trunk_get_throttle_stateno sensitive capability
  • trunk_listno sensitive capability
  • trunk_list_credential_callsno sensitive capability
  • trunk_list_credential_registrationsno sensitive capability
  • trunk_list_credentialsno sensitive capability
  • trunk_list_endpointsno sensitive capability
  • trunk_list_ipsno sensitive capability
  • trunk_revoke_registrationno sensitive capability
  • trunk_rotate_credentialno sensitive capability
  • trunk_updateno sensitive capability
  • trunk_update_credentialno sensitive capability
  • trunk_update_endpointno sensitive capability
  • trunk_update_ip_aclno sensitive capability
  • warp_statusno sensitive capability

Toxic flows 2

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
v1.1.0 latest A 93/100 7 1.13.0 2026-09-07
v1.0.2 A 93/100 7 1.13.0 2026-08-27

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/warp-mcp/badge.svg)](https://mcptrustchecker.com/registry/warp-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/warp-mcp"><img src="https://mcptrustchecker.com/registry/warp-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/warp-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 warp-mcp --online

Use the free API → How scoring works

Other implementations of Warp 1

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

More in Finance & Commerce