Remote MCP · Endpoint

Beresol EU Policy Monitors MCP server

No. Beresol EU Policy Monitors answered an MCP handshake 7 hours ago.

Up · key neededLast checked 7 hours ago

Server URL

https://beresol.eu/api/mcp/

The handshake completes, but listing its tools needs credentials.

Registry name
eu.beresol/monitors
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
431 ms
Tools exposed
Behind credentials
Uptime, last 30 days
3 checks from 3 checks
Described by its publisher as
Eight EU policy monitors: defence, capital markets, tariffs, AI, quantum, startups, gold, GovTech.
Listing
From the official MCP registry (active).
Recent checks of Beresol EU Policy Monitors
CheckedResultHandshake
7 hours agoHandshake completed431 ms
4 days agoHandshake completed381 ms
7 days agoHandshake completed432 ms

The last 3 checks. Full history is kept for 30 days; the all-time counter stands at 3 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 Beresol EU Policy Monitors and makes no claim about it beyond what these checks measured.