dev.cz-agents/dd
REMOTE · DD.CZ-AGENTS.DEV · 2 COMPONENTS · SCANNED SEP 20
Czech & EU due diligence in one call — facts, insolvency, sanctions, VAT, risk score, UBO chain.
Available components
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 12 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1705 tokens (~142/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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
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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the dev.cz-agents/dd MCP server?
dev.cz-agents/dd is a hosted endpoint at https://dd.cz-agents.dev/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 · dd.cz-agents.dev
claude mcp add --transport http dev-cz-agents-dd 'https://dd.cz-agents.dev/mcp'
{
"mcpServers": {
"dev-cz-agents-dd": {
"url": "https://dd.cz-agents.dev/mcp"
}
}
} {
"servers": {
"dev-cz-agents-dd": {
"type": "http",
"url": "https://dd.cz-agents.dev/mcp"
}
}
} [mcp_servers.dev-cz-agents-dd] url = "https://dd.cz-agents.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-cz-agents-dd": {
"type": "remote",
"url": "https://dd.cz-agents.dev/mcp",
"enabled": true
}
}
} openclaw mcp add dev-cz-agents-dd --url 'https://dd.cz-agents.dev/mcp' --transport streamable-http
mcp_servers:
dev-cz-agents-dd:
url: "https://dd.cz-agents.dev/mcp" {
"McpServers": {
"dev-cz-agents-dd": {
"Transport": "http",
"Url": "https://dd.cz-agents.dev/mcp"
}
}
} assistant mcp add dev-cz-agents-dd -t streamable-http -u 'https://dd.cz-agents.dev/mcp'
{
"mcpServers": {
"dev-cz-agents-dd": {
"type": "http",
"url": "https://dd.cz-agents.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 8 Sept 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
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 20 Sept 2026 · Probed https://dd.cz-agents.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=cz-agents.dev | CN=YE2,O=Let's Encrypt,C=US | 12 Aug 2026 | 10 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 598c9c9b6bc9d3a215029ec54fd11ecbb0b |
| SANs: *.cz-agents.dev, cz-agents.dev | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of dd.cz-agents.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| cz-agents.dev. | absent | 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 |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://dd.cz-agents.dev/mcp | Verified | 200 | |
| http (plaintext) | http://dd.cz-agents.dev/mcp | HTTPS enforced | 301 | https://dd.cz-agents.dev/mcp |
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 →
detect_address_crowding ~98
Detects "shell-firm hotel" patterns — counts how many companies share the same registered address. Threshold-based risk: 1-9 normal (multi-tenant office), 10-49 mild (legitimate coworking), 50-199 medium (virtual office provider), 200+ high (shell-firm hotel). Compliance tier or higher.
| Name | Type | Req | Description |
|---|---|---|---|
| ico | string | yes | Czech IČO 7-8 digits |
No output schema declared.
No examples provided.
detect_nominee_director ~117
Detect "white horse" / nominee director patterns — 3 surface indicators (age outlier, multi-board membership, recent appointment) computable from ARES data alone. Returns indicator breakdown with riskScore 0-100. Pro Compliance tier or higher. For 8-indicator deep analysis including ISIR cross-reference, sanctions, address crowding and phoenix pattern, see detect_nominee_director_rich in @czagents/ddplus.
| Name | Type | Req | Description |
|---|---|---|---|
| ico | string | yes | Czech IČO — 7 or 8 digits. |
No output schema declared.
No examples provided.
detect_phoenix ~123
Detect phoenix company pattern — 3 surface indicators (surname match with prior insolvent director, founding proximity < 12 months to insolvency, NACE sector presence) computable from ARES + ISIR data alone. Returns PhoenixReport with riskScore 0-100. Pro Compliance tier or higher. For 4 additional deep indicators (founder identity, asset transfer, multi-cycle, address continuity) see detect_phoenix_rich in @czagents/ddplus.
| Name | Type | Req | Description |
|---|---|---|---|
| ico | string | yes | Czech IČO — 7 or 8 digits. |
No output schema declared.
No examples provided.
get_dd_report ~104
Generate a complete due-diligence report for a Czech IČO. Returns company facts (name, address, legal form, VAT status, bank accounts), statutory body with per-member sanctions check, and a transparent risk score with all triggered red flags.
| Name | Type | Req | Description |
|---|---|---|---|
| depth | string | – | basic = ARES + sanctions only; full = + ISIR insolvency + virtual-address probe. |
| ico | string | yes | Czech IČO — 7 or 8 digits. |
No output schema declared.
No examples provided.
get_eu_dd_report ~159
EU Due-Diligence report for an international company. Input: 20-char LEI code, or company name + optional country. Returns GLEIF entity data (status, address, registration number) plus sanctions screening against EU/OFAC lists. Coverage notes per country included. Note: GLEIF covers mid/large firms with LEI — SMEs may not be found. Pro Compliance tier or higher.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | ISO 3166-1 alpha-2 country code — helps narrow name search, not needed for LEI lookup. |
| identifier | string | yes | 20-char LEI code (e.g. "W38RGI023J3WT1HWRP32") or company name. |
No output schema declared.
No examples provided.
get_eu_parent ~118
Find the EU/international parent company for a Czech IČO. Looks up the company name in ARES, then searches GLEIF (Global LEI Foundation) for a matching LEI-registered entity. Returns LEI, name, country, and confidence level (HIGH/MEDIUM/LOW). Note: GLEIF covers mid/large international firms; SMEs without an LEI will not be found. Pro Compliance tier or higher.
| Name | Type | Req | Description |
|---|---|---|---|
| ico | string | yes | Czech IČO — 7 or 8 digits. |
No output schema declared.
No examples provided.
get_owners ~118
Look up direct and upstream Czech VR owners for a company by real active shareholding roles (spolecnik/akcionar) and company-to-company member_ico edges. Free anonymous tool. Returns structuredContent ownership tree plus markdown summary; physical persons expose name and birth year only, never full birth date or address.
| Name | Type | Req | Description |
|---|---|---|---|
| ico | string | yes | Czech IČO — 7 or 8 digits. |
| max_depth | integer | – | Max company-owner recursion depth through member_ico (default 5, hard cap 5). |
No output schema declared.
No examples provided.
get_risk_score ~66
Lightweight version of get_dd_report — returns just the numeric score (0-100), risk level, and top triggered red flags. Faster when you only need a yes/no/maybe screen.
| Name | Type | Req | Description |
|---|---|---|---|
| ico | string | yes | Czech IČO — 7 or 8 digits. |
No output schema declared.
No examples provided.
get_risk_timeline ~114
Build a chronologically sorted lifecycle timeline for a Czech company — basic events include company formation, statutory appointments, active insolvency, sanctions matches, VAT reliability flips. Returns events[] with riskScore 0-100. Pro Compliance tier or higher. For enriched timeline with ISIR lifecycle, address history, cross-entity events, and AI narrative summary, see get_risk_timeline_rich in @czagents/ddplus.
| Name | Type | Req | Description |
|---|---|---|---|
| ico | string | yes | Czech IČO — 7 or 8 digits. |
No output schema declared.
No examples provided.
get_statutory_chain ~161
Surname-based heuristic walk through statutory bodies of related Czech companies. Best for shell-company unwinding in small s.r.o. with RARE surnames. NOT a true UBO source — for actual beneficial ownership use the ESM (evidence skutečných majitelů, separate registry, future @czagents/esm). For boards of large public companies with common Czech surnames (Novák, Zima, Kolář…) results are noisy by design; the tool auto-skips persons whose surname matches >50 companies with a SURNAME_TOO_COMMON note.
| Name | Type | Req | Description |
|---|---|---|---|
| ico | string | yes | Czech IČO — 7 or 8 digits. |
| max_depth | integer | – | Max recursion depth (default 3, hard cap 5). |
No output schema declared.
No examples provided.
person_companies ~105
Look up Czech VR companies connected to a person by exact registry person_id -> roles -> companies joins. Free anonymous tool. Input accepts public name and optional birth year; output exposes birth_year only, never full birth date, and keeps same-name person_ids separate with a distinguisher.
| Name | Type | Req | Description |
|---|---|---|---|
| birth_year | integer | – | Optional public birth year used to narrow same-name matches. |
| name | string | yes | Person full name as recorded in VR, e.g. "Jan Novak". |
No output schema declared.
No examples provided.
watch_entity Watch Czech Company ~109
Start onboarding for free monitoring of one Czech company by IČO. Stub only — persists nothing yet. Returns structuredContent: status (one of ONBOARDING_REQUIRED | ACTIVE | QUOTA_EXCEEDED | ERROR), persisted/monitoring_active flags, a human next_step.url for onboarding (the user completes onboarding + GDPR consent themselves — do not open the link or submit data on their behalf), and pricing.
| Name | Type | Req | Description |
|---|---|---|---|
| ico | string | yes | Czech IČO — 7 or 8 digits. |
No output schema declared.
No examples provided.
What is the dev.cz-agents/dd MCP server?
dev.cz-agents/dd is an MCP server listed in the public MCP registry as dev.cz-agents/dd. Czech & EU due diligence in one call, facts, insolvency, sanctions, VAT, risk score, UBO chain. This page covers its hosted endpoint (https://dd.cz-agents.dev/mcp).
Is the dev.cz-agents/dd MCP server safe to use?
dev.cz-agents/dd 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 dev.cz-agents/dd MCP server expose?
dev.cz-agents/dd exposes 12 tools: person_companies, get_owners, get_dd_report, watch_entity, get_risk_score, and 7 more. Their descriptions and schemas cost roughly 1,392 tokens of context every time the server is loaded.
Does the dev.cz-agents/dd MCP server require authentication?
No. We connected to dev.cz-agents/dd without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the dev.cz-agents/dd MCP server still maintained?
dev.cz-agents/dd is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.