MCP connector
A remote MCP server that lets an assistant check whether a citation identifies a decision that exists in the listings TrueCite holds. Three tools, no language model anywhere in the answer, and a short list of things it will never claim.
The address
Connector URL: https://truecite.com.au/mcp
API contract: /api/v2/openapi.json
Privacy notice: /privacy.html
Method: /method.html
Three tools
| Tool | What it answers | Credential |
|---|---|---|
get_coverage |
Which jurisdictions, courts and report series the service currently holds listings for, and the version of that coverage data. | None |
verify_citation_identities |
For up to 100 citations: VERIFIED_EXISTS, IDENTITY_CONFLICT or UNRESOLVED, each with reason codes, the dated evidence basis, and the coverage version in force. |
Required |
get_usage |
Requests and items made this calendar month (UTC), by route. | Required |
Each item is one complete citation, optionally preceded by its case name, plus an item_id you choose. That is the whole input. There is no field for document text, and none will be added.
What it will never claim
UNRESOLVED is not a finding that a case does not exist, and it is not evidence that a citation was fabricated. It means the identity supplied could not be resolved from the listings this service holds. Coverage is partial and is declared; the live get_coverage response is the only statement of what is held.
A positive match is dated evidence as of the observation it cites. It is not proof of current publication, it is not a court endorsement, and it carries no judicial authority.
Quotation text, pinpoint accuracy, paragraph content, legal propositions, currency and good-law status are not checked. The response says so in a field: content_checks_performed is false on every result.
No model in the answer
No language model is called anywhere in this path. The connector forwards the verification core's answer unchanged — it does not interpret, summarise, rewrite or supplement it. That is the point of the product: a deterministic check is the thing a probabilistic assistant cannot do for itself.
It refuses document text
Pleadings, judgments and quotations have no field to arrive in. Input shaped like pasted document text — over 2,048 UTF-8 bytes, or spanning more than one paragraph — is refused before any request leaves, naming the rule that was broken and without echoing the text back.
These checks are structural, and the limit is worth stating plainly: a single line under the byte ceiling is not distinguishable from a citation at this layer, so it is passed to the verification service, which parses citations and cannot match text that is not one. No finding is drawn from it. The alternative — a rule that rejects anything that "looks like prose" — would one day reject a legitimate long case name, and guessing is the thing this service does not do.
Adding it in Claude
In Claude, open Customize → Connectors → Add custom connector, give it a name, and enter https://truecite.com.au/mcp.
Leave the credential fields empty. Claude Connect uses OAuth 2.1 with PKCE: Claude discovers this service's authorization server (including dynamic client registration), opens a consent page, and the lawyer signs in and approves the connection for their firm. No partner token is pasted into Claude.
get_coverage answers without a credential. verify_citation_identities and get_usage require a valid Bearer — an OAuth access token from that consent flow, or a partner token on the Authorization header.
Each tool advertises an outputSchema: a union of the success structuredContent and the tool-error shape { error: { code, message, data? } }. Coverage and usage are closed-world (openWorldHint: false); verification may consult declared external search evidence (openWorldHint: true).
What is transmitted
The connector transmits the citation identities you supply, plus the optional batch label and SHA-256 fingerprint fields, to truecite.com.au. It does not transmit document bodies. The verification service retains citation strings, optional labels and fingerprints, findings and provenance in its run record. For unresolved citations it may send the citation to external search services, including Google, as explained in the privacy notice. There is no document-body field; short prose can still fit the citation input limits, so send identifiers only.
A run is recorded when verify_citation_identities is called, which is why that tool is not marked read-only. Supply an idempotencyKey tool argument and reuse it with the same citation batch to retry without creating another run. Existing HTTP clients can also use Idempotency-Key; conflicting values are refused. A call without a key does not make a later call retry-safe. Retention and contact details are in the privacy notice.
Status
Pilot. OAuth 2.1 authorization and dynamic client registration are live on this service. A public connector directory listing may still be pending; no such listing is claimed. Commercial pricing and service levels require a separate agreement. No platform partnership, sandbox approval or endorsement is implied by this connector.
Contact
TrueCite · ABN 37 688 027 367 · Sydney · info@truecite.com.au