ENTIA — 5.5M Verified Entities for AI Agents
Server Details
20 tools: entity lookup, BORME, EU VAT, GLEIF, healthcare registries, economic data. 34 countries.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.3/5 across 6 of 6 tools scored.
Most tools have distinct purposes: borme_lookup focuses on Spanish mercantile acts, entity_lookup provides comprehensive entity verification, get_competitors identifies competitors, search_entities offers general entity search, verify_vat handles VAT validation, and zone_profile delivers socioeconomic data. However, entity_lookup and search_entities could potentially overlap in entity search functionality, though their descriptions emphasize different aspects (verification vs. general search).
The tools follow a consistent snake_case naming convention throughout. Most names clearly indicate their function with a verb-noun pattern (e.g., entity_lookup, verify_vat, zone_profile), though borme_lookup uses an acronym as the noun and get_competitors uses 'get' instead of a more descriptive verb like 'find', which is a minor deviation from perfect consistency.
With 6 tools, this server is well-scoped for its purpose of providing verified entity and socioeconomic data. Each tool addresses a specific, valuable use case within the domain, such as entity verification, competitive analysis, VAT validation, and zone profiling. The count is neither too sparse nor bloated, allowing for focused functionality without overwhelming complexity.
The toolset covers key aspects of entity data and socioeconomic profiling, including lookup, search, verification, competitive analysis, and zone data. It integrates multiple official sources like BORME, VIES, and Spanish government agencies. A minor gap is the lack of tools for updating or managing entity data (e.g., add_entity or update_entity), but this may be intentional if the server is read-only. Core workflows for data retrieval and analysis are well-supported.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!