com.futurmatch/assistant
Futurmatch Assistant
Is the Futurmatch Assistant MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-10.
Interrogez votre marché depuis votre IA. Futurmatch détecte les entreprises où un besoin se dessine.
needs auth probed 2026-11-14 · unchanged since 2026-11-10 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"error":"invalid_token","error_description":"Jeton absent, expiré ou révoqué. Accès Futurmatch : https://futu- Endpoint
- https://api.futurmatch.com/mcp (streamable-http)
- Host
- api.futurmatch.com
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://api.futurmatch.com/mcp registers itself and opens the consent page; the publisher has nothing to set up for you. The publisher's guide to getting access.
Authorization server api.futurmatch.com, PKCE S256, grants authorization_code, refresh_token.
Scopes futurmatch.lecture futurmatch.ecriture.
Read from the server's public OAuth metadata, without a token. Method. - Website
- https://futurmatch.com/ia#decouverte
- Registry
- deprecated, updated 2026-11-09 · registry entry
Compare this server with others.
More servers
Other registry entries on api.futurmatch.com.
- Futurmatch Assistant com.futurmatch/futurmatch · needs auth
Servers that mention entreprises or interrogez.
- ArchiCollab archi.collab/archicollab · needs auth
- Basile cc.basile/basile · needs auth
- Origami Entreprises fr.origami-entreprises/origami · needs auth
- Entreprises Fr io.github.pipeworx-io/entreprises-fr · alive
- kbiz.fr fr.kbiz/mcp · needs auth
- LegalOne Entreprises fr.legalone/entreprises · alive
- Laopan fr.laopan/laopan · needs auth
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.