Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

DropTheHassle

NPM · DROPTHEHASSLE-MCP · SCANNED SEP 20

One platform for domain, hosting, email, analytics and your back-end. AI native, no DNS.

Available components

npm · dropthehassle-mcp 80
0 this week 80 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
Schema Quality & AI Usability84
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 761 tokens (~108/item across 7 items; 7 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "deploy_site" implies "deploy" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the DropTheHassle MCP server?

DropTheHassle runs locally as an npm package, launched with npx -y dropthehassle-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · dropthehassle-mcp

# add to Claude Code
claude mcp add bosmdavid-gif-dropthehassle -- npx -y dropthehassle-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "bosmdavid-gif-dropthehassle": {
      "command": "npx",
      "args": [
        "-y",
        "dropthehassle-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "bosmdavid-gif-dropthehassle": {
      "command": "npx",
      "args": [
        "-y",
        "dropthehassle-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add bosmdavid-gif-dropthehassle -- npx -y dropthehassle-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "bosmdavid-gif-dropthehassle": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "dropthehassle-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add bosmdavid-gif-dropthehassle --command npx --arg -y --arg dropthehassle-mcp
# ~/.hermes/config.yaml
mcp_servers:
  bosmdavid-gif-dropthehassle:
    command: "npx"
    args: ["-y", "dropthehassle-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "bosmdavid-gif-dropthehassle": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "dropthehassle-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add bosmdavid-gif-dropthehassle -t stdio -c npx -a -y dropthehassle-mcp
// mcp.json
{
  "mcpServers": {
    "bosmdavid-gif-dropthehassle": {
      "command": "npx",
      "args": [
        "-y",
        "dropthehassle-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 −2
    • Stability: pass → 0.80 functional
  • 15 Sept 26 0
    • Stability: 0.97 → pass security
  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Sept 26 −2
    • Stability: pass → 0.80 functional
  • 8 Sept 26 0
    • Stability: 0.97 → pass security
  • 7 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed npm/dropthehassle-mcp@0.3.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 7 exposed · ~761 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
choose_link ~130

Rename a site's free link to <name>.dropthehassle.app. Changing a public URL is the human owner's decision: propose the name first, and only call this with confirm=true after they explicitly said yes. Safe: the old link keeps redirecting to the new name. No money.

NameTypeReqDescription
confirmbooleanyestrue ONLY after the human owner explicitly approved this exact name.
namestringyesThe label only, e.g. "myproject" for myproject.dropthehassle.app.
site_idnumberyesThe site to rename (from list_sites).

No output schema declared.

No examples provided.

deploy_site ~158

Put a built static site online on a free link. Point it at the folder that contains index.html. Without site_id it creates a new free site (optionally with a chosen slug, e.g. "hermy" -> hermy.dropthehassle.app); with site_id it updates that existing site. Returns the live URL. Free only; never buys a name.

NameTypeReqDescription
folderstringyesAbsolute path to the built site folder (the one with index.html).
site_idnumber–Optional: an existing site to update instead of creating a new one.
slugstring–Optional: the address label for a NEW site, e.g. "myproject". Errors when taken, so propose another.

No output schema declared.

No examples provided.

list_sites ~41

List the account's sites with their live URL, status and the domains pointing at each. Use to find a site_id to deploy to or point a name at.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

point_domain ~72

Point one of the account's own domains at one of its sites (redirect the name to that site's content). Both must be on this account. No money.

NameTypeReqDescription
domainstringyesA domain already on this account.
to_site_idnumberyesThe site to point it at (from list_sites).

No output schema declared.

No examples provided.

search_domain ~70

Check whether a domain name is available to register and what it would cost (EUR). Read-only: use it to propose a REAL free name. Buying is a human step in the dashboard; this never spends money.

NameTypeReqDescription
namestringyesThe domain to check, e.g. "myidea.com".

No output schema declared.

No examples provided.

set_backend ~261

Link an HTTPS backend (Railway, Render, Fly, anywhere) behind a DropTheHassle name. With uploaded files the path rules (default /api/*) reverse-proxy to the backend and the rest stays static; without uploaded files the WHOLE site serves from the backend. WITHOUT site_id it creates a fresh FREE site first: a backend-only project goes live on its own link in one call. Perfect for a deploy script: call this with the new URL after every backend deploy. Pass url="" (with site_id) to unlink. No money.

NameTypeReqDescription
pathsarray–Optional path rules for split mode, e.g. ["/api/*", "/webhooks/*"]. Default ["/api/*"].
site_idnumber–Optional: an existing site to link (from list_sites). Omit to create a new free site served fully from the backend.
slugstring–Optional address label for a NEW site, e.g. "myapp" -> myapp.dropthehassle.app. Errors when taken.
urlstringyesThe HTTPS origin of the backend, e.g. "https://myapp.up.railway.app". Empty string (with site_id) unlinks.

No output schema declared.

No examples provided.

whoami ~29

Confirm the DropTheHassle account this AI is connected to. Call first to verify the connection works.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the DropTheHassle MCP server?

DropTheHassle is an MCP server listed in the public MCP registry as io.github.bosmdavid-gif/dropthehassle. One platform for domain, hosting, email, analytics and your back-end. AI native, no DNS. This page covers its npm package (dropthehassle-mcp).

Is the DropTheHassle MCP server safe to use?

DropTheHassle scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the DropTheHassle MCP server expose?

DropTheHassle exposes 7 tools: whoami, list_sites, search_domain, deploy_site, point_domain, and 2 more. Their descriptions and schemas cost roughly 761 tokens of context every time the server is loaded.

Is the DropTheHassle MCP server still maintained?

DropTheHassle is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the DropTheHassle MCP server under?

DropTheHassle declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.