Control D MCP Server

@sv3nnie/control-d-mcp npm v0.2.0

Published by @sv3nnie — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

MCP server for the Control D DNS service API

Trust grade
A
98/100
Last scanned get badge →
Trust
A · 98/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
Minimal
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 = 98/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 − 2 = 98. 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
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

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 46

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

  • add_accessno sensitive capability
  • batch_update_filtersno sensitive capability
  • create_deviceno sensitive capability
  • create_groupno sensitive capability
  • create_profileno sensitive capability
  • create_ruleno sensitive capability
  • create_sub_organizationno sensitive capability
  • delete_deviceno sensitive capability
  • delete_groupno sensitive capability
  • delete_profileno sensitive capability
Show 36 more tools ↓
  • delete_ruleno sensitive capability
  • get_caller_ipno sensitive capability
  • get_default_ruleno sensitive capability
  • get_networkno sensitive capability
  • get_organizationno sensitive capability
  • get_paymentsno sensitive capability
  • get_productsno sensitive capability
  • get_subscriptionsno sensitive capability
  • get_userno sensitive capability
  • list_accessno sensitive capability
  • list_analytics_levelsno sensitive capability
  • list_analytics_storage_regionsno sensitive capability
  • list_category_servicesno sensitive capability
  • list_device_typesno sensitive capability
  • list_devicesno sensitive capability
  • list_external_filtersno sensitive capability
  • list_filtersno sensitive capability
  • list_groupsno sensitive capability
  • list_organization_membersno sensitive capability
  • list_profile_optionsno sensitive capability
  • list_profilesno sensitive capability
  • list_proxiesno sensitive capability
  • list_rulesno sensitive capability
  • list_service_categoriesno sensitive capability
  • list_servicesno sensitive capability
  • list_sub_organizationsno sensitive capability
  • remove_accessno sensitive capability
  • update_default_ruleno sensitive capability
  • update_deviceno sensitive capability
  • update_filterno sensitive capability
  • update_groupno sensitive capability
  • update_organizationno sensitive capability
  • update_profileno sensitive capability
  • update_profile_optionno sensitive capability
  • update_ruleno sensitive capability
  • update_serviceno 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 98/100 0 1.12.1 2026-07-29

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

Use the free API → How scoring works

More in API Development