Remote MCP · Endpoint

ImmigrationLayer MCP server

Yes, as of 1 hour ago: the server returned an HTTP error.

DownLast checked 1 hour ago

Server URL

https://immigrationlayer.com/mcp

The last check failed: the server returned an HTTP error.

Registry name
com.immigrationlayer/immigration-mcp
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
8 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
USCIS fees, processing times, form editions, alerts, and the Visa Bulletin. Not legal advice.
Listing
From the official MCP registry (active).
Recent checks of ImmigrationLayer
CheckedResultHandshake
1 hour agoFailed - the server returned an HTTP error—
19 hours agoHandshake completed325 ms
2 days agoHandshake completed314 ms
3 days agoHandshake completed409 ms
4 days agoHandshake completed276 ms
5 days agoHandshake completed307 ms
6 days agoHandshake completed306 ms
8 days agoHandshake completed560 ms
10 days agoHandshake completed62 ms
13 days agoHandshake completed668 ms
15 days agoHandshake completed228 ms
17 days agoHandshake completed379 ms
19 days agoHandshake completed243 ms
21 days agoHandshake completed51 ms

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

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