Remote MCP · Endpoint

OgForge MCP server

No. OgForge answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://ogforge.mike-tusa.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.workers.mike-tusa.ogforge/ogforge
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
210 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Render 1200x630 Open Graph social preview images from templates; returns a cacheable PNG URL.
Listing
From the official MCP registry (active).
Recent checks of OgForge
CheckedResultHandshake
5 hours agoHandshake completed210 ms
21 hours agoHandshake completed359 ms
1 day agoHandshake completed186 ms
3 days agoHandshake completed155 ms
4 days agoHandshake completed197 ms
5 days agoHandshake completed181 ms
6 days agoHandshake completed150 ms
7 days agoHandshake completed222 ms
8 days agoHandshake completed454 ms
11 days agoHandshake completed120 ms
13 days agoHandshake completed474 ms
16 days agoHandshake completed66 ms
18 days agoHandshake completed206 ms
20 days agoHandshake completed119 ms
22 days agoHandshake completed118 ms

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

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