Remote MCP · Endpoint
nitur MCP server
Yes, as of 1 hour ago: the connection was refused or dropped.
DownLast checked 1 hour ago
Server URL
https://nitur.dev/api/mcp
The last check failed: the connection was refused or dropped.
- Registry name
- io.github.AmarShaked/nitur
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- Not measured yet
- Uptime, last 30 days
- 61.1% from 18 checks
- Described by its publisher as
- Create projects and read their web analytics: views, referrers, countries, custom events.
- Website
- https://nitur.dev/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Failed - the connection was refused or dropped | — |
| 2 days ago | Failed - the connection was refused or dropped | — |
| 4 days ago | Failed - the connection was refused or dropped | — |
| 6 days ago | Failed - the connection was refused or dropped | — |
| 7 days ago | Failed - the connection was refused or dropped | — |
| 9 days ago | Failed - the connection was refused or dropped | — |
| 10 days ago | Failed - the connection was refused or dropped | — |
| 11 days ago | Credentials required | — |
| 14 days ago | Credentials required | — |
| 15 days ago | Credentials required | — |
| 17 days ago | Credentials required | — |
| 18 days ago | Credentials required | — |
| 19 days ago | Credentials required | — |
| 20 days ago | Credentials required | — |
| 21 days ago | Credentials required | — |
| 22 days ago | Credentials required | — |
| 23 days ago | Credentials required | — |
| 24 days ago | Credentials required | — |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 11 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 nitur and makes no claim about it beyond what these checks measured.