Remote MCP · Endpoint
Licita MCP server
Yes, as of 58 minutes ago: the TLS certificate could not be verified.
DownLast checked 58 minutes ago
Server URL
https://eutenders.duckdns.org/mcp
The last check failed: the TLS certificate could not be verified.
- Registry name
- io.github.gastonrey/licita-app
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- Not measured yet
- Uptime, last 30 days
- 3 checks from 3 checks
- Described by its publisher as
- Spanish/EU procurement intelligence for agents; x402 or prepaid credits.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 58 minutes ago | Failed - the TLS certificate could not be verified | — |
| 1 day ago | Failed - the TLS certificate could not be verified | — |
| 2 days ago | Failed - the TLS certificate could not be verified | — |
The last 3 checks. Full history is kept for 30 days; the all-time counter stands at 0 responding of 3.
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 Licita and makes no claim about it beyond what these checks measured.