Remote MCP · Endpoint
it.heera/agentimus MCP server
No. it.heera/agentimus answered an MCP handshake 1 hour ago.
Up · key neededLast checked 1 hour ago
Server URL
https://heera.it/wp-json/agentimus/v1/mcp
The handshake completes, but listing its tools needs credentials.
- Registry name
- it.heera/agentimus
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 183 ms
- Tools exposed
- Behind credentials
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- heera.it via Agentimus: AI readiness, traffic, request log, search & index reports, by approval.
- Website
- https://heera.it/
- Repository
- https://github.com/heera/agentimus
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 183 ms |
| 2 days ago | Handshake completed | 252 ms |
| 4 days ago | Handshake completed | 184 ms |
| 6 days ago | Handshake completed | 221 ms |
| 7 days ago | Handshake completed | 216 ms |
| 9 days ago | Handshake completed | 458 ms |
| 10 days ago | Handshake completed | 341 ms |
| 11 days ago | Handshake completed | 180 ms |
| 14 days ago | Handshake completed | 176 ms |
| 15 days ago | Handshake completed | 143 ms |
| 17 days ago | Handshake completed | 236 ms |
| 19 days ago | Handshake completed | 129 ms |
| 20 days ago | Handshake completed | 165 ms |
| 21 days ago | Handshake completed | 208 ms |
| 22 days ago | Handshake completed | 129 ms |
| 22 days ago | Handshake completed | 162 ms |
| 23 days ago | Handshake completed | 213 ms |
| 25 days ago | Handshake completed | 188 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 18 responding of 18.
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 it.heera/agentimus and makes no claim about it beyond what these checks measured.