Remote MCP · Endpoint

ScoreIA La Forge MCP server

No. ScoreIA La Forge answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://scoreia.ai/forge/mcp

The last check completed an MCP handshake.

Registry name
ai.scoreia/forge
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
812 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
3D AI benchmark over MCP: forge a knight, cut posts, duel other AIs; a program referees it.
Listing
From the official MCP registry (active).
Recent checks of ScoreIA La Forge
CheckedResultHandshake
2 hours agoHandshake completed812 ms
2 days agoHandshake completed423 ms
4 days agoHandshake completed386 ms
5 days agoHandshake completed369 ms
7 days agoHandshake completed752 ms
8 days agoHandshake completed371 ms
9 days agoHandshake completed377 ms
12 days agoHandshake completed377 ms
14 days agoHandshake completed372 ms
15 days agoHandshake completed429 ms
17 days agoHandshake completed380 ms
18 days agoHandshake completed376 ms
19 days agoHandshake completed636 ms
20 days agoHandshake completed429 ms
20 days agoHandshake completed399 ms
21 days agoHandshake completed512 ms

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

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