Remote MCP · Endpoint

EOR Scope MCP server

No. EOR Scope answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://mcp.eorscope.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.eorscope/eorscope-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
201 ms
Tools exposed
14 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Statutory employer cost by country, before any Employer of Record (EOR) fee.
Listing
From the official MCP registry (active).
Recent checks of EOR Scope
CheckedResultHandshake
2 hours agoHandshake completed201 ms
1 day agoHandshake completed132 ms
2 days agoHandshake completed203 ms
2 days agoHandshake completed114 ms
4 days agoHandshake completed284 ms
7 days agoHandshake completed69 ms
9 days agoHandshake completed86 ms
12 days agoHandshake completed96 ms
14 days agoHandshake completed98 ms
16 days agoHandshake completed106 ms
18 days agoHandshake completed160 ms
20 days agoHandshake completed99 ms
22 days agoHandshake completed122 ms
23 days agoHandshake completed104 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 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 EOR Scope and makes no claim about it beyond what these checks measured.