Skip to main content

fca-register

Async Python client, command-line tool and MCP server for the FCA Financial Services Register API.

It stays under the FCA rate limit (50 requests per 10 seconds) with a sliding window that every process on the machine shares through a locked file in ~/.cache, so parallel runs don't get the account blocked. It runs on POSIX systems only, because the lock uses fcntl.

Install

pip install fca-register

Credentials

Register for an API key on the FCA developer portal, then set:

export FCA_API_EMAIL=you@example.com
export FCA_API_KEY=your-key

CLI

fca-register search "Harbour Underwriting" [--limit N]   # --limit 0 = all
fca-register firm 123456 [--with-ar]                     # appointed reps are opt-in

Both print JSON to stdout. python -m fca_register works too.

Library

import asyncio
from fca_register import Client

async def main():
    client = Client()  # or Client(email=..., api_key=...)
    matches = await client.search("Harbour Underwriting", limit=5)
    firm = await client.firm(matches[0]["fca_frn"])
    print(firm["permissions"])

asyncio.run(main())

Errors

The API usually answers HTTP 200 and puts its result code (FSR-API-…) in the body. "No record" codes come back as empty data. Error codes raise FcaAuthError (bad key or email, also a PermissionError), FcaBadRequestError (bad FRN or search string, also a ValueError) or FcaSystemError (FCA-side failure, also a RuntimeError). All three are subclasses of FcaApiError and carry .code and .message.

MCP server

A thin MCP server exposes two tools, search_firms(name, limit=20) and get_firm(frn, include_appointed_reps=False), over stdio. It needs Python 3.10+:

pip install "fca-register[mcp]"

Add it to Claude Code:

claude mcp add fca-register -e FCA_API_EMAIL=you@example.com -e FCA_API_KEY=your-key -- fca-register-mcp

Or add it to any client that reads an mcpServers config:

{
  "mcpServers": {
    "fca-register": {
      "command": "fca-register-mcp",
      "env": { "FCA_API_EMAIL": "you@example.com", "FCA_API_KEY": "your-key" }
    }
  }
}

Settings

Variable Default Meaning
FCA_MAX_REQUESTS 45 Requests allowed per window
FCA_WINDOW_SECONDS 10 Window length in seconds

Metadata

Release files for fca-register 0.1.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for fca-register 0.1.2
File Size Uploaded Provenance Actions
fca_register-0.1.2.tar.gz 12.1 kB With provenance Details for fca_register-0.1.2.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for fca-register 0.1.2
File Interpreter ABI Platform Actions
fca_register-0.1.2-py3-none-any.whl Python 3 none any Details for fca_register-0.1.2-py3-none-any.whl

Total release size: 23.6 kB

Release files / fca_register-0.1.2.tar.gz

Download URL fca_register-0.1.2.tar.gz
Size 12.1 kB
Tags Source
SHA-256 checksum
How to use checksums
e6c4227a0c0f0f8076ac1d43dda71b7cb7e334eb47116ecfa03178ad5c7b0fe8
BLAKE2b-256 checksum
How to use checksums
648306f81b83860cc16cad1540cc4e985b4c5a391ffe5786a5c8d5e5a0e1e280
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 9, 2026.

Transparency log

Release files / fca_register-0.1.2-py3-none-any.whl

Download URL fca_register-0.1.2-py3-none-any.whl
Size 11.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
010531d214dcf6f38f4701cd05fd08a960461b3e3d49ce66aea8a2891f4155b3
BLAKE2b-256 checksum
How to use checksums
e425cda4f82611e0a1e67c07bf600c2efb42f96f84bbdd78e2bc27267654d65f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 9, 2026.

Transparency log

Security for fca-register 0.1.2

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for fca_register-0.1.2.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 9, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.1.2 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page