# Confirme, by Synapse [Health: Active]

**Category:** 💬 Communication  
**Repository:** https://github.com/francistremblay30-netizen/confirme  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/confirme-by-synapse

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

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "confirme-by-synapse": {
    "url": "https://www.synapseconnexion.com/ia/mcp"
  }
}
```

## Documentation

## What Confirme, by Synapse MCP server does

Confirme, by Synapse MCP server gives AI agents an external way to check selected facts and record the observation in a signed receipt. It can inspect a public web page, assess a domain, validate an email address using syntax, MX, disposable-address, and role checks, record a scheduled-run heartbeat, or query whether a task has reported activity recently.

The service is operated by Synapse and is separate from the AI platform making the request. Each response includes the request and result, timing, price and quota information, plus a receipt. The receipt contains an identifier, timestamp, service name, SHA-256 hashes, a key identifier, and an Ed25519 detached signature. Receipts can be checked through Synapse's online verifier or verified offline with the repository's example.

## How it works

Connect an MCP client to `https://www.synapseconnexion.com/ia/mcp` using Streamable HTTP. The endpoint is stateless. The same operations are also exposed as HTTP requests, and an OpenAPI document is available from the service. A typical agent flow is to call `confirme_battement` after a successful scheduled run, then call `confirme_tache` later to look for evidence of recent activity. Silence can then be treated as an operational signal, while the receipts provide evidence of what the service observed.

The signed record proves the observation made by Synapse and when it was made. It does not prove what the agent did after receiving the result, and a heartbeat attests that the agent declared a heartbeat rather than independently proving that the underlying work completed.

## Setup and configuration

Add the endpoint to an MCP client with its HTTP transport. Claude Code and Gemini CLI have command-line examples in the documentation; Cursor, Windsurf, and VS Code can use an `mcp.json` entry with the endpoint URL. ChatGPT and Claude.ai can also connect through their custom MCP connector settings where available.

During launch, no authentication is required. The documented launch allowance is 1,000 calls per IP address per UTC day through 2026-10-07. After that period, the service describes a free key with an initial allowance and daily refill. A key can be created through `POST /ia/cle/nouvelle` and supplied as a bearer token or query parameter. Calls cost one cent each when paid usage applies, while receipt verification remains free.

## Tools and capabilities

- `confirme_page`: checks whether a public URL can be reached. Private networks and password-protected pages are refused.
- `confirme_domaine`: evaluates an unfamiliar domain for legitimacy-related checks.
- `confirme_courriel`: checks email syntax, MX records, disposable status, and role-account indicators. It never sends email and cannot prove that a particular mailbox exists.
- `confirme_battement`: records a heartbeat declaration with a key and note.
- `confirme_tache`: looks up task activity using a key and a time window such as the previous 86,400 seconds.

## Limitations and notes

Confirme, by Synapse MCP server only observes the inputs supported by these tools; it does not verify arbitrary agent actions. Page checks cover public hosts only. Email validation is not mailbox verification. Heartbeat receipts record the declaration time, not independent completion of the reported task. Usage can return a payment-related response when the available allowance is exhausted.

The repository's documentation and examples use the MIT license. The hosted service itself is operated by Synapse, so service availability and pricing are governed by the service documentation rather than the repository license.

_Full upstream README: https://allmcps.com/mcp/confirme-by-synapse/readme_