mcp-registry/com.domainposture/mcp · v0.1.0
As of 2026-10-20 13:04 UTC, the Domainposture MCP server is up with a Glimind reliability score of 64/100 (grade C). Over the last 30 days it answered 97.9% of Glimind's liveness checks. It had 100 outages in 90 days, with a median recovery of 7 minutes.
Remote MCP server: 19 domain-hygiene and email-auth tools (DNS, SPF, DMARC, DKIM, TLS).
Claude Code
claude mcp add --transport http domainposture-mcp-server https://www.domainposture.com/mcp/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"domainposture-mcp-server": {
"type": "http",
"url": "https://www.domainposture.com/mcp/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
22 of 22 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
Reachable 97.9% of the time over the last 30 days; median recovery 7 min.
Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.
Handshake + tools/list takes ~2,357 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.domainposture%2Fmcp/fixes
{
"name": "dns_lookup",
"description": "Context lookup: Resolve a single DNS record type (A, AAAA, MX, TXT, NS, CNAME, SOA, CAA, or SRV) and return the raw answers. Use for quick, targeted lookups of one record type; prefer dossier_dns for a full multi-type DNS audit in parallel, or dossier_full for a complete domain health check. Queries Cloudflare DoH (1.1.1.1/dns-query) over HTTPS, follows CNAME chains, 5 s timeout. Returns a JSON array of answer objects with name, type, and data fields. On error, returns a string describing the DN",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"name",
"type"
],
"properties": {
"name": {
"type": "string",
"description": "Domain name or hostname to resolve, e.g. example.com or mail.example.com. FQDN preferred; relative labels are accepted."
},
"type": {
"enum": [
"A",
"AAAA",
"MX",
"TXT",
"NS",
"CNAME"
],
"type": "string",
"description": "DNS record type to query. Common choices: A (IPv4), AAAA (IPv6), MX (mail), TXT (SPF/DKIM/verification), NS (nameservers), CNAME (alias)."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "ip_lookup",
"description": "Context lookup: Resolve an IPv4 or IPv6 address to its geolocation, ASN, org name, and city/country. Use when you need network or location context for a raw IP address; prefer dns_lookup or dossier_dns for hostname resolution. Queries ipinfo.io with a server-side token — the token is never exposed to callers. Returns a JSON object with fields ip, city, region, country, org, loc, and timezone. On failure, returns an error string describing what went wrong.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"ip"
],
"properties": {
"ip": {
"type": "string",
"description": "IPv4 or IPv6 address to look up, e.g. 1.2.3.4 or 2001:db8::1. Hostnames are not accepted."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.domainposture/mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.domainposture/mcp"}) over MCP.
dossier_cors ~325 tokensdossier_dkim ~304 tokensdns_lookup ~300 tokensuser_agent_parse ~243 tokensdossier_ai_crawlers ~242 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.domainposture%2Fmcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.domainposture%2Fmcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.domainposture%2Fmcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.domainposture%2Fmcp.svg :target: https://glimind.com/server/mcp-registry%2Fcom.domainposture%2Fmcp?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:bcf014f4215a810d…, first seen 2026-10-17, included at leaf 9315 of 33,024. Version history · verify what your client received.
Compare: most reliable network servers · most reliable security servers · most reliable web servers · most reliable data servers · most reliable knowledge servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-20 13:04 UTC, the Domainposture MCP server is up with a Glimind reliability score of 64/100 (grade C). Over the last 30 days it answered 97.9% of Glimind's liveness checks. It had 100 outages in 90 days, with a median recovery of 7 minutes.
Domainposture MCP server advertises 22 tools, including dns_lookup, dossier_ai_crawlers, dossier_cors, dossier_ct_log, dossier_dkim.
Point your MCP client at this streamable-http endpoint: https://www.domainposture.com/mcp/mcp
Glimind scanned all 22 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.