Synapze — Financial Intermediary MCP
REMOTE · MCP.SYNAPZE.EU · 2 COMPONENTS · SCANNED AUG 3
Connect AI agents to licensed financial intermediaries in France: insurance, credit, wealth.
Available components
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 →
Endpoint Security77
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability56
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1064 tokens (~266/item across 4 items; 4 tools + 0 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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.synapze.eu
claude mcp add --transport http eu-synapze-financial-intermediary-mcp https://mcp.synapze.eu/v1/registry
[mcp_servers.eu-synapze-financial-intermediary-mcp] url = "https://mcp.synapze.eu/v1/registry"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"eu-synapze-financial-intermediary-mcp": {
"type": "remote",
"url": "https://mcp.synapze.eu/v1/registry",
"enabled": true
}
}
} openclaw mcp add eu-synapze-financial-intermediary-mcp --url https://mcp.synapze.eu/v1/registry --transport streamable-http
mcp_servers:
eu-synapze-financial-intermediary-mcp:
url: "https://mcp.synapze.eu/v1/registry" {
"mcpServers": {
"eu-synapze-financial-intermediary-mcp": {
"type": "http",
"url": "https://mcp.synapze.eu/v1/registry"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +4
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Jul 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.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 63
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 3 Aug 2026 · Probed https://mcp.synapze.eu/v1/registry
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.synapze.eu | CN=YR2,O=Let's Encrypt,C=US | 24 Jul 2026 | 22 Oct 2026 | RSA 4096 | SHA256-RSA | 6b89d0b4b2c14b07542fdd6f4f123ed009f |
| SANs: mcp.synapze.eu | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
DNSSEC secure
Validation of mcp.synapze.eu. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| eu. | present | 35926 | 8 | Verified |
| synapze.eu. | present | 1521 | 13 | Verified |
| mcp.synapze.eu. | Verified address RRset verified with the apex keys |
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 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.synapze.eu/v1/registry | Verified | 200 | |
| http (plaintext) | http://mcp.synapze.eu/v1/registry | HTTPS enforced | 301 | https://mcp.synapze.eu/v1/registry |
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.
find_broker ~206
Trouver un courtier en assurance / Find a licensed insurance broker in France. Recherche par produit (auto, moto, MRH/habitation, RC Pro, protection juridique, épargne, assurance vie, PER), ville et langue. Search by product type, city, and language. Returns broker name, specialties, DDA compliance status, and connection endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | — | City or zone in France (e.g. 'paris', 'lyon', 'marseille') |
| language | string | — | Preferred language: fr, en |
| product | string | yes | Insurance product type: auto, moto, mrh, rc_pro, protection_juridique, epargne, assurance_vie, per |
| sub_specialty | string | — | Sub-specialty niche within the product (e.g. 'architectes', 'sci_is', 'dirigeants') |
| ticket | number | — | Project amount in EUR (for routing large-ticket cases) |
No output schema declared.
No examples provided.
get_broker_info ~116
Informations et branding du courtier / Broker branding and identity. Returns: company name, logo URL, brand color (#hex), address, postal code, phone, ORIAS number, website, specialties, and DDA compliance status. ALWAYS call this before generating any document (PDF, PPTX, comparison, advisory note) to brand it with the broker's logo, color, name, address, and ORIAS number.
| Name | Type | Req | Description |
|---|---|---|---|
| broker_code | string | — | Broker code returned by find_broker. Optional in broker-authenticated mode. |
No output schema declared.
No examples provided.
get_products ~137
Catalogue produits assurance / List insurance products with eligibility criteria, coverage details, and indicative pricing. A category is required. Categories: auto, moto, mrh (habitation/home), rc_pro (responsabilité civile/professional liability), protection_juridique (legal), epargne (savings), assurance_vie (life savings), per (retirement savings).
| Name | Type | Req | Description |
|---|---|---|---|
| broker_code | string | — | Broker code returned by find_broker. Optional in broker-authenticated mode. |
| category | string | — | Product category filter: auto, moto, mrh, rc_pro, protection_juridique, epargne, assurance_vie, per |
No output schema declared.
No examples provided.
get_quote ~605
Tarification assurance en temps réel / Generate real insurance quotes from partner APIs. Devis auto, moto, habitation (MRH), RC Pro, protection juridique, épargne, assurance vie, PER. Returns monthly prices per product and level. No PII stored or returned. IMPORTANT — birth_date + postal_code are REQUIRED for all products. Use product_data for product-specific information. Call get_products first to see quoteRequirements.guidance for each product — it tells you exactly what to ask the client. product_data examples by product_type: • auto / moto: {marque, modele, annee, immatriculation, energie, puissance_fiscale, km_annuel, usage, stationnement, date_permis, bonus_malus, sinistres_3ans, formule: tiers/tiers_etendu/tous_risques} • mrh: {type_logement: appartement/maison, statut_occupant: proprietaire/locataire/pno, surface, nb_pieces, etage, annee_construction, alarme, valeur_mobilier} • rc_pro: {activite, code_naf, nb_salaries, ca_annuel} • protection_juridique (pj): {domaine, nb_salaries} • per: {revenus_annuels, tmi, versement_initial, versement_mensuel, profil_risque: prudent/equilibre/dynamique} • assurance_vie: {versement_initial, versement_mensuel, profil_risque, horizon_placement_annees}
| Name | Type | Req | Description |
|---|---|---|---|
| birth_date | string | yes | Client birth date in YYYY-MM-DD format (e.g. '1988-05-15') |
| broker_code | string | — | Broker code returned by find_broker. Optional in broker-authenticated mode. |
| budget | number | — | Client's monthly budget in euros (e.g. 80). Results sorted by proximity to budget. |
| children | array | — | Children details for family coverage |
| gender | string | — | Gender: M or F |
| has_spouse | boolean | — | Whether the client has a spouse/partner to cover |
| number_of_children | number | — | Number of children to cover |
| postal_code | string | — | French postal code (e.g. '75008', '92150'). Required for all products. |
| product_data | object | — | Product-specific data object. Fields depend on product_type — see description above for examples per product. Call get_products first to see quoteRequirements.guidance for the exact fields to collect. |
| product_type | string | yes | Product type: auto, moto, mrh, rc_pro, protection_juridique (pj), epargne, assurance_vie, per |
| show_all | boolean | — | Return ALL quotes instead of top 5. Use only when client asks for more options. |
| spouse_birth_date | string | — | Spouse birth date in YYYY-MM-DD format |
No output schema declared.
No examples provided.