Remote MCP · Endpoint

Futurmatch Assistant MCP server

No — it is up, but it requires credentials. Futurmatch Assistant answered 10 hours ago with an authentication challenge rather than a session.

Auth requiredLast checked 10 hours ago

Server URL

https://api.futurmatch.com/mcp

The endpoint is answering and asked us for credentials. That is a working server, not an outage.

Registry name
com.futurmatch/assistant
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
Behind credentials
Uptime, last 30 days
3 checks from 3 checks
Described by its publisher as
Interrogez votre marché depuis votre IA. Futurmatch détecte les entreprises où un besoin se dessine.
Listing
From the official MCP registry (deprecated).
Recent checks of Futurmatch Assistant
CheckedResultHandshake
10 hours agoCredentials required—
4 days agoCredentials required—
7 days agoCredentials required—

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