Private Law Wiki
REMOTE · WIKI.PRIVATE.LAW · SCANNED SEP 21
Read-only answers and semantic search for wiki.private.law, served by the Mothership runtime.
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 Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 881 tokens (~176/item across 5 items; 5 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 Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 59% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Private Law Wiki MCP server?
Private Law Wiki is a hosted endpoint at https://wiki.private.law/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 · wiki.private.law
claude mcp add --transport http privatelawattorneys-wiki-private-law 'https://wiki.private.law/mcp'
{
"mcpServers": {
"privatelawattorneys-wiki-private-law": {
"url": "https://wiki.private.law/mcp"
}
}
} {
"servers": {
"privatelawattorneys-wiki-private-law": {
"type": "http",
"url": "https://wiki.private.law/mcp"
}
}
} [mcp_servers.privatelawattorneys-wiki-private-law] url = "https://wiki.private.law/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"privatelawattorneys-wiki-private-law": {
"type": "remote",
"url": "https://wiki.private.law/mcp",
"enabled": true
}
}
} openclaw mcp add privatelawattorneys-wiki-private-law --url 'https://wiki.private.law/mcp' --transport streamable-http
mcp_servers:
privatelawattorneys-wiki-private-law:
url: "https://wiki.private.law/mcp" {
"McpServers": {
"privatelawattorneys-wiki-private-law": {
"Transport": "http",
"Url": "https://wiki.private.law/mcp"
}
}
} assistant mcp add privatelawattorneys-wiki-private-law -t streamable-http -u 'https://wiki.private.law/mcp'
{
"mcpServers": {
"privatelawattorneys-wiki-private-law": {
"type": "http",
"url": "https://wiki.private.law/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.
- 18 Sept 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Tool coverage: 80% → 59% ▼ functional
- Schema quality: 198 → 176 ▲ functional
- New tool “assess_bank_case” functional
- New tool “bank_index” functional
- New tool “bank_rating” functional
- 11 Sept 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 174 → 198 ▼ functional
- Server version: 3.2.0 → 3.3.0 functional
- 8 Sept 26 +5
- Stability: fail → pass ▲ security
- 30 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67.
- 29 Aug 26 −1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 63.
- 28 Aug 26 −5
- Stability: pass → fail ▼ 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
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 21 Sept 2026 · Probed https://wiki.private.law/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=private.law | CN=YE1,O=Let's Encrypt,C=US | 11 Aug 2026 | 9 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 5a8c6dba4ca30c45f75c869e4aea1c7dad1 |
| SANs: *.private.law, private.law | ||||||
| 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 wiki.private.law. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| law. | present | 42496 | 8 | Verified |
| private.law. | 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'; base-uri 'self'; form-action 'self' https:; frame-ancestors 'none'; object-src 'none'; img-src 'self' data: blob: https:; font-src 'self' data: https:; style-src 'self' 'unsafe-inline' https:; script-src 'self' 'unsafe-inline' 'unsafe-eval' https:; connect-src 'self' https:; frame-src 'self' https:; upgrade-insecure-requests |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=(), browsing-topics=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://wiki.private.law/mcp | Verified | 200 | |
| http (plaintext) | http://wiki.private.law/mcp | HTTPS enforced | 301 | https://wiki.private.law/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 →
ask Ask the Private Law wiki ~133
Answer a question by quoting a published wiki article. The answer is extracted verbatim, never generated, and always carries the URL it came from. Returns confident=false with suggested reading when the corpus does not cover the question or when context genuinely conflicts. Bare MSO means the Hong Kong Money Service Operator licence; use Management Services Organization or regulated-practice context for the broader platform concept. Ask in the language you want answered — Russian and English are both first-class.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | Corpus language; inferred from the question when omitted. |
| question | string | yes | A natural-language question, up to 2000 characters. |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string|null | yes | – |
| citations | array | yes | – |
| confident | boolean | yes | – |
| locale | string | – | – |
| queryInterpretation | object|null | yes | – |
| refusalReason | string|null | – | – |
| suggestedReading | array | yes | – |
| threshold | number | – | – |
| topDistance | number|null | – | – |
No examples provided.
assess_bank_case Assess a problem with a bank ~152
The complaint desk's deterministic assessment for a frozen account, a closure notice, a document request, a stuck payment or a refused application: what to do now, the escalation ladder of the bank's jurisdiction (bank complaint, ombudsman or regulator, data access request), deadlines, cautions and the help that fits. Information, not legal advice. Never submit a person's contact details; hand them the complaint URL instead.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | – |
| jurisdiction | string | yes | Where the bank or the neobank's licence sits. |
| locale | string | – | – |
| problem | string | yes | – |
| sanctions | string | yes | Russia or Belarus nexus of the client. |
| stage | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| articles | array | yes | – |
| cautions | array | yes | – |
| complaintUrl | string | yes | – |
| deadlines | array | yes | – |
| escalation | array | yes | – |
| firstSteps | array | yes | – |
| headline | string | yes | – |
| service | object | yes | – |
No examples provided.
bank_index The private.law Bank Index ~178
List providers of banking for international clients with their standing in the Bank Index: a ranking per product (business account, private banking, personal account, digital assets, payments and FX, banking infrastructure, trade finance), tier, composite score 0–100, data coverage and watch flag. Filter by product, tier or a standardised client profile; without a product each provider shows its best standing. Scores are computed from dated, sourced data points; unrated providers are listed too. Use bank_rating for one provider with its evidence.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Default 25. |
| locale | string | – | – |
| product | string | – | Rank under this product; a provider appears in every product it offers. |
| profile | string | – | Only providers whose verdict for this profile is yes or case-by-case. |
| tier | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| generatedAt | string | yes | – |
| method | string | yes | – |
| providers | array | yes | – |
| total | integer | yes | – |
No examples provided.
bank_rating One provider in the Bank Index, with evidence ~88
Return one provider's full record: its standing under every product it offers (tier, composite, coverage), pillar scores, every indicator value with its source, date and verification level, the standardised profile verdicts, flags and a provenance object with a ready citation. Also returns the complaint-desk URL for that provider.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The provider card slug, e.g. mercury. |
| Name | Type | Req | Description |
|---|---|---|---|
| complaint | object | yes | – |
| composite | integer|null | yes | – |
| coverage | number | yes | – |
| flags | array | yes | – |
| headline | object|null | yes | – |
| indicators | object | yes | – |
| pillars | object | yes | – |
| products | array | yes | – |
| profiles | object | yes | – |
| provenance | object | yes | – |
| review | object | yes | – |
| slug | string | yes | – |
| standings | object | yes | – |
| tier | string | yes | – |
| watch | boolean | yes | – |
No examples provided.
search Search the Private Law wiki ~104
Rank published articles for a query and return them with titles and URLs. Use when you want sources to read rather than a single answer. Search is sense-aware: bare MSO promotes only the Hong Kong Money Service Operator owner, professional-industry context promotes the regulated-practice platform, and genuinely conflicting context returns both with an explicit interpretation object.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Default 5. |
| locale | string | – | – |
| query | string | yes | Search terms or a question. |
| Name | Type | Req | Description |
|---|---|---|---|
| hits | array | yes | – |
| queryInterpretation | object|null | yes | – |
No examples provided.
What is the Private Law Wiki MCP server?
Private Law Wiki is an MCP server listed in the public MCP registry as io.github.privatelawattorneys/wiki-private-law. Read-only answers and semantic search for wiki.private.law, served by the Mothership runtime. This page covers its hosted endpoint (https://wiki.private.law/mcp).
Is the Private Law Wiki MCP server safe to use?
Private Law Wiki scores 86 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 Private Law Wiki MCP server expose?
Private Law Wiki exposes 5 tools: ask, search, bank_index, bank_rating, assess_bank_case. Their descriptions and schemas cost roughly 655 tokens of context every time the server is loaded.
Does the Private Law Wiki MCP server require authentication?
No. We connected to Private Law Wiki without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Private Law Wiki MCP server still maintained?
Private Law Wiki is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.