# Fca Register (npm · @pipeworx/mcp-fca-register)

FCA Financial Services Register MCP — the UK Financial Conduct Authority's public register of…

- Trust score: 91/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-22

## Components

- remote · `gateway.pipeworx.io`: 88/100, [markdown](https://verifymcp.io/servers/pipeworx-io-fca-register/fca-register-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-fca-register/fca-register-mcp)
- npm · `@pipeworx/mcp-fca-register`: 91/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-fca-register/pipeworx-mcp-fca-register.md), [page](https://verifymcp.io/servers/pipeworx-io-fca-register/pipeworx-mcp-fca-register)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-fca-register`
- Version: `0.2.2`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-22.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-fca-register).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 20 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 696 tokens (~174/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 77/100
  - Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Fca Register MCP server?

Fca Register runs locally as an npm package, launched with npx -y @pipeworx/mcp-fca-register. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-fca-register -- npx -y @pipeworx/mcp-fca-register
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-fca-register": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-fca-register"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-fca-register": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-fca-register"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-fca-register -- npx -y @pipeworx/mcp-fca-register
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-fca-register": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-fca-register"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-fca-register --command npx --arg -y --arg @pipeworx/mcp-fca-register
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-fca-register:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-fca-register"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-fca-register": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-fca-register"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-fca-register -t stdio -c npx -a -y @pipeworx/mcp-fca-register
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-fca-register": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-fca-register"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-22 (score 91, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 90, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 89, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-15 (score 88, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-13 (score 87, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-11 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-09 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-07 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (4)

### `fca_firm_search` (~167 tokens)

Search the FCA Financial Services Register by firm (or individual/fund) name and return ranked matches with FRN/IRN and a status summary. Example: fca_firm_search({ q: "Barclays Bank", type: "firm" })

Input parameters:

- `_apiKey` (string): Optional. Your own FCA Register API credentials as "<email>:<key>" (the email you registered with, a colon, then the issued key). Omit it to use the Pipeworx key. Register free at https://register.fc…
- `q` (string, required): Name or substring to search for, e.g. "Barclays Bank".
- `type` (string): Which register category to search. Default "firm".

### `fca_firm_details` (~145 tokens)

Look up an FCA-regulated firm by its Firm Reference Number (FRN): returns regulatory status, business type, and registered address. Example: fca_firm_details({ frn: "122702" })

Input parameters:

- `_apiKey` (string): Optional. Your own FCA Register API credentials as "<email>:<key>" (the email you registered with, a colon, then the issued key). Omit it to use the Pipeworx key. Register free at https://register.fc…
- `frn` (string, required): Firm Reference Number, e.g. "122702" (Barclays Bank Plc).

### `fca_firm_representatives` (~156 tokens)

List a firm's appointed representatives (principal/AR relationships) by Firm Reference Number (FRN). Returns an empty list for a firm with no appointed representatives -- that is a real answer, not a failure. Example: fca_firm_representatives({ frn: "122702" })

Input parameters:

- `_apiKey` (string): Optional. Your own FCA Register API credentials as "<email>:<key>" (the email you registered with, a colon, then the issued key). Omit it to use the Pipeworx key. Register free at https://register.fc…
- `frn` (string, required): Firm Reference Number, e.g. "122702".

### `fca_individual_lookup` (~174 tokens)

Look up an individual's own public Financial Services Register record by Individual Reference Number (IRN): name and current approved-function status only -- the register's own published single-lookup fields, nothing more. This tool does not enumerate or list individuals; it looks up exactly one IRN you already have. Example: fca_individual_lookup({ irn: "MXC29012" })

Input parameters:

- `_apiKey` (string): Optional. Your own FCA Register API credentials as "<email>:<key>" (the email you registered with, a colon, then the issued key). Omit it to use the Pipeworx key. Register free at https://register.fc…
- `irn` (string, required): Individual Reference Number, e.g. "MXC29012".

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-fca-register/pipeworx-mcp-fca-register#diagnostics

## Score history

- 2026-11-22: 91
- 2026-11-21: 90
- 2026-11-20: 90
- 2026-11-19: 90
- 2026-11-18: 89
- 2026-11-17: 89
- 2026-11-16: 88
- 2026-11-15: 88
- 2026-11-14: 87
- 2026-11-13: 87
- 2026-11-12: 86
- 2026-11-11: 86
- 2026-11-10: 85
- 2026-11-09: 85
- 2026-11-08: 84
- 2026-11-07: 84
- 2026-11-06: 83
- 2026-11-05: 83
- 2026-11-04: 83
- 2026-11-03: 82
- 2026-11-02: 82
- 2026-11-01: 81
- 2026-10-31: 80
- 2026-10-30: 80

## Common questions

### What is the Fca Register MCP server?

Fca Register is an MCP server listed in the public MCP registry as io.github.pipeworx-io/fca-register. FCA Financial Services Register MCP, the UK Financial Conduct Authority's public register of… This page covers its npm package (@pipeworx/mcp-fca-register).

### Is the Fca Register MCP server safe to use?

Fca Register scores 91 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Fca Register MCP server expose?

Fca Register exposes 4 tools: fca_firm_search, fca_firm_details, fca_firm_representatives, fca_individual_lookup. Their descriptions and schemas cost roughly 642 tokens of context every time the server is loaded.

### Is the Fca Register MCP server still maintained?

Fca Register is still listed as active in the MCP registry. We last reached this channel on 22 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Fca Register MCP server under?

Fca Register declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Fca Register MCP server?

VerifyMCP ran 16 checks on Fca Register, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-fca-register
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-fca-register
- Repository: https://github.com/pipeworx-io/mcp-fca-register
- Website: https://pipeworx.io/packs/fca-register
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-fca-register/pipeworx-mcp-fca-register.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-fca-register/pipeworx-mcp-fca-register/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-fca-register/pipeworx-mcp-fca-register.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-fca-register/pipeworx-mcp-fca-register
