Fca Register MCP server

@pipeworx/fca-register

UK Financial Conduct Authority Financial Services Register (register.fca.org.uk) — the public record of every FCA-regulated firm and individual: firm search, firm details by FRN, a firm's appointed representatives, and an individual's own public register record by IRN.

Part of Pipeworx — an MCP gateway connecting AI agents to 1679+ live data sources.

Tools

type is one of firm (default), individual, fund.

• fcafirmsearch(q, type?) — search the register by name;

address by Firm Reference Number.

• fcafirmdetails(frn) — a firm's status, business type, and

representatives by FRN. An empty list for a firm with none is a real answer, not a failure.

• fcafirmrepresentatives(frn) — a firm's appointed

register record (name, current approved-function status) by Individual Reference Number. Looks up exactly one IRN; does not enumerate or list individuals.

• fcaindividuallookup(irn) — a single individual's own public

Auth

No key needed from the caller: Pipeworx fronts one. The FCA ties each API key to a signup email and needs both on every request; a caller who wants to use their own can pass _apiKey as ":" (register free at ).

Data sources

X-Auth-Email / X-Auth-Key headers, ~50 requests/10s per the FCA's own developer documentation.

• — base URL. Auth via

• GET /Search?q=&type=firm|individual|fund
• GET /Firm/{FRN}
• GET /Firm/{FRN}/AR (appointed representatives)
• GET /Individuals/{IRN}
• — developer portal / signup.

UNVERIFIED beyond the no-key and garbage-key cases — no key exists on the fleet. Endpoint paths above are corroborated across multiple independent third-party client libraries (the fsrapiclient / financialservices register_api Python packages, CyborgFinance/FCARegisterLaravel) that all describe the same shapes, but this pack has never completed a successful authenticated call. Live-probed 2026-09-23 with a syntactically-valid but non-functional key: every endpoint answered with a real, on-brand JSON body ({"Success":"false", "Value not found"}, HTTP 404) rather than a DNS failure or a generic edge error — strong evidence the base URL and path shapes above are correct, just not proof of the populated/successful response shape. raw is included on every tool's response so a caller with a real key gets the untouched upstream payload even if a field name assumption here turns out stale.

Personal-data scope is deliberate: fcaindividuallookup exposes only the register's own single-record public fields for one IRN a caller already has. This pack ships no bulk/enumeration tool over individuals (no "list every approved person", no alphabet crawl) — do not add one without re-checking that boundary.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "fca-register": {
      "url": "https://gateway.pipeworx.io/fca-register/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/fca-register/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — askpipeworx, discovertools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

Shortened. The full README is on GitHub.