MCP Server

We provide an MCP (Model Context Protocol) server with prompts, resources and tools that you can use for building AI-applications. The server uses streamable HTTP transport providing real-time communication with Server-Sent Events (SSE) streaming support.

Getting Started

Our MCP server is located at https://mcp.tic.io. It accepts your TIC API key via either of two headers:

• x-api-key: <your_api_key> - same scheme as our REST API
• Authorization: Bearer <your_api_key> - for clients (such as the Anthropic Messages API connector) that only forward an OAuth-style bearer token

Either form authenticates the same way against the same key. Pick whichever your MCP client supports.

IP restrictions

Every request is checked against the calling IP address before the API key is looked up, as AbuseIPDB reports it. The MCP server accepts more countries than the LENS API, since AI platforms call from their own cloud regions, most of them in the US:

• Every country is accepted except China (CN), Taiwan (TW), Russia (RU), Brazil (BR), India (IN) and Iran (IR).
• An address with an abuse confidence score above 25 (of 100, from reports in the last 90 days) is refused, whatever its country.

A refused request gets 403 Forbidden with a plain-text body: Forbidden IP-address, contact support@tic.io. (abuse score) or Forbidden country, contact support@tic.io. (country). The answer for an address is cached for 7 days.

Example of using OpenAI Responses API

Full documentation for the OpenAI Responses API is available here.

Endpoint: https://api.openai.com/v1/responses

Note you need to include Bearer authentication for the OpenAI API. An example request body follows below.

{
  "model": "gpt-5",
  "input": [
    {
      "role": "developer",
      "content": [
        {
          "type": "input_text",
          "text": "Talk like a chief financial officer"
        }
      ]
    },
    {
      "role": "user",
      "content": [
        {
          "type": "input_text",
          "text": "Get company information for Bahnhof AB (publ)."
        }
      ]
    }
  ],
  "text": {
    "format": {
      "type": "text"
    },
    "verbosity": "medium"
  },
  "reasoning": {
    "effort": "medium",
    "summary": "auto"
  },
  "tools": [
    {
      "type": "mcp",
      "allowed_tools": [
        "get_company_by_registration_number",
        "get_company_by_name",
        "get_company_by_company_id",
        "get_companies_by_sni_code",
        "get_financial_reports",
        "get_annual_reports",
        "get_risk_and_intelligence",
        "get_credit_score",
        "get_company_risk_summary",
        "get_company_debt_cases",
        "get_company_penalties",
        "get_company_lansstyrelsen_decisions",
        "get_company_kammarkollegiet_sanctions",
        "get_company_tax_deferrals",
        "get_company_business_mortgages",
        "get_company_payroll_history",
        "get_company_share_structure",
        "get_company_address_history",
        "get_company_name_history",
        "get_company_vehicles",
        "get_company_bankruptcies"
      ],
      "headers": {
        "x-api-key": "your_api_key"
      },
      "require_approval": "never",
      "server_label": "TIC",
      "server_url": "https://mcp.tic.io"
    }
  ],
  "store": true,
  "include": ["reasoning.encrypted_content"]
}

Example of using Anthropic Messages API

Anthropic’s Messages API can call remote MCP servers directly through its MCP connector. Full documentation is available here.

Endpoint: https://api.anthropic.com/v1/messages

You need three headers on the request:

• x-api-key: <your_anthropic_api_key> - your Anthropic API key
• anthropic-version: 2023-06-01
• anthropic-beta: mcp-client-2025-11-20

The authorization_token field on the MCP server entry is forwarded by Anthropic to our server as Authorization: Bearer <token> - pass your TIC API key there. An example request body:

{
  "model": "claude-opus-5-5",
  "max_tokens": 1024,
  "messages": [
    {
      "role": "user",
      "content": "Get company information for Bahnhof AB (publ)."
    }
  ],
  "mcp_servers": [
    {
      "type": "url",
      "url": "https://mcp.tic.io",
      "name": "tic",
      "authorization_token": "your_tic_api_key"
    }
  ],
  "tools": [
    {
      "type": "mcp_toolset",
      "mcp_server_name": "tic"
    }
  ]
}

To restrict which TIC tools the model can see, use the mcp_toolset allowlist pattern - disable everything by default, then enable specific tools:

{
  "tools": [
    {
      "type": "mcp_toolset",
      "mcp_server_name": "tic",
      "default_config": { "enabled": false },
      "configs": {
        "get_company_by_registration_number": { "enabled": true },
        "get_company_risk_summary":            { "enabled": true },
        "get_company_debt_cases":              { "enabled": true },
        "get_company_penalties":               { "enabled": true }
      }
    }
  ]
}

Example of LibreChat configuration

If you wish to use our MCP in LibreChat you simply add a block inside mcpServers section in yaml configuration file:

mcpServers:
  tic:
    type: streamable-http
    url: https://mcp.tic.io
    headers:
      x-api-key: 'your_api_key'

Prompts

Prompts are user-invokable workflow templates that combine multiple tools into a single investigation flow with explicit framing and a named deliverable. Pick one from your MCP client’s prompt menu to kick off an end-to-end analysis.

Most prompts take registrationNumber (organisation number, e.g. 556519-9493) and resolve identity to the internal companyId as their first step. build_prospect_list is the exception - it starts from a free-text brief rather than a known company.

Resources

Resources are static reference data the model reads once into context - no tool call required. They decode the codes that appear in tool responses.

Tools

Functions the model invokes to retrieve company, property, or vehicle data. Tools are grouped below by purpose.

Company search & identity

Company financials & risk

Company enforcement & compliance

Company structure & history

Vehicles

Property

Prospecting & registers

search_companies_for_leads

The broadest tool on the server. It combines free-text matching against company name, business purpose (verksamhet) and SNI industry names with structured firmographic filters, and returns a paged lead list.

Size filters are bucketed: pass a number and it maps to the SCB band containing it. Sorting by turnover or employee count is not available, because the SCB size-class field is not sortable - filter on it instead.

search_lei

We will continuously add new tools - check back here for new additions.