Fuentio: UK, France & Spain company data from official registries
REMOTE · API.FUENTIO.COM
Official UK, France and Spain company checks for AI agents
Available components
Last scanned (12 hours ago)
Scores higher than 91% of remote servers
Reachable. Last reached 5 Nov 2026.
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 5678 tokens (~246/item across 23 items; 19 tools + 4 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 95% of tool parameters carry a description.Partial
- Structured output schemas are declared (95% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 19 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
- Supports UI / widget rendering.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +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.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “lookup_company” rewrote its description, which is the text the model reads security
- Tool “search_companies” rewrote its description, which is the text the model reads security
- Tool “verify_company” rewrote its description, which is the text the model reads security
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +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.
- 24 Oct 26 +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.
- 22 Oct 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://api.fuentio.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=fuentio.com | CN=YE1,O=Let's Encrypt,C=US | 6 Oct 2026 | 4 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 54c8f5769a74e29eedc7fb386686255960a |
| SANs: *.fuentio.com, fuentio.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.fuentio.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| fuentio.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| content-security-policy | frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.fuentio.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.fuentio.com/mcp | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_address Validate a company's registered address ~203
Validate a company's registered address against the official address base: France via API Adresse (Base Adresse Nationale, IGN). Use it to check that an address exists and is the company's, or to geolocate it. Don't use it to find companies: call search_companies. Inputs: country and identifier, as lookup_company (e.g. 'FR', '441639465'). Returns: validated (true, false or null with a reason), normalized address, BAN ids, coordinates, precision, confidence, and how many active companies share the address. Limits: 1 unit. Spain not available yet. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | ISO country code: FR or ES or GB. |
| identifier | string | yes | Official ID, as lookup_company: FR SIREN (9 digits), SIRET or VAT; ES Registro Mercantil sheet, e.g. VI-23266. GB: Companies House company number, e.g. 00445790. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
| meta | object | yes | – |
No examples provided.
check_insolvency Insolvency notices and state of a company ~216
Check a company's insolvency notices and state: France from BODACC (safeguard, reorganisation, liquidation, plans, closures), Spain from BORME insolvency acts. Use it for credit or supplier checks. Don't use it for sanctions: call screen_company. Inputs: country and identifier, as lookup_company (e.g. 'FR', '441639465'). Returns: state (in_procedure, under_plan, closed, notice_found, none_found, not_covered), procedure, dates, notices with official citations, covered_since. Limits: 1 unit. No notice outside the loaded years is not proof of no procedure. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | ISO country code: FR or ES or GB. |
| identifier | string | yes | Official ID, as lookup_company: FR SIREN (9 digits), SIRET or VAT; ES Registro Mercantil sheet, e.g. VI-23266. GB: Companies House company number, e.g. 00445790. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
| meta | object | yes | – |
No examples provided.
check_supplier_list Check a supplier list (registry check) ~238
Check a supplier list against the official registers: which suppliers are ok, which need a look and why (e.g. in liquidation since a date, per BODACC), with a proof code each, and a private report link to share. Use it for 2 to 100 suppliers at once, or to read a batch you started. Don't use it for one company: call verify_company. Inputs: rows [{reference, company_name, country, identifier}] (an official ID is best; a name alone counts only with postal_code and street matching one company), or batch_id. Returns: counts by review_state (ok, review, could_not_confirm, not_covered, error), the review rows with reasons, share_url; 'next' when still checking. Limits: 5 units a row (+2 for a name), checks reused 24 h free. A registry check, not KYB or sanctions clearance; no person's name.
| Name | Type | Req | Description |
|---|---|---|---|
| batch_id | – | – | A batch this key started, e.g. sb_3Kq9… |
| rows | – | – | Up to 100 suppliers. Leave out to read a batch_id. |
No output schema declared.
No examples provided.
check_vat A company's EU VAT number (registration not checked) ~189
Give a company's EU VAT number and how it was obtained. Registration is never checked: the answer links the official VIES page. Use it to fill an invoice or a supplier file. Don't use it as proof of VAT registration: check it on VIES. Inputs: country and identifier, as lookup_company (e.g. 'FR', '441639465'). Returns: number, origin (published or computed), registration_checked false, note, check_url. Limits: 1 unit. Spain: no VAT numbers published. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | ISO country code: FR or ES or GB. |
| identifier | string | yes | Official ID, as lookup_company: FR SIREN (9 digits), SIRET or VAT; ES Registro Mercantil sheet, e.g. VI-23266. GB: Companies House company number, e.g. 00445790. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
| meta | object | yes | – |
No examples provided.
explain_match Why two records are (or aren't) the same company ~172
Explain why two register records are, or are not, the same company: today's decision with reason codes and evidence, stored decisions, links, and whether they share one Fuentio entity. Use it after resolve_company or lookup_company when you must justify a match or a rejection. Don't use it to find companies: call resolve_company. Inputs: left and right, Fuentio record IDs (e.g. 'FR-SIREN-441639465', 'FR-LEI-969500F7JLTX36OUI695'). Returns: same_entity, summary, decision (status, band, reasons), stored_decisions, links, uncertainty. Limits: 1 unit. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| left | string | yes | A Fuentio record ID. |
| right | string | yes | Another record ID. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
| meta | object | yes | – |
No examples provided.
get_company_history See what changed at a company ~278
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.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | ISO country code: FR or ES or GB. |
| detail | string | – | summary: a few key fields; standard (default): the record, long lists shortened; full: everything. |
| id_scheme | – | – | Optional: force the ID type when it is ambiguous. |
| identifier | string | yes | Official ID, as for lookup_company. |
| page | integer | – | Versions page, 10 per page. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
| meta | – | yes | – |
No examples provided.
get_evidence The evidence behind a company's facts ~198
Show the evidence behind what Fuentio says about a company: for each field, the value served and every competing value with its source, record, retrieval time, source link and record hash; and the match decision behind each link. Use it to justify an answer in a review or an audit. Don't use it to look a company up: call resolve_company first for its entity_id. Inputs: entity_id (e.g. 'fu_7K3M9Q2XH4PZ'), optional field (name, status, address, legal_form, creation_date, activity), optional as_of 'YYYY-MM-DD'. Returns: evidence, links, decisions, uncertainty, how_to_check. Limits: 1 unit. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | – | – | YYYY-MM-DD. |
| entity_id | string | yes | A Fuentio entity ID (from resolve_company). |
| field | – | – | One field, e.g. status. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
| meta | object | yes | – |
No examples provided.
get_graph A company's group: GLEIF parents and subsidiaries ~187
Show a company's group: its parent and child companies from GLEIF (direct and ultimate parents), company to company, every edge with its source. Use it to map a company's group. Don't use it to look a company up: call resolve_company first for its entity_id. Inputs: entity_id (e.g. 'fu_7K3M9Q2XH4PZ'), depth 1 or 2. Returns: nodes (companies), edges (from, kind parent_of, to, source, evidence), ownership (signals only; beneficial owners not covered), uncertainty. Limits: 2 units; API key required. No people, no director links. A company without an LEI shows no links. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| depth | integer | – | 1 or 2. |
| entity_id | string | yes | A Fuentio entity ID (from resolve_company). |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
| meta | object | yes | – |
No examples provided.
get_receipt Get a verification receipt by proof code ~292
Give back the Fuentio receipt of a verification by its proof code: outcome and reasons, status, legal form, registered office, insolvency (what was searched), source, check time, hash and the public link to check it. Use it when the user asks for a receipt or proof of a check. Always ask the user first: 'Normal or detailed receipt?', then call it. Use the proof code from verify_company. Don't use it to run a new check: call verify_company. Inputs: proof_code (e.g. 'FUE-FR-20261015-DZ7TP9', any case; a lookup's meta.receipt.request_id also works, same key), format 'normal' or 'detailed'. Returns: data.markdown, the branded receipt: show it as is; data.text, plain text. Limits: free; 30 a minute. The key that ran the check also sees its reference; anyone else, the public view. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | yes | Ask the user first: 'normal' (the receipt) or 'detailed' (also every check, the signals, changes, sources and the full hash re-checked). |
| proof_code | string | yes | The proof code verify_company returned (FUE-XX-YYYYMMDD-XXXXXX; any case or spacing), or a lookup's meta.receipt.request_id. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
| meta | object | yes | – |
No examples provided.
list_coverage List covered countries and ID formats ~175
List the countries, ID formats and official sources Fuentio covers. Free, no key. Use it first when unsure whether a country or ID format is supported, or to explain coverage. Don't use it to check a company: call lookup_company or search_companies. Inputs: none. Example: list_coverage(). Returns: per country, status (available or planned), coverage level, ID formats with real examples and whether lookup works, regional registers, and sources with licence and update frequency. Limits: 0 units. Read-only. Covered today: France, Spain and United Kingdom. Search words: company registry, KYB, SIREN, RCS, Annuaire des Entreprises, société; BORME, Registro Mercantil, empresa, sociedad; Companies House, company number, Ltd, plc, LLP.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | yes | – |
| meta | – | yes | – |
No examples provided.
lookup_company Look up a company by official ID ~576
Look up one company in its official register by ID: status, address, legal form, activity, source and check date. Use it when you have an official ID. Don't use it with a name: call search_companies first. Inputs: country FR or ES or GB; identifier. FR: SIREN 441639465, SIRET 44163946500091, VAT FR63441639465, LEI 969500F7JLTX36OUI695. ES: Registro Mercantil sheet VI-23266, LEI 549300EEJH4FEPDBBR25 (no NIF/CIF). GB: company number 00445790, LEI 2138002P5RNKC5W2JZ46. Optional: id_scheme (if ambiguous), format (json, csv, tsv, markdown, html, xml, ndjson; xlsx or parquet as a 24 h link). Returns: the record, a one-line summary, meta with source, source_url, last_verified_at. Limits: 1 unit (also a valid ID not found); keyless 20/day. 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. For KYB steps, supplier checks, due diligence: SIREN, RCS, Annuaire des Entreprises, société; BORME, Registro Mercantil, empresa, sociedad; Companies House, company number, Ltd, plc, LLP.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | ISO country code: FR or ES or GB. |
| detail | string | – | summary: a few key fields; standard (default): the record, long lists shortened; full: everything. |
| format | string | – | Answer format: json (default); csv, tsv, markdown, html (table), xml or ndjson come back inline, one row per company with source and fetched_at; xlsx or parquet as a download link valid 24 hours. Sam… |
| id_scheme | – | – | Optional: force the ID type when it is ambiguous. |
| identifier | string | yes | Official ID. FR: SIREN (9 digits), SIRET (14) or VAT (FR + 11). ES: Registro Mercantil sheet, e.g. VI-23266. GB: Companies House company number, e.g. 00445790. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | The record; a few key fields with detail=summary (when enabled); null when meta.export holds it. |
| meta | – | yes | – |
No examples provided.
report_issue Report a wrong or missing answer ~158
Report an answer you believe is wrong or missing, so Fuentio checks it against the official source. Use it when a result contradicts an official document you hold. Don't use it to ask questions: call the lookup tools. Inputs: subject (entity ID, record ID such as 'FR-SIREN-441639465', or tool name), category (wrong_data, wrong_link, missing_data, wrong_status, other), message. Returns: issue_id, status 'open'. Limits: free; API key required; 20 reports per key per day.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | – |
| message | string | yes | What you expected and what you got. |
| subject | string | yes | Entity ID, record ID or tool name. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
| meta | object | yes | – |
No examples provided.
resolve_company Is this the same company? (match with evidence) ~259
Decide whether a company you know (an official ID, or a name with a postcode or town) is a company in the official registers, with evidence: candidates each with a decision, linked, possible or rejected, and the reasons. Use it to match a supplier or customer record to a register record. Don't use it to read a company you already identified: call lookup_company. Inputs: country FR or ES or GB; name ('Renault', postal_code '92100') and/or identifier (441639465); optional id_scheme, locality, limit (1-10). Returns: outcome (linked, possible_match, no_match), uncertainty, best, candidates with entity_id, reason codes and evidence. Limits: 2 units. Only an official ID links: a name, even with an address, is never proof. Read-only, nothing stored.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | ISO country code: FR or ES or GB. |
| id_scheme | – | – | Optional: force the ID type. |
| identifier | – | – | An official ID, if you have one: the only thing that links exactly. |
| limit | integer | – | Candidates. |
| locality | – | – | – |
| name | – | – | The company's name as you have it. |
| postal_code | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
| meta | object | yes | – |
No examples provided.
review_report A review-ready report on a company ~233
Produce one review-ready report on a company: identity and links with reasons, facts with sources, last year's changes and gaps, and every check at once (insolvency, sanctions, address, VAT, and in France the public contracts won). Use it for the registry part of a KYB or supplier review you must file (not full KYB: no UBO, PEP or adverse-media checks). Don't use it for one quick fact: call lookup_company. Inputs: country and identifier, as lookup_company (e.g. 'FR', '441639465'). Returns: company, facts, links, decisions, changes_last_year, modules, gaps, uncertainty, sha256, markdown. Limits: 8 units; API key required. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | ISO country code: FR or ES or GB. |
| identifier | string | yes | Official ID, as lookup_company: FR SIREN (9 digits), SIRET or VAT; ES Registro Mercantil sheet, e.g. VI-23266. GB: Companies House company number, e.g. 00445790. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
| meta | object | yes | – |
No examples provided.
screen_company Screen a company against sanctions lists ~238
Screen a company's own names against sanctions lists: EU Financial Sanctions File, UK Sanctions List, OFAC SDN list, France's registre des gels. Use it as the sanctions-list step of onboarding a supplier or customer (not full KYB). Don't use it to identify a company: call resolve_company or lookup_company first. Inputs: country and identifier, as lookup_company (e.g. 'FR', '441639465'). Returns: result 'possible_match' (list, entry, score, reasons, listing date, legal act, official link), 'no_match_found' or 'not_checked', the list versions, and a note. Limits: 2 units; API key required. A possible match is not proof; no match is never 'clear'. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | ISO country code: FR or ES or GB. |
| identifier | string | yes | Official ID, as lookup_company: FR SIREN (9 digits), SIRET or VAT; ES Registro Mercantil sheet, e.g. VI-23266. GB: Companies House company number, e.g. 00445790. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
| meta | object | yes | – |
No examples provided.
search_companies Search companies by name ~523
Find companies by name in the official registers of France, Spain and United Kingdom, 10 per page. Use it when you know a name but no ID, then call lookup_company or verify_company with an ID from the results. Don't use it when you already have an official ID. Inputs: country FR or ES or GB; query, 2 to 200 characters ('telefonica'). Optional: postal_code, locality, status, jurisdiction (regional registers), page, format; limit (up to 100 rows) with a file format. Returns: best match first, each with match.score (0-1) and reasons, name, status, address, IDs, provenance; meta.next_page. Limits: 2 units a page; files 2 per started 25 rows. Read-only. 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: SIREN, RCS, Annuaire des Entreprises, société; BORME, Registro Mercantil, empresa, sociedad; Companies House, company number, Ltd, plc, LLP, KYB, supplier check.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | ISO country code: FR or ES or GB. |
| format | string | – | Answer format: json (default); csv, tsv, markdown, html (table), xml or ndjson come back inline, one row per company with source and fetched_at; xlsx or parquet as a download link valid 24 hours. Sam… |
| jurisdiction | – | – | Optional ISO 3166-2 region to search in, for countries with regional registers (list_coverage lists them). |
| limit | – | – | Rows in one file, up to 100, with a non-json format only. 2 units per started 25 rows (100 rows = 8 units). |
| locality | – | – | Registered-office town filter (Spain). |
| page | integer | – | Results page, 10 per page. |
| postal_code | – | – | Registered-office postal code filter. |
| query | string | yes | Company name, 2 to 200 characters. |
| status | – | – | Only companies with this status. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | yes | – |
| meta | – | yes | – |
No examples provided.
verify_company Verify a company (registry check) ~407
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.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | ISO country code: FR or ES or GB. |
| detail | string | – | summary: a few key fields; standard (default): the record, long lists shortened; full: everything. |
| id_scheme | – | – | Optional: force the ID type. |
| identifier | string | 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. |
| reference | – | – | Optional: your own case id, stored with the result. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
| meta | – | yes | – |
No examples provided.
watch_company Watch a company for changes (signed webhooks) ~141
Watch a company: when its official records change, Fuentio POSTs the changes, signed, to your https endpoint. Use it to monitor a supplier or customer. Don't use it for a one-off check: call what_changed. Inputs: entity_id (from resolve_company), callback_url (your https endpoint; private or local addresses are refused). Returns: watch_id, signing_secret (shown once) and how to verify each POST. Limits: 1 unit; API key required; free plan 3 watches.
| Name | Type | Req | Description |
|---|---|---|---|
| callback_url | string | yes | Your https endpoint. |
| entity_id | string | yes | A Fuentio entity ID (from resolve_company). |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
| meta | object | yes | – |
No examples provided.
what_changed What changed at a company since a date ~212
List what changed at a company since a date, from every official record Fuentio holds for it: status, name, address, legal form, and the source's dated events (BORME acts), each with its source and evidence. Use it to review a supplier or customer since your last check. Don't use it for the current state: call lookup_company. Inputs: entity_id (from resolve_company, e.g. 'fu_7K3M9Q2XH4PZ'), since 'YYYY-MM-DD', optional until. Returns: changes (type, old/new or added/removed, observed_at or effective_date, source, evidence), gaps (days not loaded, sources not checked since), uncertainty. Limits: 1 unit. A gap is never reported as no change. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_id | string | yes | A Fuentio entity ID (from resolve_company). |
| since | string | yes | YYYY-MM-DD. |
| until | – | – | YYYY-MM-DD; default today. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
| meta | object | yes | – |
No examples provided.
How do I install the Fuentio: UK, France & Spain company data from official… MCP server?
Fuentio: UK, France & Spain company data from official… is a hosted endpoint at https://api.fuentio.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.fuentio.com
claude mcp add --transport http com-fuentio-company-data 'https://api.fuentio.com/mcp'
What is the Fuentio: UK, France & Spain company data from official… MCP server?
Fuentio: UK, France & Spain company data from official… is an MCP server listed in the public MCP registry as com.fuentio/company-data. Official UK, France and Spain company checks for AI agents. This page covers its hosted endpoint (https://api.fuentio.com/mcp).
Is the Fuentio: UK, France & Spain company data from official… MCP server safe to use?
Fuentio: UK, France & Spain company data from official… scores 85 out of 100 on VerifyMCP. 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 Fuentio: UK, France & Spain company data from official… MCP server expose?
Fuentio: UK, France & Spain company data from official… exposes 19 tools: lookup_company, search_companies, get_company_history, verify_company, get_receipt, and 14 more. Their descriptions and schemas cost roughly 4,895 tokens of context every time the server is loaded.
Does the Fuentio: UK, France & Spain company data from official… MCP server require authentication?
No. We connected to Fuentio: UK, France & Spain company data from official… without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Fuentio: UK, France & Spain company data from official… MCP server still maintained?
Fuentio: UK, France & Spain company data from official… is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.