Remote MCP · Endpoint

UTF-8 BOM presence, bytes discarded MCP server

No. UTF-8 BOM presence, bytes discarded answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/utf8sig-ok/mcp

The last check completed an MCP handshake.

Registry name
io.github.sadri-dridi/utf8sig-ok
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
15 ms
Tools exposed
31 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
UTF-8 BOM presence, bytes discarded
Repository
https://github.com/sadri-dridi/named-mcp-utilities
Listing
From the official MCP registry (active).
Recent checks of UTF-8 BOM presence, bytes discarded
CheckedResultHandshake
1 hour agoHandshake completed15 ms
8 days agoHandshake completed65 ms
9 days agoHandshake completed48 ms
11 days agoHandshake completed44 ms
12 days agoHandshake completed45 ms
13 days agoHandshake completed22 ms
14 days agoHandshake completed47 ms
15 days agoHandshake completed46 ms
16 days agoHandshake completed355 ms
19 days agoHandshake completed15 ms
22 days agoHandshake completed48 ms
24 days agoHandshake completed1.22 s
26 days agoHandshake completed43 ms
28 days agoHandshake completed28 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with UTF-8 BOM presence, bytes discarded and makes no claim about it beyond what these checks measured.