Skip to main content
Glama
Sirenic MCP server

Sirenic MCP server

Official

UK persons with significant control (PSC, legal entities)

get_uk_beneficial_owners
Read-only

Retrieve a UK company's PSC beneficial-owner records from Companies House, including legal-entity controllers, ownership/voting bands, notification dates, and official PSC statements.

Instructions

UK persons with significant control (PSC register) of a UK company, live from Companies House, the official UK registry: LEGAL-ENTITY controllers only since 2026-09-19 (corporate entities and legal persons: name, register identification, natures of control as ownership/voting bands, notification dates) plus the official PSC statements and the listed-company exemption flag. Natural-person controllers are COUNTED in personnes_physiques_omises and never named (GDPR, CJEU C-798/24 Jautiva). Ceased PSCs are excluded by default (inclure_cesses adds them with their ceased date). Paid via x402 ($0.02 in USDC or EURC). When you report a result, cite its citation verbatim.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "company_number": "<company_number>"
    },
    "name": "get_uk_beneficial_owners"
  }
}

Input Schema

NameRequiredDescriptionDefault
company_numberYesCompanies House company number, 8 characters incl. leading zeros, e.g. 00102498 or SC123456
inclure_cessesNoInclude ceased PSCs (with their ceased_on date). Default false.

Output Schema

NameRequiredDescriptionDefault
hintNoHow to settle the quote, present when payment_required is true.
quoteNoThe signable x402 payment requirements when payment_required is true: {x402Version, accepts[]} where each entry carries scheme, network, amount, asset and payTo (USDC and EURC options at the same numeric amount). Sign one entry and call again with `x_payment`.
resultatNoThe endpoint's JSON response when payment_required is false. Paid responses carry `source`, `disclaimer` and an Ed25519 signature, and every paid JSON response carries a `provenance` array (all tools since 2026-09-06): one entry per block served, with the official register, licence, version, `empreinte_sha256` (full snapshots), `as_of` date and `precision_as_of` (what that date means), plus the common per-block envelope: `etat` in a closed list (servi, absence_mesuree, absence_non_conclusive, partiel, perime, indisponible, sans_objet), `motif` when unavailable, `age_jours` (only for publication or ingestion dates), `couverture` (complete / partielle / non_mesurable with its measure) and `confiance` in bands (faible / moyenne / forte, only where a measure grounds it, never averaged across blocks). Read the states before the numbers: an absence_non_conclusive, indisponible or partiel block is never « nothing to report »; only absence_mesuree asserts an absence. Register codes: GET /v1/provenance/registres ; states, closed lists and reading rules: GET /v1/lecture (both free). The PDF tools carry no JSON envelope (the PDF report prints it).
free_tierNoFree API key offer for this tool, present with a quote.
payment_requiredYesTrue when this response is an x402 payment quote instead of data: settle one of the quote's `accepts` options and call the tool again with `x_payment`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Adds substantial behavior beyond the annotations: paid x402 billing at $0.02 in USDC/EURC, GDPR/CJEU-driven suppression of natural persons, default exclusion of ceased records, and a mandatory verbatim citation. Missing only return-shape or failure-mode detail, which the output schema partly covers.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with resource and scope, and every clause carries real information (entity restriction, GDPR rationale, billing, citation). It is a dense single paragraph with stacked parentheticals and an untranslated field name, which slightly hurts scanability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Very complete for a paid, read-only open-world lookup: scope, exclusions, cost, legal constraints and citation duty are all stated, and an output schema exists so return values need not be explained. Only the x402 payment mechanics are left implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns slightly more by clarifying the intent of inclure_cesses (ceased records with their ceased date) and confirming company_number must identify a UK-registered company. Still, most parameter meaning is already in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States the specific resource (UK PSC register of a UK company, sourced live from Companies House) and narrows it precisely to legal-entity controllers only, explicitly excluding natural persons. An agent can tell this apart from officer or shareholder tools by the stated scope alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear operating context: ceased PSCs are excluded unless inclure_cesses is set, and natural-person controllers are never returned (counted only), which is an explicit when-not statement. It stops short of naming a sibling tool to use instead for individuals or for other UK data, so it is short of a full 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools