AuthiChain
io.github.undone0603Published by GitHub account undone0603v1.3.2Updated Oct 23, 2026
Look up AuthiChain product records. x402 paid verification and on-chain anchoring in development.
The publisher's own server: AuthiChain
Overview
Lets an assistant look up AuthiChain product records and, per the description, use paid verification and on-chain anchoring that are still in development.
- What you can do
- AuthiChain is a remote MCP endpoint for a physical-world trust layer: a product or asset identifier resolves to a signed claim, and policy and provenance data are evaluated to return an auditable verification result. The registry description says it supports looking up AuthiChain product records, with x402 paid verification and on-chain anchoring noted as in development. The README describes the wider flow of identify, resolve, attest, verify, interpret and act, exposed to agents through MCP, API or web interfaces. No individual tools are listed in the manifest.
- When to use it
- Consider it when an assistant needs to check AuthiChain product or asset records, or to consume verification results for identifiers such as GS1 Digital Link GTIN and serial values. It is aimed at agentic and enterprise workflows that need evidence-backed verification rather than simple identifier resolution.
- Requirements
- A remote MCP connection to the AuthiChain endpoint; no package, environment variable or header is declared in the manifest. The README's local build instructions (pnpm, Cloudflare Workers, Supabase/Postgres, DATABASE_URL) apply to running the repository itself, not to using the hosted endpoint.
Installation
In SourceWeft
- Open AuthiChain in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.undone0603%2Fauthichain/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"authichain": {
"type": "http",
"url": "https://authichain.com/mcp"
}
}
}README
This repository has no README.
Tools
0Version history
6- v1.3.2LatestOct 16, 2026
- v1.3.1Oct 9, 2026
- v1.3.0Oct 8, 2026
- v1.2.0Oct 3, 2026
- v1.1.1Sep 29, 2026
- v1.1.0Sep 27, 2026
Score
28% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.