Skip to main content
Glama
fieldnote-agents

Global Company Check MCP Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
APIFY_TOKENYesYour Apify API token, obtained from https://console.apify.com/settings/integrations

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
lookup_companyA

Find a company by legal name in GLEIF open data. Optionally pass an ISO 3166-1 alpha-2 country code (e.g. 'SE', 'DE', 'US') for a much better match. Returns the best match with LEI, legal name, addresses, status and (optionally) parent companies.

lookup_leiB

Look up one 20-character Legal Entity Identifier (LEI) from any country in GLEIF open data. Returns legal name, addresses, registration status and parents.

bulk_lookupA

Look up up to 500 companies in one run. Each query is either an LEI ('549300TTCXZOGZM2EY83') or 'Legal name | CC' with an optional ISO-2 country ('Spotify AB | SE'). One result per query.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 3 tools

Disambiguation4/5

The three tools split cleanly by input key: lookup_company takes a legal name, lookup_lei takes a single 20-char LEI, and bulk_lookup handles many queries. There is mild overlap since bulk_lookup accepts both LEI and 'name | CC' formats, but the single-vs-batch boundary is clear enough to guide selection.

Naming Consistency4/5

All names are snake_case and start with a lookup verb, giving a predictable read (lookup_company, lookup_lei). The only minor deviation is bulk_lookup, which drops the 'lookup_' prefix for the batch variant, but it remains understandable.

Tool Count4/5

Three tools is slightly lean but well-matched to a focused GLEIF data-access service: one per lookup mode (name, LEI, batch). Each tool earns its place without redundancy, though the surface is minimal.

Completeness4/5

Core GLEIF access is covered: name search, single-LEI resolution, and batch lookup, all returning status, addresses and parents. Minor gaps exist (e.g. no reverse/parent-tree traversal or pagination/filter options), but agents can work around these by chaining lookups.

Maintenance

ActivityMaintained
ResponsivenessNo issues