_ registry / mcp http-sse · checked 34m ago

czid-mcp

https://czid.casuyi.com

Registry code: c1e76cbd5a05d4b3

api record

Czech ARES company registry: VAT, insolvency, RÚIAN addresses, IČO/DIČ checks. All free, no auth.

from a public catalogue that lists it, not from the operator

endpoint
https://czid.casuyi.com/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is czid-mcp live?
Yes — it answered the hub's last check (checked 34m ago). It answered 100% of checks over the last 30 days.
Is czid-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does czid-mcp have?
6 tools: validate_cz, check_vat, entity_status, address_check, search_company, company_lookup.
Is czid-mcp safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
300ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 279 checks · signed record
  • degraded → live
  • unknown → live
_ what it is for
topic
government & legal public records & government
used for
  • look up a czech company by ico
  • check czech vat payer status
  • standardize a czech address
  • validate ico dic or iban
takes → gives
text → data
tools
6 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 6 tools
6 never probed 0 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • validate_cz reads unknown never probed

    Checksum/format validation: IČO (mod-11), DIČ (CZ+IČO or birth number), IBAN (mod-97, CZ-specific), variable symbol. Pure local, no network.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "dic": {
      "type": "string"
    },
    "ico": {
      "type": "string"
    },
    "iban": {
      "type": "string"
    },
    "variableSymbol": {
      "type": "string"
    }
  }
}
    arguments 18 lines
  • check_vat reads unknown 34m ago

    Authoritative plátce-DPH status from RZP register: payer yes/no, effective from, tax office, trade licences. Use before issuing/czech invoicing. Batch up to 20 IČOs.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "ids"
  ],
  "properties": {
    "ids": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "maxItems": 20,
      "minItems": 1,
      "description": "IČOs or DIČs (CZ+10)"
    }
  }
}
    arguments 18 lines
  • entity_status reads unknown 18h ago

    KYC-style snapshot: active/cancelled, which registers the entity appears in (VR, RZP, NRPZS, RS insolvency, RCNS, SZR...), plus insolvency-register record if present.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "IČO or DIČ"
    }
  }
}
    arguments 13 lines
  • address_check reads unknown never probed

    Free-text Czech address -> RÚIAN-standardized (full KOD ADM, codes for obec/část/ulice, correct PSC).

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "address"
  ],
  "properties": {
    "address": {
      "type": "string",
      "minLength": 3,
      "description": "e.g. \"Václavské náměstí 1, Praha\""
    }
  }
}
    arguments 14 lines
  • search_company reads unknown 34m ago

    Company-name search in ARES (prefix match, case-insensitive; no wildcards). Returns IČOs + names + addresses for further lookups.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "minLength": 2,
      "description": "Company name or name prefix (e.g. \"Alza\")"
    },
    "limit": {
      "type": "integer",
      "maximum": 50,
      "minimum": 1,
      "description": "Max results (default 10)"
    }
  }
}
    arguments 20 lines
  • company_lookup reads unknown 34m ago

    Basic register (ARES) lookup: name, legal form, registered address, NACE, data-box, VAT DIČ. Input: IČO (8 digits) or DIČ (CZ+10).

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "IČO (e.g. 27082440) or DIČ (e.g. CZ27082440)"
    }
  }
}
    arguments 13 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id c1e76cbd5a05d4b3.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/c1e76cbd5a05d4b3/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/c1e76cbd5a05d4b3/badge.svg)](https://brick.blue/agent/c1e76cbd5a05d4b3?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on casuyi.com 1 entry

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.