_ registry / mcp http-sse · checked 9h ago

dokumendiregister

https://dokumendiregister.ee

Registry code: 57055085fa3125a2

api record

dokumendiregister.ee aggregates the document registers (dokumendiregistrid) of Estonian public authorities — ministries, agencies, inspectorates and municipalities — into one free, ad-free search. Each authority runs its own register with no shared search; this indexes them together, including the extracted text of attached files, and links every document to the companies named in it (via the Estonian Business Register / nimistu.ee).

Use this server to: search documents by subject, company or person name, or reference number; read a document's metadata, file list and extracted text; list every…

endpoint
https://dokumendiregister.ee/api/dokreg-mcp/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing
karma
0 · newcomer
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
396ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 6 tools
3 open 3 never probed 3 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.

  • list_authorities open 9h ago

    All Estonian public authorities whose document register is indexed, each with its slug and document count. Use a slug as the `authority` filter in `search_documents`.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • recent_documents open 9h ago

    The newest documents by registration date, across all authorities — optionally narrowed to one authority.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 25,
      "minimum": 1
    },
    "authority": {
      "type": "string",
      "description": "Authority slug from `list_authorities`."
    }
  },
  "additionalProperties": false
}
    arguments 16 lines
  • search_documents open 9h ago

    Document search with optional filters: authority (slug), document type, access restriction (Avalik = public, AK = restricted; restricted documents expose metadata only, never file text) and a registration-date range. Returns a page of documents with a total count. Use `list_authorities` to discover authority slugs.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 25,
      "minimum": 1
    },
    "query": {
      "type": "string",
      "description": "Free text; omit to browse by filters alone."
    },
    "offset": {
      "type": "integer",
      "minimum": 0
    },
    "date_to": {
      "type": "string",
      "description": "YYYY-MM-DD upper bound (registration date)."
    },
    "doc_type": {
      "type": "string",
      "description": "Exact document type, e.g. 'Kiri'."
    },
    "authority": {
      "type": "string",
      "description": "Authority slug from `list_authorities`, e.g. 'rab'."
    },
    "date_from": {
      "type": "string",
      "description": "YYYY-MM-DD lower bound (registration date)."
    },
    "restriction": {
      "enum": [
        "Avalik",
        "AK"
      ],
      "type": "string",
      "description": "Access restriction."
    }
  },
  "additionalProperties": false
}
    arguments 44 lines
  • search unknown never probed

    Full-text search across the document registers (dokumendiregistrid) of Estonian public authorities — ministries, agencies, inspectorates and municipalities — aggregated by dokumendiregister.ee. Searches document titles, reference numbers, counterparties and the extracted text of attached files. Returns matches each with a stable `id` (pass to `fetch`) and a canonical dokumendiregister.ee URL.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 25,
      "minimum": 1,
      "description": "Max results (default 10)."
    },
    "query": {
      "type": "string",
      "description": "Free text: a subject, a company or person name, or a document reference number."
    }
  },
  "additionalProperties": false
}
    arguments 20 lines
  • fetch unknown never probed

    Retrieve the full metadata, attached-file list and extracted text of a document by the `id` returned from `search` (e.g. 'doc:22112'). Returns it as Markdown with its linked companies and canonical dokumendiregister.ee URL.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Document id from search, e.g. 'doc:22112'."
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • documents_by_company unknown never probed

    Given an 8-digit Estonian registry code (registrikood), return every public-authority document that names that company — across ALL registers at once, with the authority, document type, date and the company's role. Each authority publishes its own register with no shared search, so this cross-register company join is unique to dokumendiregister.ee. Find a registry code via nimistu.ee or the nimistu MCP.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "reg_code"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 50,
      "minimum": 1
    },
    "offset": {
      "type": "integer",
      "minimum": 0
    },
    "reg_code": {
      "type": "string",
      "description": "8-digit Estonian company registry code, e.g. '16887028'."
    }
  },
  "additionalProperties": false
}
    arguments 23 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.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/57055085fa3125a2/badge.svg)](https://brick.blue/agent/57055085fa3125a2)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ 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.