Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Rejstřík AI

REMOTE · REJSTRIK.AI

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

Available components

78 Trust /100

Last scanned (22 hours ago)

Scores higher than 71% of remote servers

Reachable. Last reached 21 Nov 2026.

Category CRM and Sales

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability85
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1368 tokens (~105/item across 13 items; 12 tools + 1 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
  • Supports UI / widget rendering.Pass
What we tested

Checks we ran (14)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol
  • Capabilities

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +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.

  • 19 Nov 26 +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.

  • 17 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 16 Nov 26 75

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://rejstrik.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=rejstrik.ai CN=WE1,O=Google Trust Services,C=US 5 Oct 2026 3 Jan 2027 ECDSA 256 ECDSA-SHA256 3d3a7844316bbf0d0e71a5f24b594f78
SANs: rejstrik.ai, *.rejstrik.ai
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of rejstrik.ai. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ai. DS published 1814 8 Verified
rejstrik.ai. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://rejstrik.ai/mcp Verified 200
http (plaintext) http://rejstrik.ai/mcp HTTPS enforced 301 https://rejstrik.ai/mcp
MCP tools · 12 exposed · ~1,341 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_company_status ~89

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.

NameTypeReqDescription
icostringyesExactly eight digits of the Czech company ICO; malformed values return 400 before charge.

Structured output declared, but exposes no named fields.

No examples provided.

fetch ~93

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.

NameTypeReqDescription
idstringyesResult id from search, for example company:27074358, or a public profile URL containing an ICO.

Structured output declared, but exposes no named fields.

No examples provided.

find_path ~138

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.

NameTypeReqDescription
fromstringyesStart graph seed, e.g. 27074358 or person:jan-novak.
maxDepthinteger–Maximum search depth, aligned with GET /graph/path.
tostringyesTarget graph seed, e.g. 00001350 or person:petra-dvorakova.

Structured output declared, but exposes no named fields.

No examples provided.

get_changes ~134

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.

NameTypeReqDescription
cursorstring–Opaque cursor returned by previous get_changes responses.
icostring–Optional single ICO or comma-separated ICO filter within your own watchlist.
limitinteger–Page size, max 200.
sincestringyesRFC3339 timestamp for incremental polling.
typestring–Optional change type filter.

Structured output declared, but exposes no named fields.

No examples provided.

get_evidence ~91

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.

NameTypeReqDescription
icostringyesExactly eight digits of the Czech company ICO; malformed values return 400 before charge.

Structured output declared, but exposes no named fields.

No examples provided.

get_relationships ~145

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.

NameTypeReqDescription
depthinteger–0 returns direct edges only; 1-3 returns a wider graph slice.
directionstring–Traversal direction when depth is greater than 0.
edgeTypesstring–Comma-separated edge types when depth is greater than 0.
icostringyesCompany ICO to inspect.

Structured output declared, but exposes no named fields.

No examples provided.

list_top_in_industry ~110

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.

NameTypeReqDescription
cursorstring–Opaque cursor returned by previous results.
limitinteger–Page size, max 100.
slugstringyesIndustry slug from GET /industries or /industries/{slug}/companies.

Structured output declared, but exposes no named fields.

No examples provided.

lookup_company ~73

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.

NameTypeReqDescription
icostringyesCompany ICO. Use the same value as GET /companies/{ico}.

Structured output declared, but exposes no named fields.

No examples provided.

score_company_for_use_case ~104

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.

NameTypeReqDescription
icostringyesCompany ICO to score.
thesisstring–Optional thesis to score against the company.
useCasestring–Contextual scoring profile.

Structured output declared, but exposes no named fields.

No examples provided.

screen_companies_by_thesis ~111

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.

NameTypeReqDescription
limitinteger–Maximum number of ranked companies.
thesisstringyesPlain-language thesis, e.g. "stable Prague software companies with audited financials".
useCasestring–Contextual scoring profile.

Structured output declared, but exposes no named fields.

No examples provided.

search ~95

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.

NameTypeReqDescription
limitinteger–Requested result count; all keys are capped at 10 by this connector tool.
querystringyesCompany name, ICO, or free-text company query.

Structured output declared, but exposes no named fields.

No examples provided.

search_companies ~158

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.

NameTypeReqDescription
activeboolean–Optional active company filter.
cursorstring–Opaque cursor returned by previous search results.
krajstring–Optional region slug or label filter.
limitinteger–Result page size, max 100.
nacestring–Optional NACE filter.
qstring–Free-text search query from GET /companies?q=.
rokinteger–Optional founding year filter.

Structured output declared, but exposes no named fields.

No examples provided.

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.

remote · rejstrik.ai

# add to Claude Code
claude mcp add --transport http ai-rejstrik-mcp 'https://rejstrik.ai/mcp'
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.