Remote MCP · Endpoint
ai.jeda/jeda-ai MCP server
No. ai.jeda/jeda-ai answered an MCP handshake 8 hours ago.
UpLast checked 8 hours ago
Server URL
https://mcp.jeda.ai/mcp
The last check completed an MCP handshake.
- Registry name
- ai.jeda/jeda-ai
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 920 ms
- Tools exposed
- 5 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- Visual AI for strategic thinking — SWOT, flowcharts, mindmaps, Gantt diagrams as polished SVG.
- Website
- https://jeda.ai/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 8 hours ago | Handshake completed | 920 ms |
| 2 days ago | Handshake completed | 732 ms |
| 4 days ago | Handshake completed | 770 ms |
| 5 days ago | Handshake completed | 630 ms |
| 7 days ago | Handshake completed | 965 ms |
| 8 days ago | Handshake completed | 722 ms |
| 9 days ago | Handshake completed | 487 ms |
| 12 days ago | Handshake completed | 749 ms |
| 13 days ago | Handshake completed | 716 ms |
| 15 days ago | Handshake completed | 1.62 s |
| 16 days ago | Handshake completed | 506 ms |
| 17 days ago | Handshake completed | 709 ms |
| 18 days ago | Handshake completed | 638 ms |
| 19 days ago | Handshake completed | 245 ms |
| 20 days ago | Handshake completed | 429 ms |
| 21 days ago | Handshake completed | 838 ms |
| 23 days ago | Handshake completed | 988 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.
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 ai.jeda/jeda-ai and makes no claim about it beyond what these checks measured.