Remote MCP · Endpoint

io.github.itsoft7/egrul-mcp MCP server

No. io.github.itsoft7/egrul-mcp answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://egrul.org/mcp/

The last check completed an MCP handshake.

Registry name
io.github.itsoft7/egrul-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
393 ms
Tools exposed
39 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
Проверка организаций, ИП и физлиц по данным ЕГРЮЛ/ЕГРИП ФНС: санкции, иноагенты, банкротство.
Listing
From the official MCP registry (active).
Recent checks of io.github.itsoft7/egrul-mcp
CheckedResultHandshake
1 hour agoHandshake completed393 ms
2 days agoHandshake completed400 ms
5 days agoFailed - the request timed out—
7 days agoHandshake completed392 ms
9 days agoHandshake completed467 ms
11 days agoHandshake completed393 ms
13 days agoHandshake completed409 ms
15 days agoHandshake completed422 ms
17 days agoHandshake completed395 ms
19 days agoHandshake completed397 ms
20 days agoHandshake completed396 ms
21 days agoHandshake completed426 ms
22 days agoHandshake completed395 ms
25 days agoHandshake completed391 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 io.github.itsoft7/egrul-mcp and makes no claim about it beyond what these checks measured.