Remote MCP · Endpoint

Localization Resource Integrity MCP server

No. Localization Resource Integrity answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp-factory.bowling-anthony.workers.dev/localization-resource-integrity/mcp

The last check completed an MCP handshake.

Registry name
com.mcpscores/localization-resource-integrity
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
49 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Checks the structural integrity of translated resource dictionaries against a source dictionary y...
Listing
From the official MCP registry (active).
Recent checks of Localization Resource Integrity
CheckedResultHandshake
1 hour agoHandshake completed49 ms
2 days agoHandshake completed111 ms
4 days agoHandshake completed84 ms
5 days agoHandshake completed100 ms
7 days agoHandshake completed69 ms
8 days agoHandshake completed277 ms
9 days agoHandshake completed138 ms
12 days agoHandshake completed99 ms
13 days agoHandshake completed114 ms
15 days agoHandshake completed124 ms
16 days agoHandshake completed100 ms
17 days agoHandshake completed77 ms
18 days agoHandshake completed163 ms
19 days agoHandshake completed70 ms
20 days agoHandshake completed94 ms
21 days agoHandshake completed109 ms
22 days agoHandshake completed82 ms

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

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