Telecom MCP Server

mcp-telecom PyPI v0.2.0

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

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 Tool "run_command" exposes command/code executionMTC-CAP-001

Tool "run_command" appears to run shell commands or evaluate code (keyword "run_command" in tool name). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.

Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.

Location: tool run_command

low Mutating tool "run_command" declares no destructiveHintMTC-CAP-005

Tool "run_command" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool run_command

Tools 58

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

  • run_commandruns code / shell
  • backup_configno sensitive capability
  • clab_devices_yamlno sensitive capability
  • clab_generateno sensitive capability
  • clab_scenariosno sensitive capability
  • compare_configsno sensitive capability
  • compare_devicesno sensitive capability
  • compliance_checkno sensitive capability
  • compliance_check_ruleno sensitive capability
  • compliance_list_rulesno sensitive capability
Show 48 more tools ↓
  • discover_topologyno sensitive capability
  • find_pathno sensitive capability
  • get_audit_logno sensitive capability
  • health_checkno sensitive capability
  • list_device_capabilitiesno sensitive capability
  • list_devicesno sensitive capability
  • netconf_capabilitiesno sensitive capability
  • netconf_get_configno sensitive capability
  • netconf_get_operationalno sensitive capability
  • parallel_commandno sensitive capability
  • parallel_health_checkno sensitive capability
  • parallel_operationno sensitive capability
  • pool_statsno sensitive capability
  • run_vendor_operationno sensitive capability
  • show_alarmsno sensitive capability
  • show_arp_tableno sensitive capability
  • show_bgp_neighborsno sensitive capability
  • show_bgp_summaryno sensitive capability
  • show_cpuno sensitive capability
  • show_device_neighborsno sensitive capability
  • show_environmentno sensitive capability
  • show_interface_detailno sensitive capability
  • show_interfacesno sensitive capability
  • show_lag_statusno sensitive capability
  • show_lldp_neighborsno sensitive capability
  • show_log_eventsno sensitive capability
  • show_mac_tableno sensitive capability
  • show_memoryno sensitive capability
  • show_mpls_lspno sensitive capability
  • show_nokia_servicesno sensitive capability
  • show_ntp_statusno sensitive capability
  • show_ospf_neighborsno sensitive capability
  • show_routing_tableno sensitive capability
  • show_system_infono sensitive capability
  • show_topologyno sensitive capability
  • show_topology_jsonno sensitive capability
  • show_topology_mermaidno sensitive capability
  • snmp_device_overviewno sensitive capability
  • snmp_getno sensitive capability
  • snmp_walkno sensitive capability
  • start_dashboardno sensitive capability
  • start_metrics_endpointno sensitive capability
  • telemetry_historyno sensitive capability
  • telemetry_list_pathsno sensitive capability
  • telemetry_list_subscriptionsno sensitive capability
  • telemetry_queryno sensitive capability
  • telemetry_subscribeno sensitive capability
  • telemetry_unsubscribeno 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
v0.2.0 latest A 93/100 2 1.9.0 2026-07-23

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

Use the free API → How scoring works

More in Developer Tools