biii

Name: biii
Author: philpof102-svg

MCP serverMCP

Fail-closed safe-to-pay verdicts on Base: known-bad wallets, look-alike tokens, repeat rug funders.

by philpof102-svgrepository ↗v0.2.1

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"biii","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability110/110 checks ok

Tools observed via MCP handshake

till_vet_merchant — MainStreet safe-to-pay preflight on a merchant address. Returns the hosted oracle read (advisory) AND a LOCAL CLASSIFIER verdict computed on this node via trust
till_create_charge — Create a USDC-on-Base charge for a real-world merchant. Returns the charge + the EIP-681 payment URI your OWN wallet must execute (basetill holds no key, moves
till_check_payment — Watch Base for the USDC transfer paying a charge and verify it FIELD-FOR-FIELD (wrong chain/token/recipient/underpay/unconfirmed = NOT paid). Only the chain say
till_trust — The TRUST TRIANGLE in one call: composes reputation, standing (LAWBOR proven history, if BIII_LAWBOR_URL set) and settlement (on-chain, if amountMicro given) in
till_create_invoice — Create a Web2-style INVOICE (number, line items, due date, bill-to) on the SAME non-custodial registry: paid by the same EIP-681 intent, verified by the same ch
till_check_invoice — Check an invoice against the chain: settled (paid on-chain, field-for-field) / overdue / issued / not_observable (settles on a rail BIII cannot read — ask the m
till_vet_asset — Is a TOKENIZED ASSET (stock/treasury/RWA) contract the GENUINE issuer's, or an impersonator? genuine / impersonation / unsafe / unknown — fail-closed (unknown i
till_vet_meme — Which contract is the REAL memecoin among 10+ look-alikes? Fail-closed verdict from live market data (DexScreener). Returns: genuine (one contract dominates liq
till_receipt — Produce the chain-anchored receipt for a VERIFIED payment (txHash + basescan link). Refuses without verification.
till_roll — PROVABLE BOOKS: render an agent/merchant's till roll — a shareable statement where EVERY line carries its own txHash + basescan link, so the reader re-verifies
till_export — ACCOUNTING EXPORT: turn the verified receipts into an accountant-ready CSV that QuickBooks / Xero / Excel import (the export finance teams need to adopt). Every
till_meter — USAGE → BILL for a white-label pilot, split by trust. The settled receipts are ON-CHAIN (each txHash re-verifiable on Base — the PROVABLE basis for receipt char
till_floor — DECENTRALIZATION PROOF: the provenance + content-FINGERPRINT of this node's known-bad floor. Two nodes with the SAME fingerprint judge on the SAME floor — samen
till_resolve — IDENTITY BRIDGE: resolve an AGENT identity — a buzz/Nostr npub (64-hex secp256k1) AND/OR a gitlawb did:key (Ed25519) — to a payable, trust-assessable BASE addre
till_kya — IDENTITY STANDARD (interop): read a Skyfire KYA ("Know Your Agent") JWT — the signed token binding a real human/business to an agent (Experian's identity layer)
till_authorize — SPEND AUTHORIZATION (Skyfire Programmable Payment): create a charge AND check it against what the agent's OWNER signed off — token, recipient allow-list, per-ch
till_rug_powers — WHO CAN STILL RUG THIS TOKEN? till_vet_meme says which contract is the real one; this says whether the real one is itself a trap. A dangerous capability only co
till_launch_funder — WHO PAID FOR THIS LAUNCH, AND WHAT ELSE DID THEY PAY FOR? Follows the money backwards: a token names its creator, a creator minted minutes ago names the wallet
till_b20_authentic — IS THIS A REAL BASE-NATIVE B20, OR AN ERC-20 WEARING ITS ADDRESS PREFIX? B20 is Base's native standard for compliant asset issuance (stablecoins, RWA); its toke
till_trace_theft — FOLLOW STOLEN FUNDS from the victim's transaction to where the trail dies. Three modes. moved: what actually left a wallet in one transaction, marking which tra
till_recovery_offer — THE SECOND THEFT: judge an approach offering to recover already-stolen funds. Every other tool here tries to stop the first loss; this exists because the first
till_vet_approach — JUDGE AN INBOUND OPPORTUNITY BY ITS ASK, NOT BY HOW GOOD IT LOOKS (podcast, interview, partnership, job, AMA). Built from a lure that worked on someone who veri
till_open_approvals — WHICH DOORS INTO THIS WALLET ARE STILL OPEN? An ERC-20 approval is a standing permission to move your tokens without asking again, and it is the most common dra
till_watch_wallet — WHAT CHANGED AROUND THIS WALLET SINCE WE LAST LOOKED? The other tools answer at a point in time; this is what turns them into a guard, because it REMEMBERS and
till_vet_agent — IS THIS AGENT SAFE TO CONNECT TO, AND SAFE TO PAY? The gap this closes: everything else here judges tokens, launches, thefts and wallets, but never the AGENT —
till_seed_exposure — IS A RECOVERY PHRASE SITTING IN CLEARTEXT ON THIS MACHINE? Everything else here answers whether an ADDRESS is safe to pay; this answers whether the MACHINE is s
till_key_exposure — WHAT KEY MATERIAL IS ON THIS DISK, AND WHAT STILL HOLDS AN OLD COPY OF IT? The companion to till_seed_exposure, and it exists because a real theft happened with
till_verify_delivery — I CAN PROVE I PAID. CAN I PROVE I WAS SERVED? Every other check here runs before money moves; this is the question after, and it is the one nothing in this mark
till_funder_history — HAS THE WALLET THAT PAID FOR THIS LAUNCH ALREADY KILLED ONE? till_launch_funder reads the graph and tells you a cluster exists; this reads our OWN observation r

when	check	result	http	latency	detail
35 min ago	mcp initialize	ok	200	98 ms	server biii 0.1.0 · protocol 2024-11-05 · 29 tools
8 h ago	mcp initialize	ok	200	98 ms	server biii 0.1.0 · protocol 2024-11-05 · 29 tools
15 h ago	mcp initialize	ok	200	93 ms	server biii 0.1.0 · protocol 2024-11-05 · 29 tools
22 h ago	mcp initialize	ok	200	99 ms	server biii 0.1.0 · protocol 2024-11-05 · 29 tools
29 h ago	mcp initialize	ok	200	99 ms	server biii 0.1.0 · protocol 2024-11-05 · 29 tools
35 h ago	mcp initialize	ok	200	95 ms	server biii 0.1.0 · protocol 2024-11-05 · 29 tools
2 d ago	mcp initialize	ok	200	102 ms	server biii 0.1.0 · protocol 2024-11-05 · 29 tools
2 d ago	mcp initialize	ok	200	99 ms	server biii 0.1.0 · protocol 2024-11-05 · 29 tools
2 d ago	mcp initialize	ok	200	99 ms	server biii 0.1.0 · protocol 2024-11-05 · 29 tools
3 d ago	mcp initialize	ok	200	100 ms	server biii 0.1.0 · protocol 2024-11-05 · 29 tools

biii

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from