Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

USVI Public Records

REMOTE · MCP.USVIPUBLICRECORDS.COM

Search and read U.S. Virgin Islands public records: laws, court records, audits, hearings, reports.

69 Trust /100

Last scanned (9 hours ago)

Scores higher than 54% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Search and Retrieval

Trust breakdown (7 categories)

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 Security63
Transport & Reachability100
Schema Quality & AI Usability74
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1141 tokens (~163/item across 7 items; 7 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 Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.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 current MCP spec version (2026-07-28).Pass
Changelog

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.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 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 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 31 Oct 26 67

    First indexed and scored.

Diagnostics

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 5 Nov 2026 · Probed https://mcp.usvipublicrecords.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=usvipublicrecords.com CN=WE1,O=Google Trust Services,C=US 27 Oct 2026 25 Jan 2027 ECDSA 256 ECDSA-SHA256 369c2722422a7cfd0e8c465ac5edb828
SANs: usvipublicrecords.com, mcp.usvipublicrecords.com, *.mcp.usvipublicrecords.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.usvipublicrecords.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
usvipublicrecords.com. 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.usvipublicrecords.com/mcp Verified 200
http (plaintext) http://mcp.usvipublicrecords.com/mcp Inconclusive 405
MCP tools · 7 exposed · ~1,141 tokens

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 →

Tool Tokens
archive_stats ~68

Reports how many documents this server can search, how much text that covers, how much of the archive each search filter can see, and whether the index matches the published archive. Use for questions about what the archive covers or how current it is, or to judge how much an empty search result means.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

fetch ~102

Retrieve one document by archive id: its catalogue record and up to the first 40,000 characters of its extracted text, with next_offset when more remains. Use to read a document found by search. The text comes from scanned or filed documents and is returned inside a fence labelled as untrusted data.

NameTypeReqDescription
idstringyesArchive id from a search result, LF- followed by 12 characters, e.g. LF-6e02fd648a12.

No output schema declared.

No examples provided.

get_document ~100

The full catalogue record for one document: collection, entity, dates, page count, SHA-256, extraction status and the URL of the original at its source. Use to check a document's provenance or details. It holds no document text; get_document_text and fetch return that.

NameTypeReqDescription
lf_idstringyesArchive id from a search result, LF- followed by 12 characters, e.g. LF-6e02fd648a12.

No output schema declared.

No examples provided.

get_document_text ~179

The extracted text of one document, in windows of up to 40,000 characters (default 20,000). Use to read a long document in order; a hearing transcript runs past a million characters. Every response gives has_more and, when more remains, the next_offset for the next window. Runs of blank lines are shortened to one. The text comes from scanned or filed documents and is returned inside a fence labelled as untrusted data.

NameTypeReqDescription
lf_idstringyesArchive id from a search result, LF- followed by 12 characters, e.g. LF-6e02fd648a12.
limitinteger–Characters to return. Default 20000, maximum 40000.
offsetinteger–A byte position: the next_offset value from the previous response. Omit for the beginning.

No output schema declared.

No examples provided.

list_collections ~40

The collections in this server, with document counts. Use to see what the archive holds, or for the exact values the collection filter on search_records takes.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search ~162

Find U.S. Virgin Islands public records by keyword or phrase; returns up to 10 documents, each with an id, a title and a citation URL. Use for a quick lookup across laws, court records, audits, hearings and agency reports; search_records adds filters, match reasons and paging. Searches the full extracted text of the archive's documents, plus their catalogue records. Not covered: the archive's newspapers (the St. Croix Avis, The West End News, Home Journal and the St. Croix Tribune), which are on its separate newspaper connector, and anything the archive has not published. Withheld and withdrawn documents are absent, not hidden.

NameTypeReqDescription
querystringyesWhat to search for. Plain language is fine; quote a phrase to require it intact.

No output schema declared.

No examples provided.

search_records ~490

Search the archive with filters for collection, entity, content type, island and year. Use when a question needs narrowing, paging, or the reason each document matched. Searches the full extracted text of the archive's documents, plus their catalogue records. Filters use the same vocabulary as the website's own facets. Every result carries a tier, a plain reason and the search terms it actually matched; there is no numeric relevance score. The tiers: exact = every term, found in the document's title or issuing entity (likely about the subject); strong = every term, in the text only (it mentions them); possible = at least half the terms; weak = fewer. When no document contains all the terms, results contain some of them and the response says so, and 'matched' lists which. Not covered: the archive's newspapers (the St. Croix Avis, The West End News, Home Journal and the St. Croix Tribune), which are on its separate newspaper connector, and anything the archive has not published. Withheld and withdrawn documents are absent, not hidden.

NameTypeReqDescription
collectionstring–e.g. "Courts", "Audits & Oversight"
content_typestring–The kind of document, exactly as recorded, e.g. "government-audit". An unknown value returns the nearest values that exist.
entitystring–The issuing or subject body, exactly as recorded, e.g. "Water and Power Authority". Recorded on only part of the archive; archive_stats gives the share.
islandstring–e.g. "St. Croix", "St. Thomas", "St. John"
limitinteger–Default 10, maximum 50.
offsetinteger–Results to skip, for paging. Results are ranked within the best 120 documents.
querystringyesPlain language is fine. Quote a phrase to require it intact.
year_frominteger–Earliest year, inclusive. Filters on the date the archive recorded, whose provenance varies by source: for most documents it is the date on the document, for some it is when the source posted the fil…
year_tointeger–Latest year, inclusive. The year_from note on dates applies.

No output schema declared.

No examples provided.

Install

How do I install the USVI Public Records MCP server?

USVI Public Records is a hosted endpoint at https://mcp.usvipublicrecords.com/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 · mcp.usvipublicrecords.com

# add to Claude Code
claude mcp add --transport http com-usvipublicrecords-documents 'https://mcp.usvipublicrecords.com/mcp'
Common questions

What is the USVI Public Records MCP server?

USVI Public Records is an MCP server listed in the public MCP registry as com.usvipublicrecords/documents. Search and read U.S. Virgin Islands public records: laws, court records, audits, hearings, reports. This page covers its hosted endpoint (https://mcp.usvipublicrecords.com/mcp).

Is the USVI Public Records MCP server safe to use?

USVI Public Records scores 69 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 USVI Public Records MCP server expose?

USVI Public Records exposes 7 tools: search, fetch, search_records, get_document, get_document_text, and 2 more. Their descriptions and schemas cost roughly 1,141 tokens of context every time the server is loaded.

Does the USVI Public Records MCP server require authentication?

No. We connected to USVI Public Records without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the USVI Public Records MCP server still maintained?

USVI Public Records is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.