Remote MCP · Endpoint

Evictions API MCP server

No. Evictions API answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://evictionsapi.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.evictionsapi/evictions-api
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
89 ms
Tools exposed
21 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Start and track a US eviction case in any state or DC; a licensed attorney reviews each real case.
Listing
From the official MCP registry (active).
Recent checks of Evictions API
CheckedResultHandshake
1 hour agoHandshake completed89 ms
6 hours agoHandshake completed68 ms
2 days agoHandshake completed1.48 s
4 days agoHandshake completed943 ms
7 days agoHandshake completed1.51 s
9 days agoHandshake completed679 ms
11 days agoHandshake completed231 ms
13 days agoHandshake completed1.38 s
15 days agoHandshake completed966 ms
17 days agoHandshake completed873 ms
19 days agoHandshake completed1.37 s
21 days agoHandshake completed632 ms
23 days agoHandshake completed748 ms
24 days agoHandshake completed378 ms
25 days agoHandshake completed444 ms

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

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