Search, verify & screen 1M+ African companies + their government contracts across 18 registries.
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.
Average 3.8/5 across 4 of 4 tools scored.
Each tool has a clearly distinct purpose: company details, procurement contracts, sanctions screening, and search. No overlaps or ambiguous boundaries.
All tool names follow the verb_noun pattern with underscores (get_company, get_company_procurement, screen_sanctions, search_companies), ensuring predictable and consistent naming.
Four tools is a well-scoped set for a company data server, covering search, detail retrieval, procurement history, and sanctions checks without being too sparse or excessive.
The tool surface covers the core workflows for company research: discovery (search), full records (get_company), and additional signals (procurement and sanctions). No obvious gaps for a read-only data server.
get_companyGet a company recordInspectFetch one company's full record by country code and registration number, legal name, status, entity type, incorporation date, registry source, and any officers held.
| Name | Required | Description | Default |
|---|---|---|---|
| country | Yes | ISO-2 country code, e.g. NG. | |
| registration_no | Yes | The registry number (RC / RCCM / file no.). |
get_company_procurementGet a company's government contractsInspectList the government procurement contracts a company has won (from open-contracting data): the awarding body, contract title, value and date. Strong signal of what a company actually does.
| Name | Required | Description | Default |
|---|---|---|---|
| country | Yes | ISO-2 country code, e.g. NG. | |
| registration_no | Yes | The registry number. |
screen_sanctionsSanctions screeningInspectScreen a company or person name against the OFAC SDN, OFAC Consolidated and UN Security Council lists. Returns any matches with a name-match confidence.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | The name to screen. |
search_companiesSearch African companiesInspectSearch verified companies across 18 African registries by name or registration number, results are ranked by quality (listed and best-detailed companies first). Returns each match's legal name, registration_no, country, status and registry source, plus the total count. To get the full record of any result, call get_company with that result's country and registration_no.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max results (default 10). | |
| query | Yes | Company name or registration number to search for. | |
| country | No | Optional ISO-2 country code to scope the search (e.g. NG, KE, SN). |
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.
No comments yet. Be the first to start the discussion!
