Remote MCP · Endpoint

Functions MCP server

No. Functions answered an MCP handshake 42 minutes ago.

Up · key neededLast checked 42 minutes ago

Server URL

https://functions.manager.myinfrastructure.click/mcp

The handshake completes, but listing its tools needs credentials.

Registry name
click.myinfrastructure/functions
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
275 ms
Tools exposed
Behind credentials
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Publicar e rodar funções, logs, variáveis e agendamentos
Listing
From the official MCP registry (active).
Recent checks of Functions
CheckedResultHandshake
42 minutes agoHandshake completed275 ms
3 days agoHandshake completed227 ms
12 days agoHandshake completed312 ms
12 days agoHandshake completed97 ms
14 days agoHandshake completed230 ms
15 days agoHandshake completed237 ms
16 days agoHandshake completed237 ms
17 days agoHandshake completed102 ms
18 days agoHandshake completed119 ms
19 days agoHandshake completed123 ms
22 days agoHandshake completed247 ms
25 days agoHandshake completed89 ms
27 days agoHandshake completed55 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 Functions and makes no claim about it beyond what these checks measured.