AuthiChain
Look up AuthiChain product records. x402 paid verification and on-chain anchoring in development.
Should I use this
Quality & Safety
Findings (3)
- HIGH
- MEDIUMin get_pricing
- MEDIUMin scan_living_qr
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"authichain": {
"url": "https://authichain.com/mcp"
}
}
}Remote endpoints
https://authichain.com/mcpstreamable-httpWhat it can do
Tool inventory
Tools (8)
🟢get_pricing
Free. Quotes without charging or authorizing payment the live x402 agent rail ($0.05 USDC on Base) and live human Stripe checkouts: $29 Starter Pack (100 generations, paid once) at https://authichain.com/checkout/starter and $299 EU DPP Readiness at https://authichain.com/checkout/dpp_readiness. Starting a monthly plan replaces unused pack credits.
Input Schema
{
"type": "object",
"properties": {}
}🔴verify(sealId)
x402 paid seal-registry verification; use only after separate payment authorization, not for free lookup. 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.
Input Schema
{
"type": "object",
"properties": {
"sealId": {
"type": "string",
"format": "uuid",
"description": "Required seal UUID. productId and serial are not registry keys."
}
}
}🟢query_provenance(assetId)
Free registry and published-pack lookup for an assetId / seal / QR token; use for discovery, not proof of authenticity. 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.
Input Schema
{
"type": "object",
"properties": {
"assetId": {
"type": "string",
"description": "Seal, serial, or QR token identifier"
}
},
"required": [
"assetId"
]
}🟢verify_attestation(assetId, expectedObjectId)
Free. Use when verifying a registry-published attestation, not a supplied offline protocol record. 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.
Input Schema
{
"type": "object",
"properties": {
"assetId": {
"type": "string",
"description": "Unique attestation ID or exact seal/product identifier"
},
"expectedObjectId": {
"type": "string",
"description": "Optional independently observed object ID to compare with the signed subject"
}
},
"required": [
"assetId"
]
}🟢verify_record(id, record, anchor)
Free. Use for a supplied signed protocol record or demonstration record, not published JWS issuer-status checks. 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.
Input Schema
{
"type": "object",
"properties": {
"id": {
"type": "string",
"description": "Published record id. Only \"polygon-anchor-1\" exists."
},
"record": {
"type": "object",
"description": "A signed AuthiChain provenance record (JSON)."
},
"anchor": {
"type": "object",
"description": "Anchor JSON: { recordHash, chain: \"polygon:137\", txHash }. Optional."
}
}
}🟢dpp_readiness_check(category, sells_in_eu, unique_id, supplier_data, market_role, ...)
Free informational EU Digital Product Passport readiness questionnaire; this cannot issue a passport or certify compliance. 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.
Input Schema
{
"type": "object",
"properties": {
"category": {
"type": "string",
"enum": [
"battery_passport",
"battery_other",
"textiles",
"iron_steel",
"aluminium",
"tyres",
"furniture",
"mattresses",
"electronics",
"toys",
"construction",
"detergents",
"other"
],
"description": "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_steel: Iron and steel; aluminium: Aluminium; tyres: Tyres; furniture: Furniture; mattresses: Mattresses; electronics: Electronics and ICT; toys: Toys; construction: Construction products; detergents: Detergents and cleaning products; other: Something else"
},
"sells_in_eu": {
"type": "boolean",
"description": "Sold into the EU directly or via an importer. Default true."
},
"unique_id": {
"type": "boolean",
"description": "Each product (or model or batch) has a unique identifier, such as a GS1 GTIN with serial."
},
"supplier_data": {
"type": "boolean",
"description": "You can get material and substance data from your suppliers."
},
"market_role": {
"type": "boolean",
"description": "You know who places the product on the EU market (you, an importer or an EU representative)."
},
"footprint": {
"type": "boolean",
"description": "You have carbon or environmental footprint data for the product."
},
"data_host": {
"type": "boolean",
"description": "You have a public web location where product data could be published behind a QR code."
},
"data_owner": {
"type": "boolean",
"description": "A named person owns product compliance data."
}
},
"required": [
"category"
]
}🟢scan_living_qr(object_id)
Free. Read an existing Living QR presentation, not a QR generator or x402 purchase. 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.
Input Schema
{
"type": "object",
"properties": {
"object_id": {
"type": "string",
"description": "Stored presentation id. Canonical form is qron:url: plus 8 hex characters."
}
},
"required": [
"object_id"
]
}🟢negotiate(service, mode, currency, max_budget_usd)
Free, read-only, non-binding agent-to-agent capability/price-class quote. Returns available service, free vs separately authorized paid rail, and next step; never accepts terms, creates a commitment, transfers money, or calls an external service. This is NOT MCP initialize version negotiation.
Input Schema
{
"type": "object",
"properties": {
"service": {
"type": "string",
"enum": [
"get_pricing",
"verify",
"query_provenance",
"verify_attestation",
"verify_record",
"dpp_readiness_check",
"scan_living_qr"
],
"description": "Existing MCP service the agent wants to discuss."
},
"mode": {
"type": "string",
"enum": [
"quote_only"
],
"description": "Non-binding quote only. Defaults to quote_only."
},
"currency": {
"type": "string",
"enum": [
"USD"
],
"description": "Display denomination only; no FX transaction. Defaults to USD."
},
"max_budget_usd": {
"type": "number",
"minimum": 0,
"maximum": 1000000,
"description": "Optional caller budget ceiling; never authorizes a charge."
}
},
"required": [
"service"
],
"additionalProperties": false
}Community
Evidence