Remote MCP · Endpoint

Propecto MCP server

No. Propecto answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.propecto.eu/mcp

The last check completed an MCP handshake.

Registry name
eu.propecto/propecto
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
442 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Sociétés européennes, dirigeants, comptes, marchés publics, aides et marques (lecture seule).
Listing
From the official MCP registry (active).
Recent checks of Propecto
CheckedResultHandshake
1 hour agoHandshake completed442 ms
2 days agoHandshake completed527 ms
4 days agoHandshake completed518 ms
6 days agoHandshake completed401 ms
7 days agoHandshake completed454 ms
9 days agoHandshake completed506 ms
10 days agoHandshake completed574 ms
11 days agoHandshake completed959 ms
14 days agoHandshake completed491 ms
15 days agoHandshake completed352 ms
17 days agoHandshake completed380 ms
18 days agoHandshake completed489 ms
19 days agoHandshake completed371 ms
20 days agoHandshake completed474 ms
21 days agoHandshake completed478 ms
21 days agoHandshake completed643 ms

The last 16 checks. Full history is kept for 30 days; the all-time counter stands at 16 responding of 16.

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 Propecto and makes no claim about it beyond what these checks measured.