Remote MCP · Endpoint

io.github.mifactory-bot/mifactory-spec-api MCP server

No. io.github.mifactory-bot/mifactory-spec-api answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://spec-api-mcp.vercel.app/mcp

The last check completed an MCP handshake.

Registry name
io.github.mifactory-bot/mifactory-spec-api
Transport
Streamable HTTP
Protocol negotiated
2024-11-05
Handshake latency
76 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Convert docs to agent-readable specs with criteria and constraints. $0.10/convert.
Listing
From the official MCP registry (active).
Recent checks of io.github.mifactory-bot/mifactory-spec-api
CheckedResultHandshake
1 hour agoHandshake completed76 ms
1 day agoHandshake completed65 ms
2 days agoHandshake completed84 ms
3 days agoHandshake completed66 ms
4 days agoHandshake completed67 ms
5 days agoHandshake completed79 ms
6 days agoHandshake completed72 ms
9 days agoHandshake completed118 ms
11 days agoHandshake completed61 ms
14 days agoHandshake completed70 ms
16 days agoHandshake completed64 ms
18 days agoHandshake completed76 ms
20 days agoHandshake completed788 ms
22 days agoHandshake completed71 ms
24 days agoHandshake completed76 ms
26 days agoHandshake completed74 ms
27 days agoHandshake completed103 ms
29 days agoHandshake completed122 ms

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

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 io.github.mifactory-bot/mifactory-spec-api and makes no claim about it beyond what these checks measured.