Finance · Remote MCP server
Synapze - Financial Intermediary MCP
Connect AI agents to licensed financial intermediaries in France: insurance, credit, wealth.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
eu.synapze/financial-intermediary-mcp- Version
- 1.0.1
- Status
- Active
- Category
- finance
- Transport
- Streamable HTTP
- Published
- 2026-03-26
- Updated
- 2026-03-26
- Publisher
- eu.synapze
- Namespace
- Namespace verified by the MCP Registry via the domain synapze.eu · how
- Website
- mcp.synapze.eu
- Repository
- github.com/ycdvll/synapze-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.synapze.eu/v1/{tenant_id} | Authorization (required, secret) |
| Streamable HTTP | https://mcp.synapze.eu/v1/registry | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Endpoint
https://mcp.synapze.eu/v1/{tenant_id}(HTTP)- Checked
- Not requested: URL template placeholder
- Checked on
- 2026-10-05
- Endpoint
https://mcp.synapze.eu/v1/registry(HTTP)- Reachable
- Yes (HTTP 200)
- Handshake
- eu.synapze/financial-intermediary-mcp 1.0.0 · protocol 2025-06-18
- Tools discovered
- 4:
find_broker,get_broker_info,get_products,get_quote - Checked on
- 2026-10-05
How to connect Synapze - Financial Intermediary MCP
Synapze - Financial Intermediary MCP is a remote MCP server: there is nothing to install. Its endpoints are https://mcp.synapze.eu/v1/{tenant_id} and https://mcp.synapze.eu/v1/registry, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The URL contains placeholders to fill in before connecting: {tenant_id}.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More finance servers
| Server | Runs |
|---|---|
| Switchboard FinanceAustralian business loans: ATO debt, caveat, equipment, property. Check fit, then a broker calls. | Remote · HTTPLive check: ✓ handshake |
| SwopSell to people and AI agents: create products, a storefront, and USDC payment links from chat. | Remote · HTTPLive check: ✓ handshake |
| SWT3 AI WitnessCryptographic AI governance and audit. 72 tools, 77 frameworks. EU AI Act, NIST, CMMC, MCP Top 10. | Local · stdio |
| sygnldata - market intelligence for trading agentsMarket regime, execution-cost, bar-QC and backtest-audit tools for agents. Pay per call via x402. | Remote · HTTPLive check: ✓ handshake |
| SynciRead-only access to your bank, investment, and crypto accounts: balances, transactions, holdings. | Remote · HTTPLive check: sign-in required |
| SyncroMCP server for Syncro MSP - customers, tickets, assets, invoices, and more. | Local · stdio |
| SyncroMCP server for Syncro MSP - customers, tickets, assets, invoices, and more. | Local · stdio |
| SYNTHORA x402 Intelligence MeshCalibrated intelligence via x402 (USDC Base). ERC-8004 #84581: 272 payments, 49 wallets. | Remote · HTTPLive check: ✓ handshake |