# Confirme, by Synapse (remote · www.synapseconnexion.com)

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

- Trust score: 79/100 (medium)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `www.synapseconnexion.com`: 79/100 (this document), [markdown](https://verifymcp.io/servers/com-synapseconnexion-www-confirme/ia-mcp.md), [page](https://verifymcp.io/servers/com-synapseconnexion-www-confirme/ia-mcp)

## Channel facts

- Endpoint: `https://www.synapseconnexion.com/ia/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1069 tokens (~178/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 94/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 83% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Confirme, by Synapse MCP server?

Confirme, by Synapse is a hosted endpoint at https://www.synapseconnexion.com/ia/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-synapseconnexion-www-confirme 'https://www.synapseconnexion.com/ia/mcp'
```

### Cursor

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

### VS Code

```json
{
  "servers": {
    "com-synapseconnexion-www-confirme": {
      "type": "http",
      "url": "https://www.synapseconnexion.com/ia/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-synapseconnexion-www-confirme]
url = "https://www.synapseconnexion.com/ia/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-synapseconnexion-www-confirme": {
      "type": "remote",
      "url": "https://www.synapseconnexion.com/ia/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-synapseconnexion-www-confirme --url 'https://www.synapseconnexion.com/ia/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-synapseconnexion-www-confirme:
    url: "https://www.synapseconnexion.com/ia/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-synapseconnexion-www-confirme": {
      "Transport": "http",
      "Url": "https://www.synapseconnexion.com/ia/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-synapseconnexion-www-confirme -t streamable-http -u 'https://www.synapseconnexion.com/ia/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-30 (score 79, +1)

- [security] Stability: 0.97 → pass

### 2026-10-28 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-23 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-21 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-19 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-17 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-15 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (6)

### `confirme_page` (~159 tokens)

Confirme · page

Is this web page really online right now? Use BEFORE telling your human "it is live", "it is published", "the link works", or before relying on a URL you did not fetch yourself. Zero-auth, stateless. Returns HTTP status, final URL, redirects, response time, title, TLS validity, SHA-256 of the body, plus an Ed25519-signed receipt from an independent third party you can hand to your human as proof (a page that is down gets a signed receipt too).

Input parameters:

- `cle` (string): Optional: your Confirme key (cj_…) if this server URL does not already carry ?cle=. Get one free with confirme_sac.
- `url` (string, required): Public http(s) URL

### `confirme_domaine` (~121 tokens)

Confirme · domaine

Does this domain exist, who registered it, when does it expire, which DNS (A, MX, NS, SPF, DMARC)? Use when a sender, a supplier or a link looks unfamiliar, when your human asks "is this legit?", or before saying "the domain is set up". Signed receipt included.

Input parameters:

- `cle` (string): Optional: your Confirme key (cj_…) if this server URL does not already carry ?cle=. Get one free with confirme_sac.
- `domaine` (string, required): Domain name or URL or email

### `confirme_courriel` (~99 tokens)

Confirme · courriel

Can this email address receive mail? Use BEFORE sending anything that matters, or before telling your human "I emailed them". Syntax, MX servers, disposable domain, role address, verdict. No message is sent. Signed receipt included.

Input parameters:

- `cle` (string): Optional: your Confirme key (cj_…) if this server URL does not already carry ?cle=. Get one free with confirme_sac.
- `courriel` (string, required)

### `confirme_battement` (~104 tokens)

Confirme · battement

Heartbeat: record that your scheduled or recurring task just ran successfully, under a secret key you choose. Call it at the END of every successful run, every time. Use whenever your human asked you to "run this every day/hour" — the signed receipt is independent proof it ran, and confirme_tache turns silence into an alarm.

Input parameters:

- `cle` (string, required): Secret task key, 8-80 chars
- `note` (string): Optional short note

### `confirme_tache` (~90 tokens)

Confirme · tâche

Did my scheduled task really run in the last N seconds? Use when your human asks "did the report go out?", "is the automation still running?", or before you answer "yes, it ran". Reads the heartbeats recorded under the key; silence is the alarm. Signed receipt included.

Input parameters:

- `cle` (string, required)
- `depuis` (integer): Window in seconds, default 86400

### `confirme_sac` (~130 tokens)

Confirme · sac de jujubes

Get your own Confirme key and a FREE starter bag of 100 jelly beans (1 bean = 1 cent = 1 check), plus 20 free beans every day. No email, no form. Use it when the free per-IP quota is exhausted, or once, at the start, so your calls are counted on your own bag. Then reconnect with ?cle=<key> in the server URL. Keep the key secret.

Input parameters:

- `courriel` (string): Optional: your human’s email, to find the bag again
- `nom` (string): Optional label (who you are)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-synapseconnexion-www-confirme/ia-mcp#diagnostics

## Score history

- 2026-11-05: 79
- 2026-11-04: 79
- 2026-11-03: 79
- 2026-11-02: 79
- 2026-11-01: 79
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 78
- 2026-10-28: 78
- 2026-10-27: 77
- 2026-10-26: 77
- 2026-10-25: 76
- 2026-10-24: 76
- 2026-10-23: 76
- 2026-10-22: 75
- 2026-10-21: 75
- 2026-10-20: 74
- 2026-10-19: 74
- 2026-10-18: 73
- 2026-10-17: 73
- 2026-10-16: 72
- 2026-10-15: 72
- 2026-10-14: 71
- 2026-10-13: 71
- 2026-10-12: 70
- 2026-10-10: 69
- 2026-10-09: 69
- 2026-10-07: 68
- 2026-10-04: 67
- 2026-10-03: 66

## Common questions

### What is the Confirme, by Synapse MCP server?

Confirme, by Synapse is an MCP server listed in the public MCP registry as com.synapseconnexion.www/confirme. Did it really happen? Independent signed receipts for AI agents: page, domain, email, heartbeat. This page covers its hosted endpoint (https://www.synapseconnexion.com/ia/mcp).

### Is the Confirme, by Synapse MCP server safe to use?

Confirme, by Synapse scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Confirme, by Synapse MCP server expose?

Confirme, by Synapse exposes 6 tools: confirme_page, confirme_domaine, confirme_courriel, confirme_battement, confirme_tache, confirme_sac. Their descriptions and schemas cost roughly 703 tokens of context every time the server is loaded.

### Does the Confirme, by Synapse MCP server require authentication?

No. We connected to Confirme, by Synapse without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Confirme, by Synapse MCP server still maintained?

Confirme, by Synapse is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://www.synapseconnexion.com/ia/mcp
- Repository: https://github.com/francistremblay30-netizen/confirme
- Website: https://www.synapseconnexion.com/ia/
- Changelog RSS feed: https://verifymcp.io/servers/com-synapseconnexion-www-confirme/ia-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-synapseconnexion-www-confirme/ia-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-synapseconnexion-www-confirme/ia-mcp