Tvarka Due Diligence provides Lithuanian company data and role-holder identification through an authenticated MCP endpoint and REST API. Look up company profiles and management, shareholders, declared beneficial owners, real property, property-seizure acts and court cases, or request a composite report. Beneficial-ownership requests require a stated purpose. Supported tools can add attorney-authored, versioned legal interpretation with statute citations. Answers are provided as a legal service by a Lithuanian attorney-at-law; supported response formats include signed attestations. Identification packages match a role-holder’s qualified electronic signature against register data. create_kyc_package returns an order ID and ceremony URL; get_kyc_package reports progress and the outcome. Delivered packages contain an ASiC-E evidence container. This service does not perform document-image identity verification, facial matching, liveness checks or sanctions/PEP screening. Active sandbox keys return synthetic data at no cost, without an agreement or billing entity. Request a key at [email protected]. Production requires accepted terms at https://api.tvarka.pro/terms and a signed engagement agreement; missing legal prerequisites return 403. Production also requires a linked billable Tvarka entity with an enrolled payment method, a funded prepaid balance or individually agreed terms. Missing or blocked billing returns 402. Suspended keys, including sandbox keys, also return 402. Read the problem detail instead of retrying in a loop. Billing is per answered call; no-data answers and upstream source failures are not billed. Identification packages are billed only on delivery. Sandbox simulation tests outcomes without producing a real qualified signature or production evidence container. Documentation: https://api.tvarka.pro/docs Contact: [email protected]

MCP readiness

B · 84/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 70.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake	10/10	initialize and tools/list both answered.
Live MCP endpoint	24/25	Endpoint answers the MCP initialize handshake (4517 ms); slow response -1.
Protocol revision	6/10	Speaks MCP 2025-06-18, 2 revision(s) behind 2026-07-28.
Signed descriptor	n/a	No MCP standard defines a signed server descriptor.
Uptime (30 days)	14.5/15	29/30 probes succeeded over 30 days (97%).
Tool declaration	10/10	Lists 10 tool(s) with descriptions.
Verified identity	5/10	Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags	4/5	seen in a source within 7 days.
Auth declaration	2/5	Declares credential scheme: smithery_api_key.

Applicable criteria total 90 points, scaled to 100.

Responsiveness: Slow (4517 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).

Measured 2026-11-11.

Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness: Higher than 73% of peers; This listing 84 · peer median 81
Latency: Faster than 6% of peers; This listing 1,107 ms · peer median 326 ms

Where it loses the most points, and how to win them back

Verified identity −5 — Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Protocol revision −4 — Support the current protocol revision.
Now: Speaks MCP 2025-06-18, 2 revision(s) behind 2026-07-28.
Auth declaration −3 — State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

smithery since 2026-08-11 ↗

How to connect

MCP endpoint (streamable-http)

https://server.smithery.ai/tvarka/due-diligence/mcp

JSON-RPC initialize probe

curl -X POST https://server.smithery.ai/tvarka/due-diligence/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

Homepage

https://api.tvarka.pro/docs

Listed at (smithery)

https://api.tvarka.pro/docs