Fuentio: UK, France & Spain company data from official registries

See what changed at a company

get_company_history

Read-onlyIdempotent

See what changed at a company, and when: versions with the fields that changed (address, status), each with its official source. Use it for changes over time. Don't use it for the current state: call lookup_company. Inputs: country FR or ES or GB; identifier as for lookup_company (441639465); optional id_scheme; page. Returns: versions newest first with source, fetched_at and the fields changed; dated events where the source has them (BORME acts, Companies House filings). meta.history_since says where history starts. Limits: 1 unit; keyless 20 units a day. Read-only. France: from Fuentio's first fetch of the company. Spain: from 2 January 2009. United Kingdom: the latest filings, and every change since Fuentio first held it. Search words: historique, historial, cambios, due diligence.

Input Schema

Name	Required	Description	Default
`page`	No	Versions page, 10 per page.
`detail`	No	summary: a few key fields; standard (default): the record, long lists shortened; full: everything.	standard
`country`	Yes	ISO country code: FR or ES or GB.
`id_scheme`	No	Optional: force the ID type when it is ambiguous.
`identifier`	Yes	Official ID, as for lookup_company.

Output Schema

Name	Required	Description	Default
`data`	Yes
`meta`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 16, 2026

changedInput schema / properties / country / description

Previous value: -"ISO country code: FR or ES."New value: +"ISO country code: FR or ES or GB."

changedInput schema / properties / country / enum

Previous value: -[
-  "FR",
-  "ES"
-]New value: +[
+  "FR",
+  "ES",
+  "GB"
+]

changedInput schema / properties / id_scheme / anyOf

Previous value: -[
-  {
-    "enum": [
-      "FR_SIREN",
-      "FR_SIRET",
-      "EU_VAT",
-      "LEI",
-      "ES_RM_HOJA",
-      "ES_NIF"
-    ],
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "FR_SIREN",
+      "FR_SIRET",
+      "EU_VAT",
+      "LEI",
+      "ES_RM_HOJA",
+      "ES_NIF",
+      "GB_COMPANY_NUMBER"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

Changed1 schema field changedOct 15, 2026

addedOutput schema / $defs / HistoryMeta / properties / outcome

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "verified, partial, unverified, status_unknown, not_found, not_covered, ambiguous, stale or source_unavailable: https://api.fuentio.com/docs/outcomes",
+  "title": "Outcome"
+}

First observedOct 12, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare read-only/idempotent/non-destructive, but the description goes well beyond them: a cost model (1 unit, keyless 20 units/day) and country-specific history depth (France from Fuentio's first fetch, Spain from 2 Jan 2009, UK latest filings plus everything since first held). These are non-obvious operational constraints an agent cannot infer from the schema or annotations.

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 purpose, then alternative, inputs, returns, limits, and search words in labeled blocks, which makes it skimmable. It is on the long side and 'Read-only' restates the annotation, but nearly every line carries usable information.

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

Completeness5/5

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

For a history/versioning tool with five parameters and an output schema, nothing material is missing. It covers the sibling alternative, the quota cost, per-country history horizons, and the meaning of meta.history_since, so an agent can call it and interpret the result correctly.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents country, identifier, id_scheme, page, and detail. The description adds only one genuinely useful link ('identifier as for lookup_company') and otherwise restates enum values; notably it never mentions the `detail` parameter at all, so it adds little beyond the structured fields.

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 a specific verb and resource ('see what changed at a company, and when') and immediately names the discriminating content: versions with the changed fields plus their official source. It explicitly separates itself from lookup_company, so an agent can route between the two without opening either schema.

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

Usage Guidelines5/5

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

Gives both the positive case ('Use it for changes over time') and the exclusion ('Don't use it for the current state: call lookup_company'), naming the alternative tool directly. It also lists the supported countries and identifier style, which tells the agent when this tool is even applicable.

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

All Fuentio: UK, France & Spain company data from official registries tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.