Remote MCP · Endpoint

Attom MCP server

No. Attom answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/attom/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/attom
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
103 ms
Tools exposed
52 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
ATTOM MCP — Premium real estate data from ATTOM Data Solutions
Listing
From the official MCP registry (active).
Recent checks of Attom
CheckedResultHandshake
1 hour agoHandshake completed103 ms
1 day agoHandshake completed65 ms
2 days agoHandshake completed103 ms
3 days agoHandshake completed105 ms
4 days agoHandshake completed92 ms
5 days agoHandshake completed209 ms
7 days agoHandshake completed327 ms
8 days agoHandshake completed147 ms
11 days agoHandshake completed55 ms
14 days agoHandshake completed1.34 s
16 days agoHandshake completed60 ms
18 days agoHandshake completed80 ms
20 days agoHandshake completed64 ms
22 days agoHandshake completed78 ms
24 days agoHandshake completed82 ms
26 days agoHandshake completed149 ms
27 days agoHandshake completed63 ms
29 days agoHandshake completed228 ms

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.

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 Attom and makes no claim about it beyond what these checks measured.