Remote MCP · Endpoint
com.domainposture/mcp MCP server
No. com.domainposture/mcp answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://www.domainposture.com/mcp/mcp
The last check completed an MCP handshake.
- Registry name
- com.domainposture/mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 764 ms
- Tools exposed
- 22 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- Remote MCP server: 19 domain-hygiene and email-auth tools (DNS, SPF, DMARC, DKIM, TLS).
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 764 ms |
| 2 days ago | Handshake completed | 881 ms |
| 4 days ago | Handshake completed | 763 ms |
| 5 days ago | Handshake completed | 865 ms |
| 7 days ago | Handshake completed | 1.13 s |
| 8 days ago | Handshake completed | 987 ms |
| 9 days ago | Handshake completed | 814 ms |
| 12 days ago | Handshake completed | 313 ms |
| 13 days ago | Handshake completed | 759 ms |
| 15 days ago | Handshake completed | 846 ms |
| 16 days ago | Handshake completed | 770 ms |
| 17 days ago | Handshake completed | 798 ms |
| 18 days ago | Handshake completed | 762 ms |
| 19 days ago | Handshake completed | 798 ms |
| 20 days ago | Handshake completed | 782 ms |
| 21 days ago | Handshake completed | 750 ms |
| 22 days ago | Handshake completed | 783 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.
How to read this
- ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
- ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
- ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
- ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.
Listing data comes from the official MCP registry. Glide is not affiliated with com.domainposture/mcp and makes no claim about it beyond what these checks measured.