What is MCP and why use it?
Model Context Protocol is an open protocol that connects AI applications to external data sources and tools. An MCP server describes the actions it offers; an MCP client inside an AI application calls those actions to carry out your request. You can work with a service's data through a conversation.
Statsnet provides the company data. Ask your assistant to find an organization by its identifier, prepare a company brief or examine relationships. The assistant receives tool results through MCP and uses them as context for its answer. See the official introduction to Model Context Protocol for the underlying concepts.
MCP architecture: how the Statsnet server works
- Describe your task. Specify the company, country and output you need: a short brief, a contract list or a relationship overview.
- The assistant chooses a tool. Its MCP client reads the server's tool descriptions and sends the parameters for the relevant call.
- Statsnet returns data. The server processes the request according to authentication, plan access and available quota.
- The assistant prepares an answer. It organizes the results into an explanation or table. Follow up to request more detail.
For example, an assistant can first identify the correct legal entity, then retrieve its company card and request court cases or government contracts. Each step uses an available tool. This follows the MCP client-server architecture.
The remote Statsnet MCP server is available at https://statsnet.co/mcp over Streamable HTTP. You do not need to deploy a server or maintain a local process to access Statsnet.
MCP servers and external data sources
MCP architecture separates the model's role from the information source. The language model interprets your task and prepares an answer; the MCP connection provides access to the selected service's data. The assistant can request information during the conversation without putting an entire database into a message. How current the answer is still depends on the sources and when they were updated.
One client can work with several MCP servers: for example, retrieving company information from Statsnet and accessing internal sources through separate connections. Integration with corporate databases or access to files requires its own tools and permissions. Connecting Statsnet alone does not give the assistant access to those resources.
Company data available through MCP
Public tools work without an API key. Extended data requires a key and the appropriate plan. The following tools are listed in the Statsnet MCP documentation.
| Tool | Use it to |
|---|---|
search_companies | Find a company by name, BIN/IIN or director. |
get_company | Retrieve a public company card in Markdown. |
get_company_paid | Explore the full card, shareholders, capital, financial history and risks. |
get_gov_contracts | Review government contracts, customers, amounts and dates. |
get_court_cases | Retrieve court cases, parties and outcomes. |
get_relations | Explore connections between officers, shareholders and companies. |
check_individual | Check a person by IIN for company roles and risks. |
Coverage depends on the company and available sources. Ask the assistant to identify missing fields. Individual screening requires Premium or higher and is also available in Pro.
Example prompts for company research
Prepare a counterparty check
Find the company with this BIN in Kazakhstan. Prepare a brief covering its status, director, shareholders and risk indicators. List any information missing from the returned data separately.
Use an exact identifier to distinguish organizations with similar names. Our company verification guide provides a practical sequence for your research.
Analyze government contracts
Retrieve this company's government contracts. Group the returned records by customer and show amounts and dates. State which period the data covers.
This can help you prepare for a meeting and understand a supplier's experience. Ask the assistant to use the returned records and flag incomplete coverage.
Explore relationships
Show other companies associated with this organization's directors and shareholders. For each relationship, identify the person, role and connected company.
Use the result as a starting point for affiliation research. A shared connection alone does not explain the relationship; examine the roles and context.
How to connect Statsnet MCP
1. Prepare your access
For extended tools, choose Pro and create an API key in your account. Use the same key as the REST API. Pass it in the Authorization: Bearer header in your connection settings, rather than in a message to the assistant.
2. Add the MCP server to your client
In Claude Code, run the following command, replacing sk_live_YOUR_KEY with your key:
claude mcp add --transport http statsnet https://statsnet.co/mcp \
--header "Authorization: Bearer sk_live_YOUR_KEY"
For Cursor and other clients that support remote connection settings through mcp.json, use this configuration from the documentation:
{
"mcpServers": {
"statsnet": {
"url": "https://statsnet.co/mcp",
"headers": {
"Authorization": "Bearer sk_live_YOUR_KEY"
}
}
}
}
Keep the file containing your real key in your personal client settings; do not commit it to a shared repository. Current setup options, including Claude Desktop, are in the connection guide.
3. Verify the connection
Confirm that your client can see the Statsnet tools. Start by searching for a known company and check its name and identifier. Then request the extended information you need. To use anonymous access, remove the Authorization header: the two public tools remain available.
MCP or REST API?
| Task | MCP | REST API |
|---|---|---|
| Research a company in a conversation | The assistant selects tools based on your request. | Requires code or an interface to make calls. |
| Add data to your application | Works with an application that has an MCP client. | Suits direct integration with a website, CRM or service. |
| Control the request sequence | Refine the task and review the assistant's actions. | Define the sequence and response handling in code. |
MCP gives AI applications a standard way to interact with tools. REST API works well for a predefined integration process. Both use the same Statsnet API key; request accounting is explained in the service documentation.
Controlling data access and AI actions
Tools and their results become part of the selected AI application's workflow. The model uses the returned information to prepare an answer, so review your client's data handling settings before connecting it. In a corporate environment, establish which sources and information it is permitted to use.
Start with a public company card. Add authenticated requests for extended data when the task requires them. If your MCP client supports tool-call approval, configure it before you begin: some actions consume quota. A single question can trigger several tool calls. Ask the assistant to explain its research plan and list the data it needs first, especially when investigating multiple companies.
Frequently asked questions
Is MCP included in Pro?
Yes. MCP is included in Pro. Paid tools use your subscription's permissions and quota. See the plans page for features and pricing.
Can I try it without an API key?
Yes. Company search and public company cards are available without a key. Anonymous search is limited to 30 requests per hour per IP. Authenticated search returns up to 50 results per call without that IP limit.
How are paid requests counted?
Accounting matches the REST API: API plans are metered per call; report plans consume one report per company card with free reuse for two weeks. Retrieving a full card consumes plan quota.
Why do I get HTTP 401 or a tool error?
HTTP 401 indicates an invalid or revoked key. The server does not silently switch the request to anonymous access. Quota or plan restrictions return an explanatory tool error. Check your key and subscription in your account, or contact support.
Do I need to build my own MCP server?
No. Connect the existing remote Statsnet server to a compatible client. You would need your own implementation for a separate integration with your own data sources or business logic.
Does MCP show changes in real time?
The connection lets you request data during a conversation, but it does not guarantee instant updates across all registries. Check record dates and reporting periods. Querying an MCP server and updating the original database are separate processes.
Should the assistant make the final decision about a company?
Treat its answer as a working summary. Verify the company identifier, data period and material facts against the company card and original sources. Ask it to distinguish returned information from interpretation and identify gaps.
Start working with MCP
Open the MCP connection guide, create a key in your account and ask your first question about a company. Choose Pro for extended access. If you need help with setup, contact Statsnet.