Remote MCP · Endpoint

SpriteForge Editor MCP server

No. SpriteForge Editor answered an MCP handshake 32 minutes ago.

UpLast checked 32 minutes ago

Server URL

https://www.spriteforge.tech/mcp/editor

The last check completed an MCP handshake.

Registry name
tech.spriteforge/editor
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
89 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Free pixel and tileset editor, no account: hand-edit sprites, animations and Wang tilesets in chat
Listing
From the official MCP registry (active).
Recent checks of SpriteForge Editor
CheckedResultHandshake
32 minutes agoHandshake completed89 ms
3 days agoHandshake completed65 ms
13 days agoHandshake completed80 ms
13 days agoHandshake completed49 ms
15 days agoHandshake completed100 ms
16 days agoHandshake completed114 ms
17 days agoHandshake completed79 ms
18 days agoHandshake completed106 ms
18 days agoHandshake completed405 ms
20 days agoHandshake completed77 ms
22 days agoHandshake completed71 ms
25 days agoHandshake completed115 ms
27 days agoHandshake completed987 ms

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

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