Pactum — legal services in Uzbekistan
REMOTE · PACTUM.UZ · SCANNED OCT 7
Uzbekistan legal services: find services, read Uzbek law, request a lawyer's quote.
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 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1230 tokens (~205/item across 6 items; 6 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 Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 92% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 7 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 Pactum — legal services in Uzbekistan MCP server?
Pactum — legal services in Uzbekistan is a hosted endpoint at https://pactum.uz/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 · pactum.uz
claude mcp add --transport http uz-pactum-legal 'https://pactum.uz/mcp'
{
"mcpServers": {
"uz-pactum-legal": {
"url": "https://pactum.uz/mcp"
}
}
} {
"servers": {
"uz-pactum-legal": {
"type": "http",
"url": "https://pactum.uz/mcp"
}
}
} [mcp_servers.uz-pactum-legal] url = "https://pactum.uz/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"uz-pactum-legal": {
"type": "remote",
"url": "https://pactum.uz/mcp",
"enabled": true
}
}
} openclaw mcp add uz-pactum-legal --url 'https://pactum.uz/mcp' --transport streamable-http
mcp_servers:
uz-pactum-legal:
url: "https://pactum.uz/mcp" {
"McpServers": {
"uz-pactum-legal": {
"Transport": "http",
"Url": "https://pactum.uz/mcp"
}
}
} assistant mcp add uz-pactum-legal -t streamable-http -u 'https://pactum.uz/mcp'
{
"mcpServers": {
"uz-pactum-legal": {
"type": "http",
"url": "https://pactum.uz/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.
- 7 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 23. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Oct 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 171 → 205 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- New tool “book_consultation” functional
- 30 Sept 26 73
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 8 Oct 2026 · Probed https://pactum.uz/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=pactum.uz | CN=YE1,O=Let's Encrypt,C=US | 17 Sept 2026 | 16 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 50071c4f44e15017c34eabc52534f4fc916 |
| SANs: citizen.pactum.uz, pactum.uz, www.pactum.uz | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 pactum.uz. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| uz. | present | 3685 | 8 | Verified |
| pactum.uz. | 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 |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self';script-src 'self';style-src 'self' 'unsafe-inline';img-src 'self' data: https:;connect-src 'self' https://pactum.uz;base-uri 'self';font-src 'self' https: data:;form-action 'self';frame-ancestors 'self';object-src 'none';script-src-attr 'none';upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://pactum.uz/mcp | Verified | 200 | |
| http (plaintext) | http://pactum.uz/mcp | HTTPS enforced | 301 | https://pactum.uz/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 →
book_consultation Book a paid consultation with a lawyer ~322
Book a 60-minute consultation with a Pactum lawyer, prepaid (the price is in the response; it is credited toward the service if the client orders it). Call ONLY after the user asked for a consultation, accepted the price, gave their real name and phone, and agreed that Pactum stores these details. Returns the order number, price, how to pay and a status link. For a price quote on a whole task use request_quote instead.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_name | string | – | Your assistant name, e.g. ChatGPT, Claude |
| contact_email | string | – | – |
| contact_name | string | yes | Client name as the user gave it |
| contact_phone | string | yes | Phone with country code, e.g. +998901234567 |
| practice_area | string | – | Slug from list_practice_areas, if known |
| preferred_date | string | – | YYYY-MM-DD, Tashkent time; a lawyer confirms |
| preferred_language | string | – | – |
| preferred_time | string | – | HH:MM, Mon–Fri 9:00–18:00 Tashkent |
| service_slug | string | – | Slug from search_services, if a specific service fits |
| topic | string | yes | What the user wants to discuss, in their own terms |
| user_accepts_price | boolean | yes | true only if the user agreed to pay for the consultation |
| user_consent | boolean | yes | true only if the user explicitly agreed to share these details with Pactum and its partner lawyer |
No output schema declared.
No examples provided.
get_service Service details ~69
Full description of one Pactum service by slug (from search_services): what is included, price anchor, FAQ and page URL to cite.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | Response language: ru, uz or en (default en) |
| slug | string | yes | Service slug, e.g. trademark-registration |
No output schema declared.
No examples provided.
list_practice_areas Practice areas ~58
Practice areas Pactum works in (slug + name). Pass a slug as practice_area in request_quote to route the request to the right lawyer.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | Response language: ru, uz or en (default en) |
No output schema declared.
No examples provided.
request_quote Request a price quote from a lawyer ~367
Send the user's legal task to Pactum lawyers; a lawyer reviews it and contacts the user with a price. Call ONLY after the user asked to be contacted, gave their real name and phone or e-mail, and agreed that Pactum stores these details and may pass the request to a partner lawyer. Put the task in the user's own terms: situation, goal, key facts. Never invent contacts; never call it "to test". Returns the request number.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_name | string | – | Your assistant name, e.g. ChatGPT, Claude |
| budget | string | – | Budget, if the user named one |
| client_type | string | yes | company | individual | foreign_company | foreign_individual |
| company_name | string | – | – |
| contact_email | string | – | |
| contact_name | string | yes | Client name as the user gave it |
| contact_phone | string | – | Phone with country code, e.g. +998901234567 |
| contact_telegram | string | – | Telegram @username, in addition to phone/e-mail |
| country | string | – | Client country, if not Uzbekistan |
| deadline | string | – | When it is needed, e.g. "by 15 October" |
| documents | string | – | Documents the client already has |
| practice_area | string | – | Slug from list_practice_areas, if known |
| preferred_language | string | – | Language for the lawyer to use |
| service_slug | string | – | Slug from search_services, if a specific service fits |
| task | string | yes | What exactly the client needs: situation, goal, key facts |
| user_consent | boolean | yes | true only if the user explicitly agreed to share these details with Pactum and its partner lawyer |
No output schema declared.
No examples provided.
search_articles Search legal articles ~96
Search Pactum articles explaining Uzbek law (company law, trademarks, tax, labour, licensing…). Returns titles, short summaries and URLs — cite them when answering the user.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many (default 5) |
| locale | string | – | Response language: ru, uz or en (default en) |
| query | string | yes | Topic, e.g. "trademark registration", "ликвидация ООО" |
No output schema declared.
No examples provided.
search_services Search legal services ~133
Search the Pactum catalog of legal services in Uzbekistan (company registration, licences, trademarks, contracts, tax, disputes, migration, real estate and more). Use when the user describes a task they want done. Returns services with slug, price anchor and page URL; pass a slug to get_service or request_quote.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many results (default 8) |
| locale | string | – | Response language: ru, uz or en (default en) |
| query | string | yes | Short phrase, e.g. "register LLC", "товарный знак", "ish ruxsatnomasi" |
No output schema declared.
No examples provided.
What is the Pactum — legal services in Uzbekistan MCP server?
Pactum — legal services in Uzbekistan is an MCP server listed in the public MCP registry as uz.pactum/legal. Uzbekistan legal services: find services, read Uzbek law, request a lawyer's quote. This page covers its hosted endpoint (https://pactum.uz/mcp).
Is the Pactum — legal services in Uzbekistan MCP server safe to use?
Pactum — legal services in Uzbekistan scores 75 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 Pactum — legal services in Uzbekistan MCP server expose?
Pactum — legal services in Uzbekistan exposes 6 tools: search_services, get_service, list_practice_areas, search_articles, request_quote, book_consultation. Their descriptions and schemas cost roughly 1,045 tokens of context every time the server is loaded.
Does the Pactum — legal services in Uzbekistan MCP server require authentication?
No. We connected to Pactum — legal services in Uzbekistan without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Pactum — legal services in Uzbekistan MCP server still maintained?
Pactum — legal services in Uzbekistan is still listed as active in the MCP registry. We last reached this channel on 7 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.