Cml MCP Server

cml-mcp PyPI v0.31.2

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

Cisco Modeling Labs (CML) MCP Server

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/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
Moderate
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 = 96/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 − 4 = 96. 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
−3 capability blast radius (moderate) — 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 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 51

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

  • download_lab_topologyingests untrusted input
  • get_packet_capture_dataingests untrusted input
  • add_ellipse_annotationno sensitive capability
  • add_interface_to_nodeno sensitive capability
  • add_line_annotationno sensitive capability
  • add_node_to_cml_labno sensitive capability
  • add_rectangle_annotationno sensitive capability
  • add_text_annotationno sensitive capability
  • apply_link_conditioningno sensitive capability
  • check_packet_capture_statusno sensitive capability
Show 41 more tools ↓
  • clone_cml_labno sensitive capability
  • configure_cml_nodeno sensitive capability
  • connect_two_nodesno sensitive capability
  • create_cml_groupno sensitive capability
  • create_cml_userno sensitive capability
  • create_empty_labno sensitive capability
  • create_full_lab_topologyno sensitive capability
  • delete_annotation_from_labno sensitive capability
  • delete_cml_groupno sensitive capability
  • delete_cml_labno sensitive capability
  • delete_cml_nodeno sensitive capability
  • delete_cml_userno sensitive capability
  • get_all_links_for_labno sensitive capability
  • get_annotations_for_cml_labno sensitive capability
  • get_captured_packet_overviewno sensitive capability
  • get_cml_groupsno sensitive capability
  • get_cml_informationno sensitive capability
  • get_cml_lab_by_titleno sensitive capability
  • get_cml_labsno sensitive capability
  • get_cml_licensing_detailsno sensitive capability
  • get_cml_node_definitionsno sensitive capability
  • get_cml_statisticsno sensitive capability
  • get_cml_statusno sensitive capability
  • get_cml_usersno sensitive capability
  • get_console_logno sensitive capability
  • get_interfaces_for_nodeno sensitive capability
  • get_node_definition_detailno sensitive capability
  • get_nodes_for_cml_labno sensitive capability
  • modify_cml_labno sensitive capability
  • send_cli_commandno sensitive capability
  • set_cml_lab_permissionsno sensitive capability
  • start_cml_labno sensitive capability
  • start_cml_linkno sensitive capability
  • start_cml_nodeno sensitive capability
  • start_packet_captureno sensitive capability
  • stop_cml_labno sensitive capability
  • stop_cml_linkno sensitive capability
  • stop_cml_nodeno sensitive capability
  • stop_packet_captureno sensitive capability
  • wipe_cml_labno sensitive capability
  • wipe_cml_nodeno sensitive capability

What this scan could not see

Versions 3

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.31.2 latest A 96/100 0 1.13.0 2026-09-06
v0.31.1 A 96/100 0 1.13.0 2026-08-27
v0.31.0 A 96/100 0 1.13.0 2026-08-25

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

Use the free API → How scoring works

More in Cloud & DevOps