cisco-cucm-mcp (calltelemetry/cisco-cucm-mcp) is an MCP server listed on the M8ven Trust Index. It scores 46 out of 100, grade D. It declares 64 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
D
Caution
46/100

cisco-cucm-mcp

MCP server for Cisco CUCM operational debugging — 61 tools covering logs, device inventory, performance monitoring, packet capture, call analysis, service control, AXL discovery, certificates, backups, CTI status, and cluster topology.

→ calltelemetry/cisco-cucm-mcp· listed on glama

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

calltelemetry

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Secret credentials may flow to a network call
3 flows detected: CUCM_PASSWORD. We can’t prove the destination matches the brand the credential belongs to.
🚨
Known vulnerabilities in dependencies: 2 critical, 5 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 2 credentials: CUCM_PASSWORD, CUCM_SSH_PASSWORD
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies2 critical5 high2 medium3 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

criticalfast-xml-parser@4.5.3GHSA-m7jm-9gc2-mpf2

fast-xml-parser has an entity encoding bypass via regex injection in DOCTYPE entity names

criticalvitest@4.0.18GHSA-5xrq-8626-4rwp

When Vitest UI server is listening, arbitrary file can be read and executed

highfast-xml-parser@4.5.3GHSA-8gc5-j5rx-235r

fast-xml-parser affected by numeric entity expansion bypassing all entity expansion limits (incomplete fix for CVE-2026-26278)

highfast-xml-parser@4.5.3GHSA-jmr7-xgp7-cmfj

fast-xml-parser affected by DoS through entity expansion in DOCTYPE (no expansion limit)

highvite@7.3.1GHSA-fx2h-pf6j-xcff

vite: `server.fs.deny` bypass on Windows alternate paths

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configCUCM_MCP_CAPTURE_RUNNING_TTL_MSRunning capture TTL (default: 6 hours)
configCUCM_MCP_CAPTURE_STOPPED_TTL_MSStopped capture TTL (default: 24 hours)
configCUCM_MCP_STATE_PATHState file path (default: ./.cucm-mcp-state.json)
configCUCM_MCP_TLS_MODEpermissive (default) or strict
configCUCM_MCP_TSHARK_TIMEOUT_MSExecution timeout (default: 60000)
configCUCM_MCP_WSDL_CACHE_DIRCache directory (default: ~/.cisco-cucm-mcp/wsdl-cache/)
🔐 secretCUCM_PASSWORD"": "<cucm-pass>",
🔐 secretCUCM_SSH_PASSWORD"": "<ssh-pass>"
configCUCM_SSH_PORTSSH port (default: 22)
configCUCM_SSH_USERNAME"": "<ssh-user>",
configCUCM_USERNAME"": "<cucm-user>",
configCUCM_VERSIONAXL API version (default: 15.0)
configMCP_TLS_MODE
configTSHARK_PATH1. env var
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

64/64 tools missing one or more hints — guess_timezone_string (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_node_service_logs (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); select_logs (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +61 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool test coverage

Only 0/64 tools referenced in tests (0%)

Write tests that reference each tool by name so every tool has at least one test.

Secrets stay with their owner

3 secret/sensitive values flow into network calls (CUCM_PASSWORD → dynamic, CUCM_PASSWORD → dynamic)

Audit where credentials are sent. A NOTION_TOKEN should only reach api.notion.com — never a third-party host.

Production dependencies are patched

1 critical, 2 high severity in production deps — fast-xml-parser@4.5.3 (critical), fast-xml-parser@4.5.3 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Dev dependencies

4 critical/high in dev-only deps (does not ship to users)

Upgrade dev dependencies when convenient.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 6 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/calltelemetry/cisco-cucm-mcp?variant=verified)](https://m8ven.ai/mcp/calltelemetry/cisco-cucm-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: f3d31375e0d8ba9fbc4abb574ebe31809ebc9655
code hash: 52f1e923573ee40cd99e5e3526478ee0a13aae368e359efad603849c07cf7134
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client