# Privi Verify (remote · privi-verify-s4jb.onrender.com)

Manufacturing lot verification and chain of custody for AI agents, paid per call in USDC (x402).

- Trust score: 73/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `privi-verify-s4jb.onrender.com`: 73/100 (this document), [markdown](https://verifymcp.io/servers/canoydario847-cloud-privi-verify/privi-verify-s4jb.md), [page](https://verifymcp.io/servers/canoydario847-cloud-privi-verify/privi-verify-s4jb)

## Channel facts

- Endpoint: `https://privi-verify-s4jb.onrender.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.5.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 2020 tokens (~101/item across 20 items; 20 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 92/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 72% of tool parameters carry a description.
  - Structured output schemas are declared (10% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Privi Verify MCP server?

Privi Verify is a hosted endpoint at https://privi-verify-s4jb.onrender.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.

### Claude

```bash
claude mcp add --transport http canoydario847-cloud-privi-verify 'https://privi-verify-s4jb.onrender.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "canoydario847-cloud-privi-verify": {
      "url": "https://privi-verify-s4jb.onrender.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "canoydario847-cloud-privi-verify": {
      "type": "http",
      "url": "https://privi-verify-s4jb.onrender.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.canoydario847-cloud-privi-verify]
url = "https://privi-verify-s4jb.onrender.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "canoydario847-cloud-privi-verify": {
      "type": "remote",
      "url": "https://privi-verify-s4jb.onrender.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add canoydario847-cloud-privi-verify --url 'https://privi-verify-s4jb.onrender.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  canoydario847-cloud-privi-verify:
    url: "https://privi-verify-s4jb.onrender.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "canoydario847-cloud-privi-verify": {
      "Transport": "http",
      "Url": "https://privi-verify-s4jb.onrender.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add canoydario847-cloud-privi-verify -t streamable-http -u 'https://privi-verify-s4jb.onrender.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "canoydario847-cloud-privi-verify": {
      "type": "http",
      "url": "https://privi-verify-s4jb.onrender.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 73, +1)

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

### 2026-11-19 (score 72, +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.

### 2026-11-17 (score 71, +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.

### 2026-11-16 (score 70, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-15 (score 70)

First indexed and scored.

## MCP tools (20)

### `privi_token_market` (~126 tokens)

PRIVI token market

PRIVI on Base: price, how much PRIVI and USDC the Privi swap desk holds (so whether a swap can fill),
any Uniswap v3 / Aerodrome pools, and optionally a swap quote. Every paid Privi tool also accepts PRIVI. Free.

Input parameters:

- `amount` (string): Amount to swap in (USDC for buy, PRIVI for sell), e.g. '25'
- `side` (string): Optional swap quote: 'buy' (USDC -> PRIVI) or 'sell' (PRIVI -> USDC)

### `privi_pricing` (~25 tokens)

Privi pricing

List Privi Verify tools, what each costs, and how payment works.

### `privi_lookup_fingerprint` (~48 tokens)

Look up a record fingerprint

Check whether a record fingerprint (from a label, certificate or document) exists in Privi. Free.

Input parameters:

- `fingerprint` (string, required): 64-character hex SHA-256 record fingerprint

### `privi_verify_lot` (~56 tokens)

Verify a lot

Verify a lot: product, first and latest custody events, recall status, and whether
its record history is intact. Paid per call via x402.

Input parameters:

- `lot_code` (string, required): Lot or batch code to verify

### `privi_chain_of_custody` (~56 tokens)

Chain of custody

Full ordered event history for a lot with each event's fingerprint, plus an
integrity check of the whole chain. Paid per call via x402.

Input parameters:

- `lot_code` (string, required): Lot or batch code

### `privi_record_event` (~164 tokens)

Record a lot event

Append an event to a lot's history (manufacturers only). Requires
'Authorization: Bearer <key>' with a key from PRIVI_WRITE_KEYS. Over stdio,
writes are allowed only when PRIVI_ALLOW_LOCAL_WRITES=1.

Input parameters:

- `actor` (string, required): Company or person responsible
- `event_type` (string, required): One of: received, produced, inspected, shipped, transferred, recalled
- `location` (string, required): Where it happened, e.g. 'Plant 2, Port Huron MI'
- `lot_code` (string, required): Lot or batch code
- `notes` (string)
- `product` (string): Product name or part number
- `quantity` (string): Quantity with units, e.g. '500 kg'

### `chainflow_link_lots` (~127 tokens)

ChainFlow: link a lot to what it was made from

Record that one lot was made from another, so a recall can follow the material. Adds an event to both
lots' histories. Manufacturers only.

Input parameters:

- `actor` (string, required)
- `child_lot` (string, required): The lot that was made from it
- `location` (string, required): Where it happened, e.g. 'Plant 2, Port Huron MI'
- `parent_lot` (string, required): The lot that was used up (material, component)
- `quantity` (string): How much of the parent went in, e.g. '400 kg'

### `chainflow_recall_trace` (~66 tokens)

ChainFlow: recall trace

Everything a lot touched: the lots made from it (and from those), which have already shipped, which
are not yet recalled, and the lots it was itself made from. The list a recall starts with.

Input parameters:

- `lot_code` (string, required): Lot or batch code

### `chainflow_coc_issue` (~209 tokens)

ChainFlow: issue a Certificate of Conformance

Issue a Certificate of Conformance for a lot. It names the customer, spec and signer, lists the lot's
attached documents and points at the lot's record, so the buyer can check it has not been edited.
Refused for recalled lots, lots with open non-conformance reports, or altered histories. Manufacturers only.

Input parameters:

- `customer` (string, required)
- `location` (string, required): Where it happened, e.g. 'Plant 2, Port Huron MI'
- `lot_code` (string, required): Lot or batch code
- `part_number` (string)
- `purchase_order` (string)
- `quantity` (string)
- `signer` (string, required): Person certifying
- `signer_title` (string, required)
- `specification` (string, required): Drawing, standard or spec and revision, e.g. 'DWG A-12 rev C, ASTM A36'
- `statement` (string): Your own certification wording; a standard sentence is used if empty

### `chainflow_coc_verify` (~76 tokens)

ChainFlow: check a Certificate of Conformance

Check a Certificate of Conformance a supplier sent you: that it was issued as shown, is not revoked,
and that its lot has not been recalled or altered since.

Input parameters:

- `certificate_json` (string): Or the exact certificate_json you were sent
- `coc_id` (string): The certificate ID (coc_...)

### `chainflow_coc_revoke` (~68 tokens)

ChainFlow: revoke a Certificate of Conformance

Revoke a certificate issued in error. Manufacturers only.

Input parameters:

- `actor` (string, required)
- `coc_id` (string, required)
- `location` (string, required): Where it happened, e.g. 'Plant 2, Port Huron MI'
- `reason` (string, required)

### `chainflow_attach_document` (~166 tokens)

ChainFlow: attach a document to a lot

Attach a mill test report, material certificate or inspection report to a lot by fingerprint.
Manufacturers only.

Input parameters:

- `actor` (string, required)
- `doc_type` (string, required): mill_test_report|material_certificate|inspection_report|first_article_inspection|heat_treat_certificate|plating_certificate|test_report|other
- `issuer` (string, required): Who issued it, e.g. the mill or lab
- `location` (string, required): Where it happened, e.g. 'Plant 2, Port Huron MI'
- `lot_code` (string, required): Lot or batch code
- `reference` (string): Heat number, report number or similar
- `sha256` (string, required): SHA-256 fingerprint of the document (64 hex characters); the file stays with you

### `chainflow_documents` (~42 tokens)

ChainFlow: a lot's documents

The documents attached to a lot (type, issuer, reference, fingerprint) and common ones still missing.

Input parameters:

- `lot_code` (string, required): Lot or batch code

### `chainflow_document_check` (~55 tokens)

ChainFlow: check a document

Check that a document you were handed is the one attached to a lot, and see which lot.

Input parameters:

- `sha256` (string, required): SHA-256 fingerprint of the document (64 hex characters); the file stays with you

### `chainflow_ncr_open` (~120 tokens)

ChainFlow: open a non-conformance report

Open a non-conformance report (NCR) against a lot. While it is open, no Certificate of Conformance can
be issued for that lot. Manufacturers only.

Input parameters:

- `defect` (string, required): What is wrong
- `location` (string, required): Where it happened, e.g. 'Plant 2, Port Huron MI'
- `lot_code` (string, required): Lot or batch code
- `opened_by` (string, required)
- `quantity_affected` (string)
- `severity` (string, required): minor|major|critical

### `chainflow_ncr_close` (~102 tokens)

ChainFlow: close a non-conformance report

Close an NCR with its disposition and corrective action. Manufacturers only.

Input parameters:

- `closed_by` (string, required)
- `corrective_action` (string, required): Root cause and what was done about it
- `disposition` (string, required): use_as_is|rework|repair|scrap|return_to_supplier
- `location` (string, required): Where it happened, e.g. 'Plant 2, Port Huron MI'
- `ncr_id` (string, required)

### `chainflow_ncr_list` (~55 tokens)

ChainFlow: non-conformance reports

List non-conformance reports with days open, for one lot or all. Manufacturers only.

Input parameters:

- `lot_code` (string): Limit to one lot
- `status` (string): open or closed; empty for both

### `chainflow_gauge_save` (~93 tokens)

ChainFlow: add or update a gauge

Add a measuring tool (micrometer, caliper, CMM, torque wrench) to the calibration list. Manufacturers only.

Input parameters:

- `description` (string, required)
- `gauge_id` (string, required): Your gauge ID or serial, e.g. MIC-014
- `interval_days` (integer, required): Calibration interval in days (365 = yearly)
- `location` (string)
- `retired` (boolean)

### `chainflow_gauge_calibrated` (~101 tokens)

ChainFlow: record a calibration

Record a gauge's calibration with the fingerprint of its certificate. Manufacturers only.

Input parameters:

- `calibrated_at`: When (ISO 8601). Default: now
- `calibrated_by` (string, required): Lab or person
- `certificate_sha256` (string, required): SHA-256 fingerprint of the document (64 hex characters); the file stays with you
- `gauge_id` (string, required)
- `result` (string): pass | adjusted | fail

### `chainflow_gauges_due` (~55 tokens)

ChainFlow: gauges due for calibration

Which gauges are overdue, failed, never calibrated or due within 30 days, and which must not be used.
Manufacturers only.

Input parameters:

- `gauge_id` (string): One gauge; empty for the whole list

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/canoydario847-cloud-privi-verify/privi-verify-s4jb#diagnostics

## Score history

- 2026-11-21: 73
- 2026-11-20: 72
- 2026-11-19: 72
- 2026-11-18: 71
- 2026-11-17: 71
- 2026-11-16: 70
- 2026-11-15: 70

## Common questions

### What is the Privi Verify MCP server?

Privi Verify is an MCP server listed in the public MCP registry as io.github.canoydario847-cloud/privi-verify. Manufacturing lot verification and chain of custody for AI agents, paid per call in USDC (x402). This page covers its hosted endpoint (https://privi-verify-s4jb.onrender.com/mcp).

### Is the Privi Verify MCP server safe to use?

Privi Verify scores 73 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 Privi Verify MCP server expose?

Privi Verify exposes 20 tools: privi_token_market, privi_pricing, privi_lookup_fingerprint, privi_verify_lot, privi_chain_of_custody, and 15 more. Their descriptions and schemas cost roughly 1,810 tokens of context every time the server is loaded.

### Does the Privi Verify MCP server require authentication?

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

### Is the Privi Verify MCP server still maintained?

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

### What did VerifyMCP test on the Privi Verify MCP server?

VerifyMCP ran 13 checks on Privi Verify, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://privi-verify-s4jb.onrender.com/mcp
- Repository: https://github.com/canoydario847-cloud/Privi-Network
- Website: https://privi-discovery-6lue.onrender.com/
- Changelog RSS feed: https://verifymcp.io/servers/canoydario847-cloud-privi-verify/privi-verify-s4jb.xml
- Changelog JSON feed: https://verifymcp.io/servers/canoydario847-cloud-privi-verify/privi-verify-s4jb/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/canoydario847-cloud-privi-verify/privi-verify-s4jb.json
- HTML version of this page: https://verifymcp.io/servers/canoydario847-cloud-privi-verify/privi-verify-s4jb
