Remote MCP · Endpoint
io.github.docracy1/chasa MCP server
No. io.github.docracy1/chasa answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://api.chasa.io/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.docracy1/chasa
- Transport
- Streamable HTTP
- Protocol negotiated
- 2024-11-05
- Handshake latency
- 702 ms
- Tools exposed
- 4 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- AI invoice follow-up emails for freelancers. Draft-only, never sends for you.
- Repository
- https://github.com/docracy1/chasa
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 702 ms |
| 1 day ago | Handshake completed | 700 ms |
| 2 days ago | Handshake completed | 697 ms |
| 3 days ago | Handshake completed | 759 ms |
| 4 days ago | Handshake completed | 790 ms |
| 5 days ago | Handshake completed | 640 ms |
| 6 days ago | Handshake completed | 928 ms |
| 9 days ago | Handshake completed | 808 ms |
| 11 days ago | Handshake completed | 620 ms |
| 14 days ago | Handshake completed | 414 ms |
| 16 days ago | Handshake completed | 616 ms |
| 18 days ago | Handshake completed | 609 ms |
| 20 days ago | Handshake completed | 638 ms |
| 22 days ago | Handshake completed | 572 ms |
| 24 days ago | Handshake completed | 925 ms |
| 26 days ago | Handshake completed | 360 ms |
| 27 days ago | Handshake completed | 477 ms |
| 28 days ago | Handshake completed | 1.47 s |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
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.docracy1/chasa and makes no claim about it beyond what these checks measured.