FinTech Studios' MCP connector, announced September 24, 2026 and listed in the Claude and ChatGPT connector directories, brings its news and regulatory intelligence into AI assistants. It is a hosted Streamable HTTP server with read-only tools for collections, insight channels, account usage and cost estimates; a local stdio option with an API key is also documented.
Provides data. A read-only feed from one provider; it answers questions, doesn't act, and doesn't expect other servers alongside it. More on Source servers →All seven roles →
Endpoint verbatim from the vendor's MCP page. The hosted connector uses OAuth 2.1 sign-in with FTS Studio; the local stdio option uses an API key instead.
Vendor-verified only. Tool behavior is documented by the vendor and has not been independently tested.
Credit-based usage. A free tier exists, with paid usage beyond it; the server exposes a cost-estimate tool, so check it before large pulls.
News aggregation can surface unverified or duplicated stories. Check the underlying source before a headline reaches a client.
Read-only per the vendor. Still start with read-only scopes.
Rate this server
How to connect FinTech Studios MCP Connector
Step 1
Remote server: paste a URL
FinTech Studios MCP Connector publishes a remote (Streamable HTTP) endpoint, so nothing is installed locally. Add it as a custom connector in Claude, ChatGPT or your IDE and paste the endpoint below.
Your client opens a browser sign-in with the vendor. Approve only the scopes you need, and use a read-only account first when the platform offers one.
Step 3
Verify, then widen access
Restart your client, confirm the server's tools appear, and run one read-only question first. Keep client-side approval prompts on for any tool that can write, trade or send. Confirm with your firm's compliance policy before connecting systems holding client data.
Trade & RebalanceCustody & ClearingMarket & Financial Data
Read-only: for the proposed sells in <account>, review tax lots at the custodian and flag short-term gains, large realised gains, and any purchase in the last 30 days that could create a wash sale. Then use market-data tools to value each lot at the latest available price and to check for splits, mergers or other corporate actions that would change basis or share count. Output Symbol / Lot / Acquired / Basis / Market value / Gain-loss / Flag / Source. Do not place or modify trades. Tell me where the data may be delayed or incomplete.
Guardrail · Read-only. Confirm lot data with the custodian before acting on it.
Scenario comparison brief
A side-by-side read on two planning scenarios.
Financial PlanningFinancial PlanningMarket & Financial Data
Read-only: compare the existing plan for <client name> against the scenario <describe change, e.g. retire two years earlier>. Pull the plan's stored return, inflation and yield assumptions, then use market-data tools to show current comparable figures for the same inputs. Present outcome differences, an assumptions table of Plan assumption / Current market reading / Source / Date, and which assumption the result is most sensitive to. State every assumption explicitly. Do not save, overwrite or publish any scenario in the planning system.
Guardrail · Read-only. Plan illustrations are not advice, review before sharing.
Market context talking points
Three to five neutral talking points on recent market moves.
Client Review Meeting PrepWealth PlatformsMarket & Financial Data
Read-only: pull <client name>'s current holdings and sector or asset-class weights from the wealth platform, then use market-data tools to explain what moved those specific exposures over the last quarter. Return three to five neutral talking points, each tied to a holding or weight and to the market data behind it. No forecasts, no recommendations to buy or sell, no performance promises. Cite the source and date for both the holdings figure and the market figure so I can verify before I use it with a client.
Guardrail · Educational framing only. Avoid forward-looking or promissory language.
