ENTIA Entity Verification MCP

Entity Lookup

entity_lookup

Read-onlyIdempotent

Look up any business entity by name, CIF/NIF, EU VAT, or LEI. Free callers receive a trace-level identity preview; authenticated callers receive the full paid dossier.

Input Schema

TableJSON Schema

Name	Required	Description
`q`	No	Company name, CIF/NIF (B82846825), EU VAT (ESB82846825), or LEI (20 chars)
`name`	No	Alias for `q` — accepted for compatibility with clients that send `name`.
`query`	No	Alias for `q` — accepted for compatibility with clients that send `query`.

Output Schema

TableJSON Schema

Name	Required	Description
`_meta`	No
`found`	No	True only when an identity anchor corroborated the query
`query`	No
`entity`	No	Verified identity: legal name, tax id, address, sector
`integrity`	No	Tamper-evidence MAC. Not an electronic signature
`error_code`	No
`provenance`	No	Publisher and data sources of this answer
`data_coverage`	No	Which sources answered and which did not
`registry_data`	No	Official registry payload (BORME/GLEIF/VIES/native)
`coherence_errors`	No
`economic_profile`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedAug 30, 2026

addedOutput schema / properties / integrity

Added value: +{
+  "description": "Tamper-evidence MAC. Not an electronic signature",
+  "type": "object"
+}

removedOutput schema / properties / legal_framework
```
Removed value: -{
-  "type": "object"
-}
```

addedOutput schema / properties / provenance

Added value: +{
+  "description": "Publisher and data sources of this answer",
+  "type": "object"
+}

removedOutput schema / properties / signature

Removed value: -{
-  "description": "Provenance signature of this answer",
-  "type": "string"
-}

Changed1 schema field changedAug 18, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Identity resolution result. `found` is fail-closed: false means no identity anchor was corroborated, not 'try again'.",
+  "properties": {
+    "_meta": {
+      "type": "object"
+    },
+    "coherence_errors": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "data_coverage": {
+      "description": "Which sources answered and which did not",
+      "type": "object"
+    },
+    "economic_profile": {
+      "type": "object"
+    },
+    "entity": {
+      "description": "Verified identity: legal name, tax id, address, sector",
+      "type": "object"
+    },
+    "error_code": {
+      "type": "string"
+    },
+    "found": {
+      "description": "True only when an identity anchor corroborated the query",
+      "type": "boolean"
+    },
+    "legal_framework": {
+      "type": "object"
+    },
+    "query": {
+      "type": "string"
+    },
+    "registry_data": {
+      "description": "Official registry payload (BORME/GLEIF/VIES/native)",
+      "type": "object"
+    },
+    "signature": {
+      "description": "Provenance signature of this answer",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed3 schema fields changedJul 8, 2026

addedInput schema / properties / name

Added value: +{
+  "description": "Alias for `q` — accepted for compatibility with clients that send `name`.",
+  "type": "string"
+}

addedInput schema / properties / query

Added value: +{
+  "description": "Alias for `q` — accepted for compatibility with clients that send `query`.",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "q"
-]New value: +[]

Changed12 schema fields changedMay 26, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

removedInput schema / properties / country

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "ISO country code (ES, GB, FR...). Auto-detected from VAT prefix if not provided"
-}

removedInput schema / properties / name

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Alias for query — pass company name here if your client serializes 'name'"
-}

removedInput schema / properties / q / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / q / default
```
Removed value: -null
```

changedInput schema / properties / q / description

Previous value: -"Alias for query — pass here if your client serializes 'q' instead of 'query'"New value: +"Company name, CIF/NIF (B82846825), EU VAT (ESB82846825), or LEI (20 chars)"

addedInput schema / properties / q / maxLength
```
Added value: +500
```
addedInput schema / properties / q / minLength
```
Added value: +2
```
addedInput schema / properties / q / type
```
Added value: +"string"
```

removedInput schema / properties / query

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "CIF (e.g. B80988678), EU VAT (e.g. ESB80988678, FR12345678901), LEI (20 alphanumeric chars), or company name"
-}

addedInput schema / required
```
Added value: +[
+  "q"
+]
```

changedOutput schema / (root)

Previous value: -{
-  "additionalProperties": true,
-  "type": "object"
-}New value: +null

First observedMay 3, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already establish that this is read-only, idempotent, and non-destructive, so the description only needs to add context beyond that. It does so by disclosing an auth-dependent output split: free callers get a trace-level preview, while authenticated callers get the full paid dossier. This is useful behavioral context that annotations do not capture.

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?

Two sentences with no filler: the first states the core purpose and accepted identifiers, and the second adds the key access-level behavior. Every sentence earns its place, and the most important information is front-loaded.

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?

For a read-only lookup with three optional parameters and an existing output schema, the description covers the essential context: what can be looked up and what different callers receive. It does not specify behavior when no query parameter is supplied, but the output schema and annotations reduce the impact of that gap.

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%; q, name, and query are each documented in the schema, including alias relationships. The description adds no parameter-level detail beyond what the schema already provides, so it stays at the baseline for high schema coverage.

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

Purpose4/5

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

The description names a specific verb ('look up'), a resource ('business entity'), and the accepted identifier types (name, CIF/NIF, EU VAT, LEI). It is immediately clear what the tool does, though it does not explicitly differentiate itself from siblings like search_entities or get_full_dossier.

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

Usage Guidelines3/5

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

The identifier list and 'look up any business entity' imply when the tool should be used, but the description gives no explicit guidance about alternatives or exclusions. With sibling tools such as verify_vat, search_entities, and get_full_dossier, the routing decision is left to inference.

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

All ENTIA Entity Verification MCP 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.

Resources

Need Help?