Remote MCP · Endpoint

Fiskmas MCP server

No. Fiskmas answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.fiskmas.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.fiskmas/fiskmas
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
316 ms
Tools exposed
21 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Hosting for AI agents: your AI client deploys Docker apps to live HTTPS URLs over MCP.
Listing
From the official MCP registry (active).
Recent checks of Fiskmas
CheckedResultHandshake
1 hour agoHandshake completed316 ms
2 days agoHandshake completed320 ms
4 days agoHandshake completed310 ms
5 days agoHandshake completed315 ms
7 days agoHandshake completed317 ms
8 days agoHandshake completed317 ms
9 days agoHandshake completed317 ms
12 days agoHandshake completed304 ms
13 days agoHandshake completed322 ms
15 days agoHandshake completed314 ms
16 days agoHandshake completed322 ms
18 days agoHandshake completed319 ms
19 days agoHandshake completed330 ms
20 days agoHandshake completed314 ms
20 days agoHandshake completed327 ms
21 days agoHandshake completed330 ms
22 days agoHandshake completed336 ms

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

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