Remote MCP · Endpoint

io.github.jyswee/taufunctions MCP server

No. io.github.jyswee/taufunctions answered an MCP handshake 6 hours ago.

UpLast checked 6 hours ago

Server URL

https://mcp.taufunctions.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.jyswee/taufunctions
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
325 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Serverless functions for coding agents. Deploy, invoke, monitor. 13 tools, stdio or remote.
Listing
From the official MCP registry (active).
Recent checks of io.github.jyswee/taufunctions
CheckedResultHandshake
6 hours agoHandshake completed325 ms
9 days agoHandshake completed344 ms
10 days agoHandshake completed329 ms
11 days agoHandshake completed322 ms
12 days agoHandshake completed474 ms
14 days agoHandshake completed332 ms
15 days agoHandshake completed311 ms
15 days agoHandshake completed342 ms
17 days agoHandshake completed427 ms
19 days agoHandshake completed340 ms
22 days agoHandshake completed317 ms
24 days agoHandshake completed326 ms
26 days agoHandshake completed404 ms
28 days agoHandshake completed334 ms

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

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