Utuh watcher

Name: Utuh watcher
Author: PugarHuda

by PugarHudaversion 0.4.0i★ –iRuns on your computer

Registry nameio.github.PugarHuda/utuh-mcp

Install

Overview

Description from the maker (original English)

Sweep bonded completeness claims on Creditcoin against Ethereum, and refute one that omits an event.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiVery new↓ 63/wk · ★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Crypto & blockchain
You need to fill in: PRIVATE_KEY

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: PRIVATE_KEY

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "utuh": {
      "command": "npx",
      "args": [
        "-y",
        "utuh-mcp"
      ],
      "env": {
        "PRIVATE_KEY": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add utuh --env PRIVATE_KEY=your-value -- npx -y utuh-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "utuh": {
      "command": "npx",
      "args": [
        "-y",
        "utuh-mcp"
      ],
      "env": {
        "PRIVATE_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "utuh": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "utuh-mcp"
      ],
      "env": {
        "PRIVATE_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

PRIVATE_KEY secret env
A funded Creditcoin CC3 Testnet key, needed only by refute_claim — which also demands confirm: true. Every other tool reads the chain and spends nothing.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account PugarHuda, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Crypto & blockchaini

More stars than 0% of the other 1615 servers in this category
Published to the registry more recently than 46% of the other 1615 servers in this category
Basic checks equal to or better than 100% of the other 1615 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Utuh watcher safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: PRIVATE_KEY

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.4.0) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: xsolana, Smogon MCP, Mempool MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

xsolana

Design, check, simulate and launch Solana game economies on loot, one shared program, no contract.

by XGamesFunVery new↓ 164/wkUpdated today

Runs on your computer

Install

Smogon MCP

MCP server for competitive Pokemon, full dex data plus monthly Smogon usage statistics.

by mrfentmenVery new↓ 53/wkUpdated today

Runs on your computer

Install

Mempool MCP

Bitcoin network status: recommended fees, mempool backlog, blocks, addresses, difficulty retargets.

by mrfentmenVery new↓ 184/wkUpdated today

Runs on your computer

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Utuh

Utuh bonds the claim that a set of events is complete, pays half the bond to anyone who proves one event was left out, and lends CTC undercollateralized against the claims that survive.

_utuh_ — Indonesian: whole, intact, with nothing missing. A completeness layer for the Attestcoin Protocol, built for BUIDL CTC 2026 Fall and deployed on Creditcoin CC3 Testnet.

Live: utuh.vercel.app (landing, read from Creditcoin as it draws) and the console at utuh.vercel.app/app/ (sweep, refute, borrow; no server, no clone).
Two refuted claims, one click each: claim 5, sealed one event short and broken from a browser · claim 20, a false _"never liquidated"_ over 216,000 Ethereum mainnet blocks, refuted by one liquidation proof



The landing page, claim 5 as a working paper	The console, claim 20 opened verdict first

Dark scheme	A sweep of claim 5 from the browser, with its provenance

Verify every number yourself: npm run judge — no key. It re-measures every number this repository and the submission quote against the live chain and exits non-zero on any that no longer holds. On 2026-09-14, after the production deploy, it printed 25 of 25, two of them checks that read the example gate below.
Hold the watcher role from an agent: npx -y utuh-mcp — 0.4.0 on npm and in the official MCP Registry. For clients that cannot run a command, the same server answers at https://utuh.vercel.app/api/mcp (below).
Measured: 211 Foundry tests with 16 invariants, 100% line and branch coverage and 99.1% of 737 mutants killed · Slither 0 findings · halmos 5 of 5 · every contract verified on Blockscout and matched on Sourcify · 248 TransactionVerified events on CC3's own indexer.
Demo video (3 min): https://youtu.be/HwSnv3E4tzo · Whitepaper: PDF, from web/whitepaper.html · Deck: web/deck.pdf

What is on-chain, all verified on Blockscout and Sourcify (every address and read):

On CC3 Testnet (chain 102031)	Address	What it holds
`UtuhRegistry`, Ethereum-mainnet-sourced	`0x8FA0…5Fac`	72 claims over real Ethereum mainnet history; 32 refuted, claim 20 among them
`UtuhRegistry`, Sepolia-sourced	`0x2688…347b`	13 claims, the completed borrow-and-repay loop; claims 3 and 5 refuted
`UtuhCredit`, Sepolia-sourced	`0x0177…24b6`	lines 1–3 opened, drawn, repaid on Sepolia and settled; lines 2 and 3 entirely from the console
`SettlementLedger`, on Sepolia	`0xC8C9…575B`	the source-chain repayments those lines settled on
Creditcoin's own oracle record	transaction-verifications	248 `TransactionVerified` rows are Utuh's: 212 claim members, 34 refutations, the rest control bindings

A contract that is not Utuh reads it: NeverLiquidatedGate at 0xcA62…5D09 granted an allowance on claim 72 and refused refuted claim 20. This project wrote and deployed it as the worked example, so it is not an outside user.

The short version · The problem · What this uses of Creditcoin's · Next to Creditcoin's own example · What Utuh does · Built on Ethereum mainnet · UtuhCredit · Deployed on CC3 Testnet · Two demonstrations · The watcher as an MCP server · The console · Layout · Running it · On testing · What the tools say · Before you build on this · Attestcoin surface used · Known limits · License

Elsewhere: [docs/INTEGRATING.md](docs/INTEGRATING.md) (use the registry from your own contract) · [docs/COMPLETENESS.md](docs/COMPLETENESS.md) (does what you built have this gap?) · [docs/ROADMAP.md](docs/ROADMAP.md) (what is gated on whom) · docs/AUDIT.md · docs/MAINNET.md · SECURITY.md · 한국어 요약: [docs/README.ko.md](docs/README.ko.md)

The short version

Any registry on this protocol can tell you what it holds. Ask one whether a borrower has ever been liquidated and it can only answer with what someone chose to submit — and the borrower will not be submitting that. Utuh bonds the claim that a set is all of them, and pays half the bond to anyone who proves one event was left out.

The landing page reads both registries from Creditcoin as it draws — the two refuted claims with their block-range strips, the tally (proven, sealed, broken, burned), the deployed addresses — and each deep link above opens the console on the claim with its verdict first. The console reads the chain from your own browser, lets anyone sweep Ethereum and break an incomplete claim, and lets a borrower be underwritten end to end without cloning anything. npm run web serves both locally. Every verification behind the two refuted claims is on Creditcoin's own oracle dashboard, which nobody here can write to.

Two things a reader with a clone and no key can check first. npm run judge re-measures every number this repository and the submission quote — the contracts and their verification, the tally, both linked claims, the explorer counters, npm, the MCP Registry, the published build, the sixteen protocol entry points, the test and commit counts — and exits non-zero on any that no longer holds. And a bond here stands behind a specific line, not behind nothing: UtuhCredit.openLine reaches a claim only through UtuhRegistry.isUsable(claimId, exposure), the finalized claim is spent by the line it opens, underwrittenThrough consumes the history range, and the limit is capped at ten times the enforceable loss. Exposure is gated by the bond and consumed by the draw.

The problem

The Attestcoin Protocol proves that a source-chain transaction _happened_. A Merkle proof places the transaction in a block; a continuity proof anchors that block to an attestation stored on Creditcoin. The Block Prover precompile at 0x0FD2 checks both natively, synchronously, inside a single Creditcoin block.

What it cannot prove is that a _set_ of events is complete.

Whoever submits proofs chooses which proofs to submit. Every one of them verifies. Nothing in the protocol notices the ones that were left out.

For credit, that gap is fatal. The sentence every on-chain credit system needs is:

_This borrower has never been liquidated._

That is a statement about events which do not exist, and an inclusion proof can only ever speak about events which do. A borrower assembles their own history, submits the flattering half, and each proof checks out.

This is not hypothetical. Season 1 of this hackathon drew 76 submissions, and more than twenty of them were some form of on-chain credit score or reputation-based lending; one of those, CreditX, took a prize. Every one of them inherits this hole, the winner included — placing well is not the same as closing it, and an inclusion proof gives none of them a way to.

What this uses of Creditcoin's, and what it deliberately does not

npm run doctor (no key needed; given one it also reports the balance) ends by making a live request to every Creditcoin-owned surface this depends on, so the list below is checkable rather than asserted. A run on 2026-09-10:

Creditcoin ecosystem surfaces

ok USC Oracle dashboard 200 — every verifyAndEmit here is listed by source height ok testnet indexer 68,160 attestations of Ethereum, chain key 3 ok mainnet indexer 52,463 attestations of Ethereum, chain key 1 ok Creditcoin Mainnet RPC chain id 102030 ok Blockscout · registry UtuhRegistry verified ok Sourcify · registry chain 102031: match match, creation match ok Blockscout · credit UtuhCredit verified ok Sourcify · credit chain 102031: match match, creation match

On top of the protocol itself — both precompiles, both verifyAndEmit overloads, EvmV1Decoder, @gluwa/usc-contracts and @gluwa/usc-sdk, the hosted Proof Builder under both of its hostnames, and RawProofBuilder as the path that needs no hosted service at all.

The pins are deliberate. Gluwa published @gluwa/asc-contracts 0.2.1 on 2026-08-31 under the new ASC name, and the reference examples import from it; this tree stays on @gluwa/usc-contracts 0.1.2 and @gluwa/usc-sdk 0.18.0 (there is no newer SDK and no asc-sdk). 0.1.2's EvmV1Decoder functions are public, which is why the decoder links as a deployed library at 0x5cab…df3F; 0.2.1 made them internal and dropped the type-specific decoders Utuh never calls. The four it does call keep identical signatures in 0.2.1, and changing the pin changes bytecode and breaks the Blockscout and Sourcify match of the live deployment, so the rename lands on the merkle-claims branch, which redeploys anyway.

Two of those lines are worth reading twice. Every append and every refutation goes through verifyAndEmit rather than its view twin, so Creditcoin's own oracle dashboard is the record — the network logged this project's work, not the other way round. And the Creditcoin Mainnet indexer is read even though nothing here is deployed there: the console audits mainnet's attestors against Ethereum itself, because auditing only the network you deployed to leaves the produ

Only the beginning is shown; read the rest in the repo

Utuh watcher

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Crypto & blockchaini

Common questions

Alternatives

xsolana

Smogon MCP

Mempool MCP

README from the maker

Utuh

Contents

The short version

The problem

What this uses of Creditcoin's, and what it deliberately does not