How to Connect Checko to Microsoft Copilot via MCP

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Checko, paste your credentials, mint an MCP API key and you're done. No Docker, no git clone, no local server.

Checko + Microsoft Copilot

Checko due diligence on Russian companies and entrepreneurs (EGRUL, EGRIP): company details, directors and founders, contacts, financial statements, reliability score, arbitration cases, enforcement proceedings, public procurement contracts, Fedresurs and bankruptcy messages, inspections, banks and search. Read-only.

Prerequisites

See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:

CHECKO_API_KEY

Step 1 — Get credentials

Setting up takes about 2 minutes. You need a Checko account; the API key comes with it.

1. Register at https://checko.ru and open your personal account (Личный кабинет). The API key is shown there right after registration.
2. Paste it into CHECKO_API_KEY. The connector sends it as the key query parameter.
3. Install the connector and run checko_get_bank: the install check reads Sberbank (BIC 044525225) and shows that the key works.

Identifiers: an INN has 10 digits for an organisation and 12 for an entrepreneur or a private person; an OGRN has 13 digits (organisation), an OGRNIP 15 (entrepreneur). Most tools take inn or ogrn, and one of them is enough. A branch shares the INN of its head organisation, so the head organisation is what comes back.

What it reads: organisations from EGRUL and entrepreneurs from EGRIP with status, registration, legal address, OKVED activity codes, directors, founders and their shares, related companies, licences, branches, contacts, taxes and tax debts, SME register entries, risk factors and sanctions; the business links of a private person by personal INN; financial statements by line code; a reliability assessment with positive and negative factors; the history of register changes; arbitration court cases; FSSP enforcement proceedings; public procurement contracts under 44-FZ, 94-FZ and 223-FZ; Fedresurs messages and EFRSB bankruptcy messages; state inspections; and Russian banks by BIC from the Bank of Russia directory.

How the AI works with it: to find a company it searches with checko_search (a name of at least 4 characters, or a director, founder, phone, e-mail, OKVED code or registration date) and then reads the result with checko_get_company by INN. For due diligence on a counterparty it combines checko_get_company, checko_get_reliability, checko_get_finances (revenue is line 2110, net profit line 2400), checko_list_legal_cases with the role defendant, checko_list_enforcements, checko_list_bankruptcy_messages, checko_list_fedresurs_messages and checko_list_inspections. For public procurement it filters checko_list_contracts by law 44, 94 or 223 and by role customer or supplier.

Read-only: all 14 tools only read. Nothing is filed or changed, so there is nothing to confirm and no tool is switched off at install.

Paging: list tools return up to 100 rows per page (limit, page) together with the total count. Every answer carries meta with the status, the number of requests made today and the account balance in roubles.

Costs and limits: the first 100 requests a day are free on every plan; after that each successful request (HTTP 200) is billed at the plan price, from 0.10 to 0.15 roubles, and errors are free. The technical limit is 32 requests per second per IP address. The AI prefers one targeted call over many broad ones.

Common errors: 401 with meta.message means a missing or invalid key. 402, or a message about the balance, means the free daily quota is used up and the balance is empty. 404 means nothing was found for that INN or OGRN. Error answers carry meta.status error and the reason in meta.message, in Russian.

The connector does not cover companies from Belarus, the raw EGRUL source data or Checko's bulk datasets.

Step 2 — Install the adapter

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Step 3 — Add the connector in Microsoft Copilot

Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide shows YOUR_SERVER_ID.

Microsoft Copilot uses MCP servers through agents built in Copilot Studio: you add AnythingMCP to an agent as a tool, then publish the agent to Microsoft 365 Copilot and Teams. Copilot Studio connects from Microsoft's cloud over Streamable HTTP, which AnythingMCP supports.

1. In Copilot Studio, open your agent (or create one), go to Tools and choose Add a tool → New tool → Model Context Protocol.
2. Enter a Server name (for example AnythingMCP), a Server description that says what the connector does, and the Server URL https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID. Copilot Studio uses the description to decide when to call the server.
3. Under authentication, choose API key, set Type to Header and the header name to X-API-Key, then select Create.
4. In Add tool, choose Create a new connection, paste an MCP API key from AnythingMCP (MCP Servers → your server → API keys) and select Add to agent.
5. Try it in the agent's Test pane: ask for something that needs the Checko tools.
6. Select Publish, then Channels → Microsoft 365 and Microsoft Teams, keep Make agent available in Microsoft Copilot selected and choose Add channel. See agent in Teams installs it for you; in Microsoft 365 Copilot, type @ and pick the agent.

Prefer per-user sign-in? Choose OAuth 2.0 → Dynamic discovery instead of an API key: each user then signs in to AnythingMCP the first time the agent calls it.

Self-hosting? Use your instance's public HTTPS address instead of https://cloud.anythingmcp.com. Copilot Studio connects from Microsoft's cloud, so localhost does not work.

Available tools

Example prompts

• "Check the counterparty with INN 7707083893: status, director, founders, tax debts and risk factors."
• "How reliable is the company with OGRN 1027700132195? Show its reliability score, revenue and net profit for the last three years."
• "List the arbitration cases where this company is the defendant and any enforcement proceedings opened against it."
• "Which public procurement contracts under 44-FZ has this supplier won this year, and for how much?"
• "Which other companies does the director of INN 7707083893 run or co-own?"

FAQ

Which Copilot is this for? Microsoft 365 Copilot at work, through agents built in Copilot Studio. The Microsoft Copilot app for personal accounts has no option to add your own MCP server.

What do I need? A work account with access to Copilot Studio (a license or a trial) to build the agent. People who use it in Microsoft 365 Copilot or Teams need access to the agent: share it with them, or ask an admin to publish it to the organization. If your organization applies data policies to Power Platform connectors, they cover MCP servers too.

The agent doesn't call the tools. Check that the header name is exactly X-API-Key and that the key belongs to the same MCP server as the URL, and make the server description specific: Copilot Studio uses it to decide when to call the server. Publish the agent again after each change; in an open chat, type "start over" to get the new version.

Next steps

• Connector landing page
• Connect to Claude
• Connect to ChatGPT
• Connect to Cursor
• Connect to Gemini
• Connect to Meta Muse