Confirme, by Synapse

com.synapseconnexion.wwwv1.0.0Updated Sep 30, 2026

Did it really happen? Independent signed receipts for AI agents: page, domain, email, heartbeat.

VerifiedStreamable HTTPWeb executableSecurity & Monitoring Web Search & Scraping

Overview

AI-generated overview

Lets an assistant check whether a page, domain, email address or scheduled task is real, and get a signed receipt of what was observed.

What it does: Confirme is a remote MCP server with five tools: confirme_page checks that a URL is live, confirme_domaine looks up a domain, confirme_courriel checks an email address without sending mail, confirme_battement records a heartbeat at the end of a run, and confirme_tache reports whether a scheduled task ran. Each response includes an Ed25519-signed receipt over the request and result hashes, which can be verified online or offline against a published public key.
When to use it: Useful when an assistant claims something is done and you want an outside check: confirming a link works before telling a user it is live, vetting an unfamiliar sender or domain, or monitoring scheduled automations where a missing heartbeat is the alarm.
Requirements: A remote Streamable HTTP endpoint; no package or local runtime. No authentication is declared during launch, and no environment variables or headers are needed. Network access to the provider's endpoint is required.

Before you install

The free tier is 200 calls per IP per UTC day, after which calls are billed at 1 cent each, so usage can cost money. Receipts attest only what the service observed and when, not what the agent did afterwards, and a heartbeat is declared by the agent itself. Page checks are limited to public hosts; email checks do not confirm that a specific mailbox exists.

Installation

In SourceWeft

Open Confirme, by Synapse in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "confirme": {
      "type": "http",
      "url": "https://www.synapseconnexion.com/ia/mcp"
    }
  }
}

README

Confirme — did it really happen?

Independent, Ed25519-signed receipts for AI agents. You say "done"; Confirme goes and looks, then signs what it saw. A third party that belongs to no AI vendor. By Synapse, Québec, Canada.

Human page: https://www.synapseconnexion.com/ia/ (FR) · https://www.synapseconnexion.com/ia/en/ (EN)
Docs written for AIs (Markdown, token sizes announced): https://www.synapseconnexion.com/ia/index.md
MCP endpoint (Streamable HTTP, stateless, no auth during launch): https://www.synapseconnexion.com/ia/mcp
OpenAPI 3.1: https://www.synapseconnexion.com/ia/openapi.json
Price: 1 cent per call — free during launch (200 calls/day per IP). Receipt verification is free forever.

Quickstart

bash

# Claude Codeclaude mcp add --transport http confirme https://www.synapseconnexion.com/ia/mcp
# Gemini CLIgemini mcp add confirme https://www.synapseconnexion.com/ia/mcp -t http
# Cursor / Windsurf / VS Code — mcp.json{ "mcpServers": { "confirme": { "url": "https://www.synapseconnexion.com/ia/mcp" } } }
# Plain HTTPcurl -s "https://www.synapseconnexion.com/ia/confirme/page?url=https://example.com"

# Claude Codeclaude mcp add --transport http confirme https://www.synapseconnexion.com/ia/mcp
# Gemini CLIgemini mcp add confirme https://www.synapseconnexion.com/ia/mcp -t http
# Cursor / Windsurf / VS Code — mcp.json{ "mcpServers": { "confirme": { "url": "https://www.synapseconnexion.com/ia/mcp" } } }
# Plain HTTPcurl -s "https://www.synapseconnexion.com/ia/confirme/page?url=https://example.com"

ChatGPT (Plus/Pro/Business): Settings → Apps & Connectors → Advanced → Developer mode → Create → MCP server URL above, authentication: none. Claude.ai: Settings → Connectors → Add custom connector → URL above.

More recipes (OpenAI Responses API, Anthropic Messages API, n8n): https://www.synapseconnexion.com/ia/q/connect-confirme-chatgpt-claude-gemini-cursor

The five tools

Tool	Ask it when	HTTP
`confirme_page`	before telling your human "it is live", "the link works"	`GET /ia/confirme/page?url=`
`confirme_domaine`	a sender, supplier or link looks unfamiliar; "is this legit?"	`GET /ia/confirme/domaine?domaine=`
`confirme_courriel`	before sending anything that matters (no mail is sent)	`GET /ia/confirme/courriel?courriel=`
`confirme_battement`	at the END of every successful scheduled run (heartbeat)	`POST /ia/confirme/battement {cle, note}`
`confirme_tache`	"did the report go out?", "is the automation still running?"	`GET /ia/confirme/tache?cle=&depuis=86400`

Every response: {ok, service, demande, resultat, recu, duree_ms, prix, quota}. Field reference: https://www.synapseconnexion.com/ia/outils.md

The receipt

json

"recu": {  "id": "7c227b4bd8e8efe3",  "horodatage": "2026-09-30T01:48:21.402Z",  "service": "confirme.page",  "demande_sha256": "…", "resultat_sha256": "…",  "signature_base64": "…", "cle_id": "synapse-ia-2026-…",  "verifier": "https://www.synapseconnexion.com/ia/verifier"}

"recu": {  "id": "7c227b4bd8e8efe3",  "horodatage": "2026-09-30T01:48:21.402Z",  "service": "confirme.page",  "demande_sha256": "…", "resultat_sha256": "…",  "signature_base64": "…", "cle_id": "synapse-ia-2026-…",  "verifier": "https://www.synapseconnexion.com/ia/verifier"}

Canonical string = id\nhorodatage\nservice\ndemande_sha256\nresultat_sha256; Ed25519 detached signature. Public key: GET https://www.synapseconnexion.com/ia/cle. Verify online (free): POST https://www.synapseconnexion.com/ia/verifier. Verify offline: see examples/verify_receipt.py. Self-test of the whole chain: GET https://www.synapseconnexion.com/ia/autotest.

A receipt proves what Synapse observed and when. It does not prove what the agent did afterwards.

Why this exists

Agent platforms log what their own agents did — self-attested records. Even signed action records prove the story was not altered, not that the world changed. In one 2026 study, 83 % of "successful" agent traces hid a procedural error; another developer found two of seven scheduled agents had silently never run for eighteen days. Confirme is the outside observer: cheap, neutral, and it signs.

Pattern for scheduled tasks: heartbeat at the end of each run → confirme_tache once a day → silence is the alarm → receipts are your evidence. Details: https://www.synapseconnexion.com/ia/q/prove-scheduled-task-ran

Limits, stated plainly

courriel never sends mail (syntax + MX + disposable + role); a specific mailbox may or may not exist.
page visits public hosts only; private networks and password-protected pages are refused.
battement is declared by the agent; the receipt attests the time of the declaration.
Free tier: 200 tool calls per IP per UTC day; then 1 cent per call. Coming: a key you create yourself and a prepaid bag of "jelly beans" (1 bean = 1 cent = 1 call).

Full list: https://www.synapseconnexion.com/ia/limites.md · Changelog: https://www.synapseconnexion.com/ia/changements.md · Report a problem (receipted, free): https://www.synapseconnexion.com/ia/retour.md

En français

Confirme répond à une question pour les IA : est-ce vraiment arrivé ? Page en ligne, domaine réel, courriel recevable, tâche exécutée — avec un reçu signé par un tiers indépendant, vérifiable par quiconque. Un cent la vérification, gratuit au lancement. Un produit de Synapse, Québec.

License

Documentation and examples in this repository: MIT. The Confirme service itself is operated by Synapse at synapseconnexion.com.

Source: README.md at commit 3b364f3

Tools

Tool metadata has not been indexed yet.

Version history

v1.0.0LatestSep 30, 2026