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.
- Website
- https://taufunctions.com/
- Repository
- https://github.com/jyswee/taufunctions
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 6 hours ago | Handshake completed | 325 ms |
| 9 days ago | Handshake completed | 344 ms |
| 10 days ago | Handshake completed | 329 ms |
| 11 days ago | Handshake completed | 322 ms |
| 12 days ago | Handshake completed | 474 ms |
| 14 days ago | Handshake completed | 332 ms |
| 15 days ago | Handshake completed | 311 ms |
| 15 days ago | Handshake completed | 342 ms |
| 17 days ago | Handshake completed | 427 ms |
| 19 days ago | Handshake completed | 340 ms |
| 22 days ago | Handshake completed | 317 ms |
| 24 days ago | Handshake completed | 326 ms |
| 26 days ago | Handshake completed | 404 ms |
| 28 days ago | Handshake completed | 334 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.