Remote MCP · Endpoint
io.github.jyswee/taufunctions MCP server
No. io.github.jyswee/taufunctions answered an MCP handshake 19 minutes ago.
UpLast checked 19 minutes 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
- 404 ms
- Tools exposed
- 2 tools
- Uptime, last 30 days
- 100% from 15 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 |
|---|---|---|
| 19 minutes ago | Handshake completed | 404 ms |
| 2 days ago | Handshake completed | 334 ms |
| 4 days ago | Handshake completed | 347 ms |
| 6 days ago | Handshake completed | 410 ms |
| 8 days ago | Handshake completed | 353 ms |
| 9 days ago | Handshake completed | 434 ms |
| 11 days ago | Handshake completed | 369 ms |
| 12 days ago | Handshake completed | 442 ms |
| 13 days ago | Handshake completed | 343 ms |
| 16 days ago | Handshake completed | 351 ms |
| 17 days ago | Handshake completed | 359 ms |
| 19 days ago | Handshake completed | 352 ms |
| 21 days ago | Handshake completed | 448 ms |
| 22 days ago | Handshake completed | 364 ms |
| 23 days ago | Handshake completed | 349 ms |
The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 15.
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.