Cisco Cucm MCP Server
@calltelemetry/cisco-cucm-mcp
npm
v0.7.1
Published by @calltelemetry — 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 CUCM operational debugging: DIME logs, AXL config, RIS device status, PerfMon counters, service health, packet capture, and pcap analysis
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:
| Points | Adoption-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 1
high Shell/command execution in server code (build/index.js)MTC-SRC-002
In the server's implementation (`build/index.js:13`): 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: File as ts } from "node:child_process"; import { homedir as ss } from "node:os"; import { inflateRawSync as nt } from "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 64
Each tool and what it can reach — statically extracted from the published source.
axl_download_wsdlingests untrusted inputcdr_download_fileingests untrusted inputcoordinated_capture_stop_analyzeingests untrusted inputdownload_batchingests untrusted inputdownload_fileingests untrusted inputpacket_capture_download_from_stateingests untrusted inputpacket_capture_stop_and_downloadingests untrusted inputphone_capture_downloadingests untrusted inputaxl_describe_operationno sensitive capabilityaxl_executeno sensitive capability
Show 54 more tools ↓
axl_list_operationsno sensitive capabilitycdr_get_file_listno sensitive capabilitycdr_get_file_list_minutesno sensitive capabilitycert_listno sensitive capabilitycluster_health_checkno sensitive capabilitycoordinated_capture_startno sensitive capabilitydrf_backup_historyno sensitive capabilitydrf_backup_statusno sensitive capabilityget_service_statusno sensitive capabilityget_trace_configno sensitive capabilityguess_timezone_stringno sensitive capabilitylist_node_service_logsno sensitive capabilitylist_services_extendedno sensitive capabilitypacket_capture_listno sensitive capabilitypacket_capture_startno sensitive capabilitypacket_capture_state_clearno sensitive capabilitypacket_capture_state_getno sensitive capabilitypacket_capture_state_listno sensitive capabilitypacket_capture_stopno sensitive capabilitypcap_call_summaryno sensitive capabilitypcap_protocol_filterno sensitive capabilitypcap_rtp_streamsno sensitive capabilitypcap_sccp_messagesno sensitive capabilitypcap_sip_callsno sensitive capabilityperfmon_add_counterno sensitive capabilityperfmon_close_sessionno sensitive capabilityperfmon_collect_counter_datano sensitive capabilityperfmon_collect_session_datano sensitive capabilityperfmon_list_counterno sensitive capabilityperfmon_list_instanceno sensitive capabilityperfmon_open_sessionno sensitive capabilityperfmon_remove_counterno sensitive capabilityphone_packet_capture_enableno sensitive capabilityrestart_serviceno sensitive capabilitysdl_trace_call_flowno sensitive capabilitysdl_trace_parseno sensitive capabilityselect_cm_deviceno sensitive capabilityselect_cm_device_allno sensitive capabilityselect_cm_device_by_ipno sensitive capabilityselect_cti_itemno sensitive capabilityselect_cti_tracesno sensitive capabilityselect_curri_logsno sensitive capabilityselect_logsno sensitive capabilityselect_logs_clusterno sensitive capabilityselect_logs_minutesno sensitive capabilityselect_sip_tracesno sensitive capabilityselect_syslog_minutesno sensitive capabilityset_trace_levelno sensitive capabilityshow_network_clusterno sensitive capabilityshow_network_eth0no sensitive capabilityshow_statusno sensitive capabilityshow_versionno sensitive capabilitystart_serviceno sensitive capabilitystop_serviceno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (64 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.7.1 latest |
A 93/100 | 1 | 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.
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 @calltelemetry/cisco-cucm-mcp --onlineMore in Cloud & DevOps
Operator control CLI for AdGuard Home with an MCP adapter
interacting with Aliyun (Alibaba Cloud) services through This MCP server provides tools.
MCP server for the Aspro.Cloud REST API
MCP server for Atlassian Confluence and Jira Cloud APIs
AuroraCloud-first MCP server that exposes AuroraDocs workspace data to Claude Desktop and other AI agents
The official AWS Knowledge Base retrieval server using Bedrock Agent Runtime.