Synapze — Financial Intermediary MCP
Wire your agent to licensed French financial intermediaries for insurance, credit, and wealth workflows through Synapze’s tenant-scoped MCP API.
Overview
eu.synapze/financial-intermediary-mcp is a MCP server for the Build phase that connects AI agents to licensed French financial intermediaries for insurance, credit, and wealth via tenant-scoped HTTPS tools.
What is this MCP server?
- Connects agents to licensed French intermediaries: insurance, credit, wealth
- Streamable-http remotes: mcp.synapze.eu/v1/{tenant_id} and /v1/registry
- Per-tenant Bearer API key and broker cabinet tenant_id (e.g. protecsia, ism)
- Version 1.0.1; docs site mcp.synapze.eu; repo ycdvll/synapze-mcp
- Registry endpoint for discovering intermediary capabilities without hardcoding tenants
- Server version 1.0.1
- 2 streamable-http remotes: tenant path v1/{tenant_id} and v1/registry
- Required variables: tenant_id; required secret: Authorization Bearer API key
What problem does it solve?
Building a France-facing finance agent stalls because every intermediary exposes a different API and licensing context.
Who is it for?
Indie builders and small fintech teams targeting French broker cabinets who already have or are onboarding Synapze tenant access.
Skip if: Builders outside French intermediary workflows, hobby apps without regulatory clearance, or teams wanting a single global card processor only.
What do I get? / Deliverables
Your agent calls Synapze MCP tools against a chosen tenant so insurance, credit, and wealth flows share one integration layer.
- Agent tools backed by Synapze intermediary endpoints for a specific tenant
- Discovery of available intermediary resources via /v1/registry where supported
- Integration config you can version-control alongside app environment docs
Recommended MCP Servers
Journey fit
Broker and intermediary APIs are integrated during Build when the product needs live regulated channels—not during abstract idea brainstorming. Integrations is the shelf for third-party financial pipes, tenant URLs, and API keys that become part of your backend or agent tools.
How it compares
Licensed intermediary MCP integration, not a Stripe skill or a generic spreadsheet finance plugin.
Common Questions / FAQ
Who is eu.synapze/financial-intermediary-mcp for?
Developers shipping agent or SaaS experiences that must talk to licensed French insurance, credit, or wealth intermediaries through Synapze.
When should I use eu.synapze/financial-intermediary-mcp?
Use it during Build integrations once you have a tenant_id and API key and need agent-callable tools against live intermediary data.
How do I add eu.synapze/financial-intermediary-mcp to my agent?
Add streamable-http MCP remotes for https://mcp.synapze.eu/v1/{tenant_id} with Authorization Bearer your tenant key, optionally add /v1/registry, then reload your MCP client.