Domainwaechter Website Security Check
● Activeio.github.martinschenk/domainwaechter
Passive security check of a website you operate, with score, findings and a repair guide.
Connect this server
One click to install, or copy the config below. Suits: Cursor · HTTP clients.
Or add it manually — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor):
{
"mcpServers": {
"domainwaechter": {
"url": "https://www.domainwaechter.de/api/v1/mcp"
}
}
}claude mcp add --transport http domainwaechter https://www.domainwaechter.de/api/v1/mcpcode --add-mcp '{"name":"domainwaechter","type":"http","url":"https://www.domainwaechter.de/api/v1/mcp"}'Syntax from each client's docs (Claude Code: claude mcp add; Codex: codex mcp add; VS Code: code --add-mcp). Placeholders in angle brackets are values you fill in. Codex takes hosted servers in config.toml ([mcp_servers.<name>] url = …) rather than on the command line.
A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.
- Category
- Security & Identity
- Version
- 1.0.0
- Registry
- active
- Published
- 11/20/2026
Is it safe? Is it maintained?
Serverdex check: Nov 22, 2026Mostly fine: Domainwaechter Website Security Check is maintained, hosted endpoint behind a sign-in.
- Maintained
- Active
- Last commit today (Nov 20, 2026), 0 open issues.
- Official registry
- Active
- Published as io.github.martinschenk/domainwaechter in the official MCP registry, version 1.0.0.
- Source
- No licence found
- Public repository, but GitHub reports no recognised licence (0 stars). Check the README before shipping it in a product.
- Runs
- Hosted by the publisher
- Your client talks to www.domainwaechter.de: prompts and tool arguments leave your machine for that host.
- Credentials
- Sign-in required
- The hosted endpoint answered 401/403 to a credential-free call (checked Nov 22, 2026): it wants an API key or an OAuth login first.
- Owner
- Unclaimed
- Nobody has claimed this page yet; the data above comes from the registry, GitHub and the live check.
Facts only: last commit and licence from GitHub, the entry's status from the official registry, credentials from the live check. Not a code audit — run the security scan on the endpoint yourself and see the status history.
Live check
checked Nov 22, 2026, 07:08 UTCStatus history & uptime →The endpoint is up but wants a key or an OAuth sign-in before the handshake, so its tools can only be read with an account.
Checked by Serverdex with a plain initialize + tools/list call to www.domainwaechter.de/api/v1/mcp, no credentials, about once a day. A failed check is never a removal.
On GitHub
read Nov 21, 2026- Stars
- 0
- Forks
- 0
- Last push
- Nov 20, 2026
- License
- Other
From the README
Domainwächter MCP Remote MCP server for Domainwächter (German) and ITV web (Spanish): a passive security check of a website you operate, with a repair guide your AI assistant can walk you through. • Endpoint (German market): https://www.domainwaechter.de/api/v1/mcp • Endpoint (Spanish market): https://www.itvweb.es/api/v1/mcp • Transport: Streamable HTTP, stateless, OAuth 2.1 (dynamic client registration, PKCE). Sign-in is a six-digit code sent by e-mail. Tools The server only looks at publicly reachable information, from outside. It never changes anything on your website. Changes proposed in the repair guide are made only by you, or by your assistant with your explicit consent and access you granted on purpose. The check is software, not legal or professional advice. Connect in your assistant • Claude: Settings, Connectors, add custom connector, paste the endpoint URL. • ChatGPT, Mistral Le Chat, Perplexity, Grok and other clients with remote MCP: add the endpoint URL as a remote MCP server; the client handles registration and sign-in. • Claude Code: claude mcp add --transport http domainwaechter https://www.domainwaechter.de/api/v1/mcp • Claude Code plugin: /plugin marketplace add martinschenk/domainwaechter-mcp, then /plugin install domainwaechter@domainwaechter See llms-install.md for step-by-step setup. Limits Three new analyses per account and month are free; repeated analyses of the same domain within 30 days are served from cache.…
Read the full README on GitHub →Remotes
- streamable-http
https://www.domainwaechter.de/api/v1/mcp
Alternatives to Domainwaechter Website Security Check
All Domainwaechter Website Security Check alternatives →Best Security & Identity servers →The most-starred Security & Identity servers in the index, with their live-check result.
| Server | Stars | Last push | Live check |
|---|---|---|---|
| Handsy AI | 5,215 | Nov 2026 | Local / not checked |
| HOL Guard | 1,118 | Nov 2026 | Local / not checked |
| SonarQube MCP Server | 689 | Nov 2026 | Local / not checked |
| MCP Ssh Manager | 545 | Nov 2026 | Local / not checked |
| Security Detections | 529 | Nov 2026 | Local / not checked |
Domainwaechter Website Security Check: questions people ask
- Is Domainwaechter Website Security Check a remote or a local MCP server?
- According to its entry in the official MCP registry, Domainwaechter Website Security Check ships as a hosted endpoint (streamable-http) that your client connects to by URL.
- Does Domainwaechter Website Security Check need an API key or a sign-in?
- Yes. Its hosted endpoint answered the credential-free Serverdex live check with HTTP 401/403 on Nov 22, 2026: it expects an API key in a header or an OAuth login before it lists its tools.
- Is Domainwaechter Website Security Check safe to use?
- Mostly fine: Domainwaechter Website Security Check is maintained, hosted endpoint behind a sign-in. In detail — maintained: Active; official registry: Active; source: No licence found; runs: Hosted by the publisher; credentials: Sign-in required. Serverdex check of Nov 22, 2026. This is a reading of the repository, the registry entry and the live check, not a code audit; run the Serverdex security scan on the endpoint before trusting it with real data.
- Is Domainwaechter Website Security Check still maintained?
- Active: the repository's last commit today. Last push Nov 20, 2026, 0 GitHub stars, Other licence. Read from GitHub on Nov 21, 2026.
- How do I add Domainwaechter Website Security Check to Claude, Cursor or VS Code?
- Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
More from martinschenk
All 4 servers by martinschenk →- Startups Españolas press deskFor agencies and PR teams: submit press releases, find published ones, get live URLs for reports.Developer ToolsLive
- PalimpalemWebsites for local businesses: draft, keep, edit by chat, publish; domain, DNS, e-mail, Plus.Search & WebLive
- MachineWitnessEU archive of the machine-readable web: check a domain, order a time-stamped record or extract.Search & WebLive
More Security & Identity servers
Browse all Security & Identity →matetools MCP Server
matetools
35 utility tools for AI agents — mate.tools API. Hash, regex, SEO, random, DNS, SSL, JWT.
Airlock RLS
mateuszingano
Scan a deployed site for an exposed Supabase service_role key and audit Row Level Security.
mcpAD
matteoredaelli
Read-only Active Directory / LDAP: users, groups, memberships and security audits.
Yagami AI Context Firewall
MatthewTracy
Open-source AI context firewall for governed model, retrieval, memory, and tool access.
valvur
MaverickHQ
Offline security scanning for AI-generated code: seven open-source scanners in one MCP server.
Hushdrop
maxtechera
Private, password-protected links for what AI agents build. Remote MCP with OAuth sign-in.
Add the badge to your site
Show visitors that Domainwaechter Website Security Check is listed here — it’s also the link we check for a free listing.
HTML — for your website
<a href="https://serverdex.io/server/io-github-martinschenk-domainwaechter?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="Domainwaechter Website Security Check — listed on Serverdex" width="123" height="40" loading="lazy"></a>Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.
Markdown — for your README
[](https://serverdex.io/server/io-github-martinschenk-domainwaechter?utm_source=badge)Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.
Install buttons — for your README
[](https://serverdex.io/install/cursor/io-github-martinschenk-domainwaechter) [](https://serverdex.io/install/vscode/io-github-martinschenk-domainwaechter) [](https://serverdex.io/install/claude-code/io-github-martinschenk-domainwaechter)One click opens Cursor or VS Code with this server's config prefilled; the Claude Code button lands on the one-line command. The links point at Serverdex, so when your config changes the buttons keep working.
Install buttons — HTML for your docs
<a href="https://serverdex.io/install/cursor/io-github-martinschenk-domainwaechter"><img src="https://serverdex.io/brand/install-cursor.svg" alt="Add to Cursor — via Serverdex" width="140" height="28"></a>
<a href="https://serverdex.io/install/vscode/io-github-martinschenk-domainwaechter"><img src="https://serverdex.io/brand/install-vscode.svg" alt="Add to VS Code — via Serverdex" width="147" height="28"></a>
<a href="https://serverdex.io/install/claude-code/io-github-martinschenk-domainwaechter"><img src="https://serverdex.io/brand/install-claude-code.svg" alt="Open in Claude Code — via Serverdex" width="180" height="28"></a>Same buttons as plain links for a docs page or website.
Prefer a live badge with the score, stars and live check? Score badge (links to a page that explains the number and back to this listing).