SqueekKit 🐹

A community TypeScript SDK, MCP server and working demo for Squeekchain.

· Demo walkthrough · Compatibility report · SDK reference · MCP setup

SqueekKit turns Squeekchain's published ABI, deployment and integration rules into reusable tools. An app and an AI assistant share the same deployment checks, integer accounting, eligibility logic and transaction preparation.

Community built; not official or endorsed. Available on Sepolia today; mainnet support is planned pending deployment verification. No private keys, signing or transaction broadcasting. Packages are built locally and are not published to npm.

Try it

Requires Node.js 22.12+ and npm. The default read-only endpoints need no API key.

git clone https://github.com/formless0/squeekkit.git
cd squeekkit
npm ci
npm run check
npm run dev

Open the local URL printed by Vite. Current testnet is the default screen: live verified reads, real wallet/deposited-NFT portfolios and unsigned claim/merge simulations. The older documented deployment and the explicitly simulated merge lab remain separate. Saved snapshots are labeled recorded until refreshed.

Related MCP server: @shieldlabs-ai/mcp

What is included

Network support

v0.2.0 works with the current Sepolia app using Core v3, Mining v8 and Staking v1.

Mainnet is the next network target. Once the official deployment is published, the integration can be updated with its chain ID, contract addresses, code identities, governance, configuration and API endpoints. Any changed interfaces or reward rules need adapter updates and regression tests before a mainnet-compatible SDK/MCP release. The current clients enforce Sepolia, so changing the RPC URL alone does not enable mainnet. The official deployment documentation currently lists Sepolia; this status was checked on October 27, 2026.

The current-app profile is community-observed and reviewed, with ABI interfaces extracted as static data from the official app, recorded source hashes, pinned runtime identities, governance, configuration and contract links. It is not an official deployment manifest or security audit. It does not automatically trust addresses returned by an API. Current profile, supported operations and evidence.

The current-app profile passed real eth_call claim and merge simulations for the public protocol reserve. The reserve claim paid zero in simulation; the merge simulation succeeded. Neither was signed or broadcast. Current live receipts.

createSqueekKit() and the original unprefixed MCP tools retain the developer docs' older Core v3 / Mining v6 deployment. Use createCurrentTestnet() for the current app.

On October 27, 2026, checks of that older deployment found:

• The documented proxy code identities and contract connections still matched, but the onchain reporter differed from the manifest. Strict verification and action preparation correctly reject that drift.

• The public API was serving a different core deployment. Its mining-state endpoint returned 404. The SDK refuses to combine those responses with the pinned economy.

• chain.auditProtocol() still provides a diagnostic read after code/ABI/link checks, with snapshot.verified: false and explicit configuration differences. It never enables transaction preparation.

Those findings concern the legacy profile. Its saved audit does not claim a successful live action. Legacy evidence.

SDK example

After building, workspace packages resolve locally:

import { createCurrentTestnet, CURRENT_TESTNET, stringify } from '@squeekkit/sdk';

const squeek = createCurrentTestnet();
const protocol = await squeek.chain.protocol();
console.log(protocol.snapshot, protocol.core.blockHeight);

// Read-only public protocol-reserve example; no claim of wallet control.
const owner = CURRENT_TESTNET.links['nft.protocolRecipient'];
console.log(stringify(await squeek.api.portfolio(owner)));
console.log(stringify(await squeek.chain.account(owner)));

// Current rewards belong to the account, so no NFT IDs are passed to claim.
const prepared = await squeek.chain.prepareClaim(owner);
console.log(prepared.recipient, stringify(prepared.bundle));
// This only simulates. Only the actual owner can approve/sign in their wallet.

All action inputs are re-read onchain at a fresh, verified block; simulation uses that same block. A final canonical-block and freshness check runs before returning a bundle. State can still change before inclusion, so re-prepare immediately before signing.

MCP setup

After npm run build, add this to a compatible client's MCP server configuration. Replace the path with the absolute checkout path (Windows accepts forward slashes).

{
  "mcpServers": {
    "squeekkit": {
      "command": "node",
      "args": ["/absolute/path/to/squeekkit/packages/mcp/dist/cli.js"]
    }
  }
}

Try: “Use current_testnet_status, then inspect my account and deposited NFTs. Include source blocks and do not sign or send anything.”

The agent skill published by Squeekchain teaches an agent the protocol. This MCP server complements it with callable, tested operations. The MCP layer cannot accept keys, sign, broadcast or invoke arbitrary RPC methods. The tool inspector in the web demo calls the underlying SDK; npm run test:mcp tests the actual stdio transport.

Verification

npm run check          # strict types, unit/integration tests, builds, real MCP stdio smoke
npm run test:coverage  # SDK + MCP coverage report
npx playwright install chromium
npm run test:browser   # deterministic desktop/mobile browser regressions
npm run test:live      # optional real network compatibility check (never sends)
npm run test:live:current # current app reads + unsigned claim/merge simulations

test:live writes docs/evidence/live-verification.json and intentionally exits nonzero if strict deployment verification fails. Live availability is not required for deterministic CI. See TESTING.md for the test matrix and limits.

Design choices

• One block per snapshot: hash, number, timestamp and deployment travel with chain results; reorgs invalidate the read.

• Big integers throughout: no floating-point accounting. Current account rewards and legacy per-NFT rewards remain separate.

• Owner/custody checks: every explicitly selected NFT is checked onchain, including its staking depositor where applicable. Deposits require existing approvals; the toolkit does not grant approvals.

• Merge intent is explicit: survivor and donor order is preserved, with a permanent-burn warning in the output.

• No silent migration: changed implementations, layouts, governance or deployment links stop verification. Diagnostic configuration drift is marked unverified.

• API uncertainty stays uncertainty: unavailable, wrong-deployment, incomplete pagination and malformed data never become a zero balance. Retries are bounded and honor short Retry-After values; longer delays are surfaced to callers.

Scope

This release supports current-app Genesis NFTs and account rewards, plus the older documented Squeeks collection (collection = 0). Current NFT deposits/withdrawals are supported; SQK stake/unstake, clones, gacha, minting, autonomous keepers, arbitrary contracts and a full event indexer are outside this release. It has not undergone an independent security audit.

Contributing

See CONTRIBUTING.md, SECURITY.md and third-party notices. Original SqueekKit code is MIT licensed.