Nautobot MCP Server

nautobot-mcp PyPI v0.2.2

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

Nautobot MCP

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 97

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

  • get_circuitingests untrusted input
  • get_deviceingests untrusted input
  • get_ip_addressingests untrusted input
  • get_jobingests untrusted input
  • get_job_resultingests untrusted input
  • get_locationingests untrusted input
  • get_prefixingests untrusted input
  • get_rackingests untrusted input
  • get_tenantingests untrusted input
  • get_virtual_machineingests untrusted input
Show 87 more tools ↓
  • get_vlaningests untrusted input
  • list_secrets_groupsreads sensitive data
  • rest_getingests untrusted input
  • compliance_summaryno sensitive capability
  • get_available_ipsno sensitive capability
  • get_available_prefixesno sensitive capability
  • get_device_config_contextno sensitive capability
  • get_device_interfacesno sensitive capability
  • get_device_inventoryno sensitive capability
  • get_intended_configno sensitive capability
  • get_job_logsno sensitive capability
  • get_rack_elevationno sensitive capability
  • get_vm_interfacesno sensitive capability
  • graphql_introspectno sensitive capability
  • graphql_queryno sensitive capability
  • list_active_pluginsno sensitive capability
  • list_api_rootsno sensitive capability
  • list_cablesno sensitive capability
  • list_circuit_terminationsno sensitive capability
  • list_circuit_typesno sensitive capability
  • list_circuitsno sensitive capability
  • list_cluster_typesno sensitive capability
  • list_clustersno sensitive capability
  • list_compliance_featuresno sensitive capability
  • list_compliance_rulesno sensitive capability
  • list_computed_fieldsno sensitive capability
  • list_config_complianceno sensitive capability
  • list_config_contextsno sensitive capability
  • list_content_typesno sensitive capability
  • list_custom_fieldsno sensitive capability
  • list_design_deploymentsno sensitive capability
  • list_design_jobsno sensitive capability
  • list_designsno sensitive capability
  • list_device_rolesno sensitive capability
  • list_device_typesno sensitive capability
  • list_devicesno sensitive capability
  • list_endpoints_inno sensitive capability
  • list_golden_configno sensitive capability
  • list_golden_config_jobsno sensitive capability
  • list_golden_config_settingsno sensitive capability
  • list_groupsno sensitive capability
  • list_ip_addressesno sensitive capability
  • list_jobsno sensitive capability
  • list_location_typesno sensitive capability
  • list_locationsno sensitive capability
  • list_manufacturersno sensitive capability
  • list_namespacesno sensitive capability
  • list_object_permissionsno sensitive capability
  • list_onboarding_jobsno sensitive capability
  • list_platformsno sensitive capability
  • list_prefixesno sensitive capability
  • list_providersno sensitive capability
  • list_racksno sensitive capability
  • list_recent_job_resultsno sensitive capability
  • list_relationshipsno sensitive capability
  • list_rirsno sensitive capability
  • list_rolesno sensitive capability
  • list_ssot_jobsno sensitive capability
  • list_ssot_sync_logsno sensitive capability
  • list_ssot_syncsno sensitive capability
  • list_statusesno sensitive capability
  • list_tagsno sensitive capability
  • list_tenant_groupsno sensitive capability
  • list_tenantsno sensitive capability
  • list_usersno sensitive capability
  • list_virtual_machinesno sensitive capability
  • list_vlan_groupsno sensitive capability
  • list_vlansno sensitive capability
  • list_vrfsno sensitive capability
  • list_webhooksno sensitive capability
  • nautobot_statusno sensitive capability
  • nornir_plugin_infono sensitive capability
  • onboard_deviceno sensitive capability
  • rest_createno sensitive capability
  • rest_deleteno sensitive capability
  • rest_listno sensitive capability
  • rest_updateno sensitive capability
  • run_designno sensitive capability
  • run_golden_config_jobno sensitive capability
  • run_jobno sensitive capability
  • run_ssot_syncno sensitive capability
  • search_circuitsno sensitive capability
  • search_devicesno sensitive capability
  • search_ip_addressesno sensitive capability
  • search_locationsno sensitive capability
  • search_prefixesno sensitive capability
  • tenant_scope_infono sensitive capability

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
v0.2.2 latest A 96/100 0 1.14.0 2026-09-20
v0.1.2 A 99/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/nautobot-mcp/badge.svg)](https://mcptrustchecker.com/registry/nautobot-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/nautobot-mcp"><img src="https://mcptrustchecker.com/registry/nautobot-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/nautobot-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 nautobot-mcp --online --registry pypi

Use the free API → How scoring works

More in Cloud & DevOps