MCP servers observed by Lowdown
io.github.bosmdavid-gif/dropthehassle MCP server: daily status and tool changes
Answered initialize and tools/list on all 3 checks recorded in the last 30 days (2026-11-11 to 2026-11-17) (Lowdown checks this server every 3 days); 52 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-11; tool definitions last changed on 2026-11-17 after 6 days without change; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.bosmdavid-gif/dropthehassle
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.bosmdavid-gif/dropthehassle?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-17: the server answered initialize and tools/list.
- Observed days in the last 30: 3
- Answered initialize and tools/list: 3
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 3 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 1 of 2 compared days.
- 2026-11-17: input or output schemas changed
What tools does it list?
52 tools on 2026-11-17:
award_readinesscheck_livecheck_trademarkchoose_linkclaim_siteclear_site_passwordconnect_domaindelete_sitedeploy_sitedesign_inspirationdomain_emaildomain_renewaledit_site_fileemail_statusenable_formgallery_preferenceget_checkout_linkget_email_checkout_linkget_site_fileget_site_metricsget_site_readinessget_site_statuslist_form_submissionslist_invoiceslist_site_fileslist_site_leadslist_sitesmake_primary_domainpoint_domainremove_email_addressrename_main_inboxrequest_google_businessresend_owner_verificationresend_receiptrollback_sitesearch_domainsend_claim_mailsend_feedbackset_analytics_levelset_backendset_site_imageset_site_indexingset_site_passwordsign_insite_analyticssite_of_the_day_badgesite_statussplit_domaintransfer_domain_outturn_off_emailupdate_site_settingswhoami
MCP Registry declaration
- Registry name:
io.github.bosmdavid-gif/dropthehassle - Declared version: 0.5.2
- Status: active
- Declared hosts:
dropthehassle.com
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:io.github.bosmdavid-gif/dropthehassle", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.bosmdavid-gif/dropthehassle?menu=install-check
When running its declared package, wrap it with the stdio proxy. Since lowdown-proxy 0.1.22 the proxy adds this record (install-check) to the server's initialize response; it changes no tool result and blocks nothing:
npx -y lowdown-proxy --target mcp:io.github.bosmdavid-gif/dropthehassle -- npx -y dropthehassle-mcp
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).