Privi Verify
REMOTE · PRIVI-VERIFY-S4JB.ONRENDER.COM
Manufacturing lot verification and chain of custody for AI agents, paid per call in USDC (x402).
Available components
Last scanned (16 hours ago)
Scores higher than 59% of remote servers
Reachable. Last reached 21 Nov 2026.
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 Security74
- 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. 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. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 2020 tokens (~101/item across 20 items; 20 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage92
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 72% of tool parameters carry a description.Partial
- Structured output schemas are declared (10% 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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 21 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +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.
- 19 Nov 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.
- 17 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.
- 16 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 15 Nov 26 70
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 21 Nov 2026 · Probed https://privi-verify-s4jb.onrender.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=onrender.com | CN=WE1,O=Google Trust Services,C=US | 19 Nov 2026 | 17 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 8d72a13c2c41648513b9d014eb5e0339 |
| SANs: onrender.com, *.onrender.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 privi-verify-s4jb.onrender.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| onrender.com. | No DS | 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://privi-verify-s4jb.onrender.com/mcp | Verified | 200 | |
| http (plaintext) | http://privi-verify-s4jb.onrender.com/mcp | HTTPS enforced | 301 | https://privi-verify-s4jb.onrender.com/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 →
chainflow_attach_document ChainFlow: attach a document to a lot ~166
Attach a mill test report, material certificate or inspection report to a lot by fingerprint. Manufacturers only.
| Name | Type | Req | Description |
|---|---|---|---|
| actor | string | yes | – |
| doc_type | string | yes | mill_test_report|material_certificate|inspection_report|first_article_inspection|heat_treat_certificate|plating_certificate|test_report|other |
| issuer | string | yes | Who issued it, e.g. the mill or lab |
| location | string | yes | Where it happened, e.g. 'Plant 2, Port Huron MI' |
| lot_code | string | yes | Lot or batch code |
| reference | string | – | Heat number, report number or similar |
| sha256 | string | yes | SHA-256 fingerprint of the document (64 hex characters); the file stays with you |
No output schema declared.
No examples provided.
chainflow_coc_issue ChainFlow: issue a Certificate of Conformance ~209
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.
| Name | Type | Req | Description |
|---|---|---|---|
| customer | string | yes | – |
| location | string | yes | Where it happened, e.g. 'Plant 2, Port Huron MI' |
| lot_code | string | yes | Lot or batch code |
| part_number | string | – | – |
| purchase_order | string | – | – |
| quantity | string | – | – |
| signer | string | yes | Person certifying |
| signer_title | string | yes | – |
| specification | string | yes | 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 |
No output schema declared.
No examples provided.
chainflow_coc_revoke ChainFlow: revoke a Certificate of Conformance ~68
Revoke a certificate issued in error. Manufacturers only.
| Name | Type | Req | Description |
|---|---|---|---|
| actor | string | yes | – |
| coc_id | string | yes | – |
| location | string | yes | Where it happened, e.g. 'Plant 2, Port Huron MI' |
| reason | string | yes | – |
No output schema declared.
No examples provided.
chainflow_coc_verify ChainFlow: check a Certificate of Conformance ~76
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.
| Name | Type | Req | Description |
|---|---|---|---|
| certificate_json | string | – | Or the exact certificate_json you were sent |
| coc_id | string | – | The certificate ID (coc_...) |
No output schema declared.
No examples provided.
chainflow_document_check ChainFlow: check a document ~55
Check that a document you were handed is the one attached to a lot, and see which lot.
| Name | Type | Req | Description |
|---|---|---|---|
| sha256 | string | yes | SHA-256 fingerprint of the document (64 hex characters); the file stays with you |
No output schema declared.
No examples provided.
chainflow_documents ChainFlow: a lot's documents ~42
The documents attached to a lot (type, issuer, reference, fingerprint) and common ones still missing.
| Name | Type | Req | Description |
|---|---|---|---|
| lot_code | string | yes | Lot or batch code |
No output schema declared.
No examples provided.
chainflow_gauge_calibrated ChainFlow: record a calibration ~101
Record a gauge's calibration with the fingerprint of its certificate. Manufacturers only.
| Name | Type | Req | Description |
|---|---|---|---|
| calibrated_at | – | – | When (ISO 8601). Default: now |
| calibrated_by | string | yes | Lab or person |
| certificate_sha256 | string | yes | SHA-256 fingerprint of the document (64 hex characters); the file stays with you |
| gauge_id | string | yes | – |
| result | string | – | pass | adjusted | fail |
No output schema declared.
No examples provided.
chainflow_gauge_save ChainFlow: add or update a gauge ~93
Add a measuring tool (micrometer, caliper, CMM, torque wrench) to the calibration list. Manufacturers only.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | – |
| gauge_id | string | yes | Your gauge ID or serial, e.g. MIC-014 |
| interval_days | integer | yes | Calibration interval in days (365 = yearly) |
| location | string | – | – |
| retired | boolean | – | – |
No output schema declared.
No examples provided.
chainflow_gauges_due ChainFlow: gauges due for calibration ~55
Which gauges are overdue, failed, never calibrated or due within 30 days, and which must not be used. Manufacturers only.
| Name | Type | Req | Description |
|---|---|---|---|
| gauge_id | string | – | One gauge; empty for the whole list |
No output schema declared.
No examples provided.
chainflow_link_lots ChainFlow: link a lot to what it was made from ~127
Record that one lot was made from another, so a recall can follow the material. Adds an event to both lots' histories. Manufacturers only.
| Name | Type | Req | Description |
|---|---|---|---|
| actor | string | yes | – |
| child_lot | string | yes | The lot that was made from it |
| location | string | yes | Where it happened, e.g. 'Plant 2, Port Huron MI' |
| parent_lot | string | yes | The lot that was used up (material, component) |
| quantity | string | – | How much of the parent went in, e.g. '400 kg' |
No output schema declared.
No examples provided.
chainflow_ncr_close ChainFlow: close a non-conformance report ~102
Close an NCR with its disposition and corrective action. Manufacturers only.
| Name | Type | Req | Description |
|---|---|---|---|
| closed_by | string | yes | – |
| corrective_action | string | yes | Root cause and what was done about it |
| disposition | string | yes | use_as_is|rework|repair|scrap|return_to_supplier |
| location | string | yes | Where it happened, e.g. 'Plant 2, Port Huron MI' |
| ncr_id | string | yes | – |
No output schema declared.
No examples provided.
chainflow_ncr_list ChainFlow: non-conformance reports ~55
List non-conformance reports with days open, for one lot or all. Manufacturers only.
| Name | Type | Req | Description |
|---|---|---|---|
| lot_code | string | – | Limit to one lot |
| status | string | – | open or closed; empty for both |
No output schema declared.
No examples provided.
chainflow_ncr_open ChainFlow: open a non-conformance report ~120
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.
| Name | Type | Req | Description |
|---|---|---|---|
| defect | string | yes | What is wrong |
| location | string | yes | Where it happened, e.g. 'Plant 2, Port Huron MI' |
| lot_code | string | yes | Lot or batch code |
| opened_by | string | yes | – |
| quantity_affected | string | – | – |
| severity | string | yes | minor|major|critical |
No output schema declared.
No examples provided.
chainflow_recall_trace ChainFlow: recall trace ~66
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.
| Name | Type | Req | Description |
|---|---|---|---|
| lot_code | string | yes | Lot or batch code |
No output schema declared.
No examples provided.
privi_chain_of_custody Chain of custody ~56
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.
| Name | Type | Req | Description |
|---|---|---|---|
| lot_code | string | yes | Lot or batch code |
No output schema declared.
No examples provided.
privi_lookup_fingerprint Look up a record fingerprint ~48
Check whether a record fingerprint (from a label, certificate or document) exists in Privi. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| fingerprint | string | yes | 64-character hex SHA-256 record fingerprint |
No output schema declared.
No examples provided.
privi_pricing Privi pricing ~25
List Privi Verify tools, what each costs, and how payment works.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
privi_record_event Record a lot event ~164
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.
| Name | Type | Req | Description |
|---|---|---|---|
| actor | string | yes | Company or person responsible |
| event_type | string | yes | One of: received, produced, inspected, shipped, transferred, recalled |
| location | string | yes | Where it happened, e.g. 'Plant 2, Port Huron MI' |
| lot_code | string | yes | Lot or batch code |
| notes | string | – | – |
| product | string | – | Product name or part number |
| quantity | string | – | Quantity with units, e.g. '500 kg' |
No output schema declared.
No examples provided.
privi_token_market PRIVI token market ~126
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
Structured output declared, but exposes no named fields.
No examples provided.
privi_verify_lot Verify a lot ~56
Verify a lot: product, first and latest custody events, recall status, and whether its record history is intact. Paid per call via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| lot_code | string | yes | Lot or batch code to verify |
No output schema declared.
No examples provided.
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.
remote · privi-verify-s4jb.onrender.com
claude mcp add --transport http canoydario847-cloud-privi-verify 'https://privi-verify-s4jb.onrender.com/mcp'
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.