Remote MCP · Endpoint

Oh My Share MCP server

No. Oh My Share answered an MCP handshake 57 minutes ago.

UpLast checked 57 minutes ago

Server URL

https://openanthropic.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.shisongsong/oh-my-share
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
78 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Publish HTML/code from your agent to openanthropic.com and get a shareable link.
Listing
From the official MCP registry (active).
Recent checks of Oh My Share
CheckedResultHandshake
57 minutes agoHandshake completed78 ms
13 hours agoHandshake completed75 ms
1 day agoHandshake completed72 ms
2 days agoHandshake completed62 ms
4 days agoHandshake completed389 ms
7 days agoHandshake completed95 ms
9 days agoHandshake completed75 ms
12 days agoHandshake completed57 ms
14 days agoHandshake completed112 ms
16 days agoHandshake completed81 ms
18 days agoHandshake completed86 ms
20 days agoHandshake completed68 ms
22 days agoHandshake completed64 ms
23 days agoHandshake completed50 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 Oh My Share and makes no claim about it beyond what these checks measured.