AuthiChain
REMOTE · AUTHICHAIN.COM
Verification of signed records, plus an EU DPP check.
Available components
Last scanned (3 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Crypto and Web3
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 987 tokens (~141/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 Management43
- Stability observed for 13 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 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
- Tool “get_pricing” rewrote its description, which is the text the model reads security
- Tool “verify” rewrote its description, which is the text the model reads security
- Schema quality: good → excellent functional
- 31 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “query_provenance” rewrote its description, which is the text the model reads security
- Schema quality: 858 → 1005 ▼ functional
- Server version: 1.3.2 → 1.4.0 functional
- New tool “verify_attestation” functional
- 29 Oct 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.
- 27 Oct 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.
- 25 Oct 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.
- 24 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.3.0 → 1.3.2 functional
- 23 Oct 26 62
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 5 Nov 2026 · Probed https://authichain.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=authichain.com | CN=WE1,O=Google Trust Services,C=US | 1 Nov 2026 | 30 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 40a92c2ef0a5b5410ebe3de63c196b61 |
| SANs: authichain.com, dpp-previews.authichain.com, *.dpp-previews.authichain.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 authichain.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| authichain.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://authichain.com/mcp | Verified | 200 | |
| http (plaintext) | http://authichain.com/mcp | HTTPS enforced | 301 | https://authichain.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 →
dpp_readiness_check ~330
Free EU Digital Product Passport readiness check. Returns a 0-100 score, gaps, and the dated obligation for the product category (battery passport is law from 18 Feb 2027; other categories are ESPR targets). Not legal advice.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | battery_passport: EV, LMT (e-bike, e-scooter) or industrial battery over 2 kWh; battery_other: Other battery (portable, SLI, industrial up to 2 kWh); textiles: Textiles, apparel or footwear; iron_ste… |
| data_host | boolean | – | You have a public web location where product data could be published behind a QR code. |
| data_owner | boolean | – | A named person owns product compliance data. |
| footprint | boolean | – | You have carbon or environmental footprint data for the product. |
| market_role | boolean | – | You know who places the product on the EU market (you, an importer or an EU representative). |
| sells_in_eu | boolean | – | Sold into the EU directly or via an importer. Default true. |
| supplier_data | boolean | – | You can get material and substance data from your suppliers. |
| unique_id | boolean | – | Each product (or model or batch) has a unique identifier, such as a GS1 GTIN with serial. |
No output schema declared.
No examples provided.
get_pricing ~41
Free. Quotes the live x402 agent rail ($0.05 USDC on Base) and lists free verification tools. Stripe catalogue SKUs are not listed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
query_provenance ~108
Free public lookup for an assetId / seal / QR token. Reads matching rows from the canonical auth_seals registry when public Supabase configuration is available, and also resolves published packs. A registry match means registered only; it does not verify a signature or prove a physical item is genuine. Use verify_attestation for a published v0.1 JWS; verify_record is the separate reference-protocol verifier.
| Name | Type | Req | Description |
|---|---|---|---|
| assetId | string | yes | Seal, serial, or QR token identifier |
No output schema declared.
No examples provided.
scan_living_qr ~97
Free. Scan a stored Living QR. GET https://authichain.com/qron/r/{object_id} returns AuthiChain Verification Decision v1. This host verifies the signature. A missing id is presentation_not_found. Not an x402 payment endpoint, and it does not inspect a physical product.
| Name | Type | Req | Description |
|---|---|---|---|
| object_id | string | yes | Stored presentation id. Canonical form is qron:url: plus 8 hex characters. |
No output schema declared.
No examples provided.
verify ~79
x402 seal verify. Arguments that cannot be a seal UUID are HTTP 400 before payment. Empty arguments are unpaid HTTP 402. Paid calls are answered from the seal registry at $0.05 USDC on Base. For free verification use verify_record.
| Name | Type | Req | Description |
|---|---|---|---|
| sealId | string | – | Required seal UUID. productId and serial are not registry keys. |
No output schema declared.
No examples provided.
verify_attestation ~118
Free. Fetch the exact published AuthiChain v0.1 JWS from the signed-record registry and pass it to the canonical edge-router verifier. Checks signature, issuer trust, durable revocation/status, expiry, and signed decision. Supply expectedObjectId to bind the record to a scanned object identifier. A valid signed claim alone does not prove physical authenticity.
| Name | Type | Req | Description |
|---|---|---|---|
| assetId | string | yes | Unique attestation ID or exact seal/product identifier |
| expectedObjectId | string | – | Optional independently observed object ID to compare with the signed subject |
No output schema declared.
No examples provided.
verify_record ~135
Free. Verify an AuthiChain signed provenance record with the open reference verifier. Pass id "polygon-anchor-1" for the published demonstration record, or pass your own record and anchor JSON. Returns verified, valid-unanchored, or invalid, plus whether the transaction carries the record hash. It does not inspect a physical product.
| Name | Type | Req | Description |
|---|---|---|---|
| anchor | object | – | Anchor JSON: { recordHash, chain: "polygon:137", txHash }. Optional. |
| id | string | – | Published record id. Only "polygon-anchor-1" exists. |
| record | object | – | A signed AuthiChain provenance record (JSON). |
No output schema declared.
No examples provided.
How do I install the AuthiChain MCP server?
AuthiChain is a hosted endpoint at https://authichain.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 · authichain.com
claude mcp add --transport http com-authichain-authichain 'https://authichain.com/mcp'
What is the AuthiChain MCP server?
AuthiChain is an MCP server listed in the public MCP registry as com.authichain/authichain. Verification of signed records, plus an EU DPP check. This page covers its hosted endpoint (https://authichain.com/mcp).
Is the AuthiChain MCP server safe to use?
AuthiChain scores 68 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 AuthiChain MCP server expose?
AuthiChain exposes 7 tools: get_pricing, verify, query_provenance, verify_attestation, verify_record, and 2 more. Their descriptions and schemas cost roughly 908 tokens of context every time the server is loaded.
Does the AuthiChain MCP server require authentication?
No. We connected to AuthiChain without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AuthiChain MCP server still maintained?
AuthiChain 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.