dnsmint-mcp-server

MCPcommunitylive
v0.1.2com.dnsmintMITUpdated 23d agonpmGitHub

MCP server for DNSMint: let an agent mint and manage its own hostnames.

Endpoint healthlive
checked 8 days ago · 213ms
100% of the last 3 checks reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
39Downloads/wk
23d agoLast update
Needs 1 credential before it runs
  • DNSMINT_API_KEYAPI keyrequired

    A DNSMint API key. Create one at https://dnsmint.com/app/settings.

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorcom.dnsmint
LicenseMIT
Version0.1.2
Sourcenpm+mcp-registry
npmdnsmint-mcp-server
GitHubdnsmint/dnsmint-mcp-server
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface6 tools · none privileged
Security scan✓ Cleanv0.1.2 · 20d agoHow well does this scan work?
EvalsNone
IndexedSep 8, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

6 tools · none privileged
Statically extracted from the published packagev0.1.2 · 20d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

list_hostnamesEvery hostname this key can see, with how many are active and the plan's cap.

Every hostname this key can see, with how many are active and the plan's cap.

No input schema was published for this tool.

get_hostnameOne hostname's status and certificate mode. Does not say where it points:

One hostname's status and certificate mode. Does not say where it points:

No input schema was published for this tool.

mint_hostnameRegister an address and get back a stable hostname that survives the address changing.

Register an address and get back a stable hostname that survives the address changing.

No input schema was published for this tool.

repoint_hostnamePoint an existing hostname at a new address. This is what makes the name worth having:

Point an existing hostname at a new address. This is what makes the name worth having:

No input schema was published for this tool.

diagnose_hostnameWhy a hostname is or is not working: what the nameservers answer, what public resolvers

Why a hostname is or is not working: what the nameservers answer, what public resolvers

No input schema was published for this tool.

release_hostnamePERMANENTLY give up a hostname. Read this before calling it.

PERMANENTLY give up a hostname. Read this before calling it.

No input schema was published for this tool.

6 of 6 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

MCP server for DNSMint: let an agent mint and manage its own hostnames.

Keywords
mcpmodelcontextprotocoldnsdnsminthostname
Alternatives
Comparing tool surfaces…

Tools exposed

6 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-14 — observed resolution, not a publisher declaration.

60 packages resolved · 2 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

54 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+42 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.