# Rejstřík AI (remote · rejstrik.ai)

Czech company registry: search, profiles, relationships, status and evidence by ICO.

- Trust score: 78/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `rejstrik.ai`: 78/100 (this document), [markdown](https://verifymcp.io/servers/ai-rejstrik-mcp/rejstrik.md), [page](https://verifymcp.io/servers/ai-rejstrik-mcp/rejstrik)

## Channel facts

- Endpoint: `https://rejstrik.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.3.31.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 85/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1368 tokens (~105/item across 13 items; 12 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).
  - Supports UI / widget rendering.

## Install

### How do I install the Rejstřík AI MCP server?

Rejstřík AI is a hosted endpoint at https://rejstrik.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http ai-rejstrik-mcp 'https://rejstrik.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-rejstrik-mcp": {
      "url": "https://rejstrik.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-rejstrik-mcp": {
      "type": "http",
      "url": "https://rejstrik.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-rejstrik-mcp]
url = "https://rejstrik.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-rejstrik-mcp": {
      "type": "remote",
      "url": "https://rejstrik.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-rejstrik-mcp --url 'https://rejstrik.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-rejstrik-mcp:
    url: "https://rejstrik.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-rejstrik-mcp": {
      "Transport": "http",
      "Url": "https://rejstrik.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-rejstrik-mcp -t streamable-http -u 'https://rejstrik.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ai-rejstrik-mcp": {
      "type": "http",
      "url": "https://rejstrik.ai/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 76, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-16 (score 75)

First indexed and scored.

## MCP tools (12)

### `check_company_status` (~89 tokens)

Check Company Status

Use this when checking a Czech company by its 8-digit IČO for registry status, insolvency, VAT reliability, officers, or disclosed shareholders. Public registries only; 1 credit. Do not use for natural-person screening, legal advice, or a trustworthiness verdict.

Input parameters:

- `ico` (string, required): Exactly eight digits of the Czech company ICO; malformed values return 400 before charge.

### `get_evidence` (~91 tokens)

Get Company Evidence

Use this when you need source evidence, acquisition times, or coverage for a Czech company by 8-digit IČO. Public registries; authorized audits may add financial evidence. 1 credit. Do not use missing evidence as proof of absence, screen natural persons, or give legal advice.

Input parameters:

- `ico` (string, required): Exactly eight digits of the Czech company ICO; malformed values return 400 before charge.

### `lookup_company` (~73 tokens)

Lookup Company

Use this when you need a full normalized profile of one Czech company by 8-digit IČO. Public registries only; 1 credit. Do not use for name search, natural-person screening, or legal advice.

Input parameters:

- `ico` (string, required): Company ICO. Use the same value as GET /companies/{ico}.

### `search_companies` (~158 tokens)

Search Companies

Use this when searching Czech companies by name, IČO, region, industry, year, or status with pagination. Public registries only; 1 credit per call. Do not use for a known 8-digit IČO profile, natural-person screening, or legal advice.

Input parameters:

- `active` (boolean): Optional active company filter.
- `cursor` (string): Opaque cursor returned by previous search results.
- `kraj` (string): Optional region slug or label filter.
- `limit` (integer): Result page size, max 100.
- `nace` (string): Optional NACE filter.
- `q` (string): Free-text search query from GET /companies?q=.
- `rok` (integer): Optional founding year filter.

### `search` (~95 tokens)

Search

Use this when finding Czech companies by name or 8-digit IČO before fetching one result. Public registries only; anonymous discovery is free, signed-in calls cost 1 credit. Do not use for natural-person screening or legal advice.

Input parameters:

- `limit` (integer): Requested result count; all keys are capped at 10 by this connector tool.
- `query` (string, required): Company name, ICO, or free-text company query.

### `fetch` (~93 tokens)

Fetch

Use this when reading one Czech company found by search using company:<8-digit IČO>; signed-in clients may also use its profile URL. Public registries only; anonymous preview is free, signed-in calls cost 1 credit. Do not use for natural-person screening or legal advice.

Input parameters:

- `id` (string, required): Result id from search, for example company:27074358, or a public profile URL containing an ICO.

### `get_relationships` (~145 tokens)

Get Relationships

Use this when exploring documented relationships of a Czech company by 8-digit IČO: depth 0 costs 1 credit; graph depth 1–3 costs 2/5/15 credits. Public registry links may be incomplete. Do not use to infer beneficial ownership, screen natural persons, or give legal advice.

Input parameters:

- `depth` (integer): 0 returns direct edges only; 1-3 returns a wider graph slice.
- `direction` (string): Traversal direction when depth is greater than 0.
- `edgeTypes` (string): Comma-separated edge types when depth is greater than 0.
- `ico` (string, required): Company ICO to inspect.

### `find_path` (~138 tokens)

Find Path

Use this when finding a documented graph path between Czech registry entities; company seeds use 8-digit IČO. Public registry data; depth-scaled cost is 2/5/15 credits. Do not use a path as proof of control, for natural-person screening, or for legal advice.

Input parameters:

- `from` (string, required): Start graph seed, e.g. 27074358 or person:jan-novak.
- `maxDepth` (integer): Maximum search depth, aligned with GET /graph/path.
- `to` (string, required): Target graph seed, e.g. 00001350 or person:petra-dvorakova.

### `list_top_in_industry` (~110 tokens)

List Top In Industry

Use this when listing ranked Czech companies in a known industry slug. Company profiles use 8-digit IČO; public registry data; 1 credit per page. Do not use as a complete market census, natural-person screening, or legal advice.

Input parameters:

- `cursor` (string): Opaque cursor returned by previous results.
- `limit` (integer): Page size, max 100.
- `slug` (string, required): Industry slug from GET /industries or /industries/{slug}/companies.

### `get_changes` (~134 tokens)

Get Changes

Use this when reading changes for Czech companies on your own watchlist, optionally filtered by 8-digit IČO. Registry-derived records; 1 credit per call. Do not use for another account’s watchlist, natural-person screening, or legal advice.

Input parameters:

- `cursor` (string): Opaque cursor returned by previous get_changes responses.
- `ico` (string): Optional single ICO or comma-separated ICO filter within your own watchlist.
- `limit` (integer): Page size, max 200.
- `since` (string, required): RFC3339 timestamp for incremental polling.
- `type` (string): Optional change type filter.

### `screen_companies_by_thesis` (~111 tokens)

Screen Companies By Thesis

Use this when screening Czech companies against an investment, supplier, compliance, or sales thesis. Public registry data and 8-digit IČO identifiers; 1 credit. Do not use rankings as due diligence, for natural-person screening, or for legal advice.

Input parameters:

- `limit` (integer): Maximum number of ranked companies.
- `thesis` (string, required): Plain-language thesis, e.g. "stable Prague software companies with audited financials".
- `useCase` (string): Contextual scoring profile.

### `score_company_for_use_case` (~104 tokens)

Score Company For Use Case

Use this when scoring one Czech company by 8-digit IČO for a stated use case and reading documented finance or sector signals. Registry sources and authorized audit data when available; 1 credit. Do not use as a credit decision, natural-person screening, or legal advice.

Input parameters:

- `ico` (string, required): Company ICO to score.
- `thesis` (string): Optional thesis to score against the company.
- `useCase` (string): Contextual scoring profile.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-rejstrik-mcp/rejstrik#diagnostics

## Score history

- 2026-11-21: 78
- 2026-11-20: 77
- 2026-11-19: 77
- 2026-11-18: 76
- 2026-11-17: 76
- 2026-11-16: 75

## Common questions

### What is the Rejstřík AI MCP server?

Rejstřík AI is an MCP server listed in the public MCP registry as ai.rejstrik/mcp. Czech company registry: search, profiles, relationships, status and evidence by ICO. This page covers its hosted endpoint (https://rejstrik.ai/mcp).

### Is the Rejstřík AI MCP server safe to use?

Rejstřík AI scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Rejstřík AI MCP server expose?

Rejstřík AI exposes 12 tools: check_company_status, get_evidence, lookup_company, search_companies, search, and 7 more. Their descriptions and schemas cost roughly 1,341 tokens of context every time the server is loaded.

### Does the Rejstřík AI MCP server require authentication?

No. We connected to Rejstřík AI without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Rejstřík AI MCP server still maintained?

Rejstřík AI is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Rejstřík AI MCP server?

VerifyMCP ran 14 checks on Rejstřík AI, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://rejstrik.ai/mcp
- Authorisation metadata: https://rejstrik.ai/.well-known/oauth-protected-resource/mcp
- Website: https://rejstrik.ai/developers/mcp
- Changelog RSS feed: https://verifymcp.io/servers/ai-rejstrik-mcp/rejstrik.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-rejstrik-mcp/rejstrik/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/ai-rejstrik-mcp/rejstrik.json
- HTML version of this page: https://verifymcp.io/servers/ai-rejstrik-mcp/rejstrik
