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

Verify a company (registry check)

verify_company

Read-only

Verify a company against its official register, for onboarding or before paying or signing: an outcome with reasons, checks, warning signals and a proof code you can show an auditor. A registry check, not full KYB. Use it to decide about a company. Don't use it for a cheap single read (lookup_company) or with a name (call search_companies first). Inputs: country FR or ES or GB; identifier as for lookup_company (441639465); optional id_scheme; optional reference (your case id). Returns: outcome (verified, partial, unverified; open insolvency never verified) + reasons, checks, signals (present, none_found, not_covered), recent changes, provenance, proof code (FUE-…). Limits: 5 units (1 if not found); keyless 20/day. Stored 24 months. France: insolvency from BODACC since 2008. BODACC events and dated capital. Public contracts won since 2024 (DECP, weekly). Spain: BORME acts since 2 January 2009. Every BORME act as an event. UK: no officers or PSCs. ISINs and BICs from GLEIF, by LEI. No person's name in any answer. Search words: KYB, KYC, verify supplier, vérifier une société, verificar empresa.

Input Schema

Name	Required	Description	Default
`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.
`reference`	No	Optional: your own case id, stored with the result.
`identifier`	Yes	Official ID: FR SIREN or SIRET; ES Registro Mercantil sheet from search_companies. GB: Companies House company number, e.g. 00445790. Never a name.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 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"
+  }
+]

changedInput schema / properties / identifier / description

Previous value: -"Official ID: FR SIREN or SIRET; ES Registro Mercantil sheet from search_companies. Never a name."New value: +"Official ID: FR SIREN or SIRET; ES Registro Mercantil sheet from search_companies. GB: Companies House company number, e.g. 00445790. Never a name."

changedInput schema / properties / identifier / examples

Previous value: -[
-  "441639465",
-  "VI-23266"
-]New value: +[
+  "441639465",
+  "VI-23266",
+  "00445790"
+]

Changed1 schema field changedOct 15, 2026

changedOutput schema / $defs / VerifyResult / properties / outcome / description

Previous value: -"verified, partial, unverified or insufficient_data"New value: +"verified, partial or unverified; equals meta.outcome"

Changed1 schema field changedOct 15, 2026

addedOutput schema / $defs / Name / properties / privacy_note

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Privacy Note"
+}

Changed2 schema fields changedOct 15, 2026

addedOutput schema / $defs / VerifyMeta / properties / freshness

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "source_published_at, retrieved_at, last_verified_at, from_cache, stale and the rule applied.",
+  "title": "Freshness"
+}

addedOutput schema / $defs / VerifyMeta / 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.9/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, and idempotentHint=false. The description adds substantial context beyond those annotations: outcomes such as open insolvency never verifying, rate/cost limits (5 units, keyless 20/day), 24-month storage, country-specific coverage gaps, and the no-person-name constraint.

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

Conciseness5/5

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

The description is dense but front-loaded: purpose first, then usage, inputs, returns, limits, and coverage. Every section adds actionable information for a complex verification tool, with no filler beyond useful search terms.

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?

Given the tool's complexity, the description covers purpose, alternatives, required inputs, outcome semantics, limits, and country-specific coverage. Output schema exists, so the brief return summary is sufficient and appropriately augments rather than duplicates it.

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 description coverage is 100%, so the schema already documents all five parameters. The description still adds useful semantics, especially that identifier is an official ID and "Never a name," and that reference is the caller's own case id stored with the result.

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: "Verify a company against its official register," and explicitly scopes it as "A registry check, not full KYB." It also distinguishes the tool from siblings by naming lookup_company and search_companies as alternatives for different cases.

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 explicit use cases (onboarding, before paying or signing, deciding about a company) and explicit exclusions: don't use for a cheap single read, use lookup_company; don't use with a name, call search_companies first. This is clear when-to-use and when-not-to-use guidance.

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.