Le Confidant
REMOTE · LECONFIDANT.AI
Statistics from your own WhatsApp chat analysis as numbers only, plus free WhatsApp text tools.
Available components
Last scanned (20 minutes ago)
Scores higher than 43% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Communication
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (disconnect_conversation). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability39
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1216 tokens (~152/item across 8 items; 7 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage81
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 33% of tool parameters carry a description.Partial
- Structured output schemas are declared (86% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 1 Nov 26 59
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://leconfidant.ai/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=leconfidant.ai | CN=YE2,O=Let's Encrypt,C=US | 25 Sept 2026 | 24 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5fd1add90ce504a6e11a82f3f384fa2e47b |
| SANs: leconfidant.ai | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of leconfidant.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| leconfidant.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15724800; includeSubdomains |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://leconfidant.ai/api/mcp | Verified | 200 | |
| http (plaintext) | http://leconfidant.ai/api/mcp | HTTPS enforced | 301 | https://leconfidant.ai/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
demo_whatsapp_wrapped Show a fictional WhatsApp Wrapped recap ~74
Show a synthetic WhatsApp recap without an account, upload or private conversation access. Use only for a demo or example, never to answer questions about the user's real conversation. All numbers are fictional and fixed; no relationship diagnosis. Returns a text and structured recap, without image export.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| activeDays | integer | yes | – |
| learnMore | object | yes | – |
| limitations | array | yes | – |
| locale | string | – | – |
| participants | array | yes | – |
| scope | string | yes | – |
| source | object | yes | – |
| title | string | yes | – |
| topEmojis | array | yes | – |
| totalMessages | integer | yes | – |
No examples provided.
disconnect_conversation Disconnect your selected conversation ~105
Use only when the user explicitly asks to disconnect or revoke this connection. Permanently revoke its current OAuth grant immediately; the revoked credential cannot be restored. Fresh explicit consent creates a new grant while the original session is eligible. Stops future reads without deleting the source session or results already in this conversation. Other connections can be revoked on the website. This tool changes access and is destructive access revocation; it does not retrieve statistics or answer period comparisons.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | – |
No output schema declared.
No examples provided.
format_whatsapp_text Format text for WhatsApp ~281
Convert the user's Markdown source to text ready to paste into WhatsApp. Before calling, copy the supplied source unchanged into text: do not Markdown-escape it or pre-convert it. Example: source **Meeting tomorrow** must be passed as **Meeting tomorrow**; the tool returns *Meeting tomorrow*. Preserve backslashes the user actually supplied, but never insert extra ones. After calling, display structuredContent.formattedText verbatim in a plain-text fenced code block, without escaping or reformatting it. Supports # headings, bold, italics, strikethrough, lists and links. Preserves URL destinations, literal text and fenced/inline code. Unsupported blocks remain literal; does not render HTML, summarize or translate. Inputs are processed by this server to return the result; this tool does not store or log phone numbers or text. It does not access an account or send messages.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | – |
| text | string | yes | The user's original Markdown source, up to 12,000 UTF-16 code units. Copy it unchanged: do not render it, pre-convert formatting, or add backslashes before Markdown punctuation. For **Meeting tomorro… |
| Name | Type | Req | Description |
|---|---|---|---|
| formattedText | string | yes | Finished WhatsApp text, ready to copy. Display this value verbatim in a plain-text fenced code block; do not add backslash escapes, change emphasis markers, or format it again. Choose a fence that do… |
| locale | string | – | – |
| messageSent | boolean | yes | – |
No examples provided.
generate_whatsapp_link Create a WhatsApp click-to-chat link ~115
Create a wa.me URL with an optional prefilled message for copying or sharing. Requires a valid phone number; does not verify WhatsApp registration. Inputs are processed by this server to return the result; this tool does not store or log phone numbers or text. It does not access an account or send messages.
| Name | Type | Req | Description |
|---|---|---|---|
| defaultCountry | string | – | – |
| locale | string | – | – |
| message | string | – | – |
| phone | string | yes | International phone number beginning with +, or a national number with defaultCountry. |
| Name | Type | Req | Description |
|---|---|---|---|
| e164 | string | yes | – |
| locale | string | – | – |
| messageSent | boolean | yes | – |
| url | string | yes | – |
No examples provided.
get_conversation_snapshot Read whole-session statistics ~163
Use only to retrieve or explain WHOLE-SESSION numerical statistics from the user's explicitly authorized WhatsApp export analysis. DO NOT call for date-window, month-to-month, trend or period-comparison requests, even to check available data. For example, 'Compare September and November in my own connected WhatsApp analysis' needs NO tool call: explain that period comparison is unavailable. This tool returns only stored whole-session totals and cannot answer that request. For supported requests, returns neutral A/B labels, counts/shares, starts, reply timing/sample sizes, mean message length, definitions, limitations and expiry from the OAuth-selected session. No raw messages, names, excerpts, paid insights or new analysis. Set locale to the user's supported language.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| definitions | object | yes | – |
| expiresAt | string | yes | – |
| kind | string | yes | – |
| limitations | array | yes | – |
| locale | string | – | – |
| snapshot | object | yes | – |
| source | object | yes | – |
No examples provided.
normalize_whatsapp_numbers Normalize phone numbers for WhatsApp ~122
Validate up to 100 phone numbers and return E.164 numbers and wa.me links with per-row status and duplicate positions. National numbers require defaultCountry. Never guess a country from language. Does not check WhatsApp registration or contact people. Inputs are processed by this server to return the result; this tool does not store or log phone numbers or text. It does not access an account or send messages.
| Name | Type | Req | Description |
|---|---|---|---|
| defaultCountry | string | – | Country for national numbers; never inferred from locale. |
| locale | string | – | – |
| numbers | array | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| invalidCount | integer | yes | – |
| locale | string | – | – |
| registrationChecked | boolean | yes | – |
| rows | array | yes | – |
| uniqueValidCount | integer | yes | – |
| validCount | integer | yes | – |
No examples provided.
style_whatsapp_text Restyle text with decorative letters ~177
Rewrite the user's text in one decorative Unicode style to paste into WhatsApp. Styles: bold, italic, monospace, bubble, gothic, double (double-struck), strikethrough, upside-down. Call it once the user has picked a style from this list. These are lookalike characters, not real fonts: accented letters and digits usually stay plain, and screen readers can read the result badly. After calling, display structuredContent.styledText verbatim in a plain-text fenced code block. Inputs are processed by this server to return the result; this tool does not store or log phone numbers or text. It does not access an account or send messages.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | – |
| style | string | yes | The style the user chose. |
| text | string | yes | The user's text, copied unchanged. |
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | – |
| messageSent | boolean | yes | – |
| style | string | yes | – |
| styledText | string | yes | Finished text, ready to copy. Display this value verbatim in a plain-text fenced code block; do not normalize, translate or format it again. |
No examples provided.
How do I install the Le Confidant MCP server?
Le Confidant is a hosted endpoint at https://leconfidant.ai/api/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.
remote · leconfidant.ai
claude mcp add --transport http ai-leconfidant-le-confidant 'https://leconfidant.ai/api/mcp'
What is the Le Confidant MCP server?
Le Confidant is an MCP server listed in the public MCP registry as ai.leconfidant/le-confidant. Statistics from your own WhatsApp chat analysis as numbers only, plus free WhatsApp text tools. This page covers its hosted endpoint (https://leconfidant.ai/api/mcp).
Is the Le Confidant MCP server safe to use?
Le Confidant scores 61 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 Le Confidant MCP server expose?
Le Confidant exposes 7 tools: generate_whatsapp_link, format_whatsapp_text, normalize_whatsapp_numbers, demo_whatsapp_wrapped, style_whatsapp_text, and 2 more. Their descriptions and schemas cost roughly 1,037 tokens of context every time the server is loaded.
Does the Le Confidant MCP server require authentication?
No. We connected to Le Confidant without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Le Confidant MCP server still maintained?
Le Confidant 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.