Remote MCP · Endpoint

InvokePort MCP server

Yes, as of 48 minutes ago: the connection was refused or dropped.

DownLast checked 48 minutes ago

Server URL

https://invokeport.com/api/mcp

The last check failed: the connection was refused or dropped.

Registry name
io.github.gerefull/invokeport
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
7 tools
Uptime, last 30 days
76.9% from 13 checks
Described by its publisher as
Remote MCP: JSON repair, JSON Schema validation, JSON to TypeScript, CSV to JSON and JSON to CSV.
Listing
From the official MCP registry (active).
Recent checks of InvokePort
CheckedResultHandshake
48 minutes agoFailed - the connection was refused or dropped—
10 days agoFailed - the connection was refused or dropped—
10 days agoFailed - the connection was refused or dropped—
11 days agoHandshake completed1.44 s
12 days agoHandshake completed1.50 s
14 days agoHandshake completed1.52 s
14 days agoHandshake completed526 ms
15 days agoHandshake completed1.21 s
17 days agoHandshake completed533 ms
19 days agoHandshake completed1.02 s
21 days agoHandshake completed917 ms
24 days agoHandshake completed1.34 s
26 days agoHandshake completed974 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 10 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 InvokePort and makes no claim about it beyond what these checks measured.