Tctc MCP

Name: Tctc MCP
Author: kofujimura

by kofujimuraversion 0.3.3i★ –iRuns on your computer

Registry nameio.github.kofujimura/tctc-mcp

Install

Overview

Description from the maker (original English)

ERC-7303 token-controlled roles for AI agents: grant, check, and revoke permissions on-chain

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
UsageiNot measured yet★ –

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: TCTC_ADMIN_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: TCTC_ADMIN_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": {
    "tctc": {
      "command": "npx",
      "args": [
        "-y",
        "tctc-mcp",
        "--config",
        "your-value"
      ],
      "env": {
        "TCTC_ADMIN_PRIVATE_KEY": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add tctc --env TCTC_ADMIN_PRIVATE_KEY=your-value -- npx -y tctc-mcp --config your-value

Fill in the empty values before running it.

This one needs values on its command line, so copy the settings and fill them in.

Or copy the settings yourself

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

{
  "mcpServers": {
    "tctc": {
      "command": "npx",
      "args": [
        "-y",
        "tctc-mcp",
        "--config",
        "your-value"
      ],
      "env": {
        "TCTC_ADMIN_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 needs values on its command line, so copy the settings and fill them in.

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "tctc": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "tctc-mcp",
        "--config",
        "your-value"
      ],
      "env": {
        "TCTC_ADMIN_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

TCTC_ADMIN_PRIVATE_KEY secret env
Issuer key enabling grant_role/revoke_role (admin mode). Omit for read-only mode: state-changing tools are then not even registered

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 kofujimura, 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 1612 servers in this category
Published to the registry more recently than 31% of the other 1612 servers in this category
Basic checks equal to or better than 100% of the other 1612 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 Tctc MCP 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: TCTC_ADMIN_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.3.3) reached the registry 4 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: NEMO x402 Micro-Services, Crypto Derivatives Data: Perp Funding Rates, Open Interest, Basis, IV, Agent Data Tools: Prices and DeFi

Alternatives

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

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

NEMO x402 Micro-Services

by floortomproductions-droid

34 paid tools: site/SEO, weather, crypto+markets, podcasts, YouTube, Polymarket. x402/MPP/Stripe.

Runs in the cloudUpdated today

Install

Crypto Derivatives Data: Perp Funding Rates, Open Interest, Basis, IV

by derivs.duoleads.com

Perp funding rates, open interest, futures basis, IV, liquidations, order books on 8 exchanges

Runs in the cloudUpdated today

Install

Agent Data Tools: Prices and DeFi

by Nutshell2000

50 tools: token prices, wallet and contract risk, liquidity pools, FX. 25 free calls.

Runs in the cloudUpdated today

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.

tctc-mcp

An MCP server exposing ERC-7303 (Token-Controlled Token Circulation) roles to AI agents: agents check their own on-chain permissions, and human principals grant/revoke them by minting/burning control tokens — no permission server required.

Status: v0.3.4 — adds timed roles with gasless auto-expiry (below), on top of v0.2's IERC7303 auto-discovery; published on npm (tctc-mcp), unit-tested and verified end-to-end against the Sepolia demo deployment (grant → check → revoke → check, and grant-for-75s → auto-expiry, through a real MCP client).

Demo (60 seconds)

*A human grants an AI agent a minting permission; the agent verifies it on-chain and mints an NFT. The human burns the role token — and the agent instantly loses the capability. Live on Sepolia, no permission server involved.*

Quick start

The package is published on npm, so no clone or build is needed — npx fetches and runs it directly:

# 1. Get a config. The secret-free Sepolia demo config needs no API keys:

curl -fsSLO https://raw.githubusercontent.com/kofujimura/tctc-mcp/main/examples/config.sepolia.agent.json

2. Register with your MCP client, e.g. Claude Code

(read-only mode: only query tools are registered)

claude mcp add tctc -- npx -y tctc-mcp --config "$PWD/config.sepolia.agent.json"

Admin mode (principal side): grant_role / revoke_role also registered.

Provide the issuer key ONLY via the environment:

claude mcp add tctc-admin --env TCTC_ADMIN_PRIVATE_KEY=0x... \ -- npx -y tctc-mcp --config "$PWD/config.sepolia.json"

Or in a project-scoped .mcp.json:

{ "mcpServers": { "tctc": { "command": "npx",

"args": ["-y", "tctc-mcp", "--config", "examples/config.sepolia.agent.json"] } } }

A fuller registration example is in examples/claude.mcp.json. The admin private key is only ever read from the TCTC_ADMIN_PRIVATE_KEY environment variable; configs containing anything that looks like a private key are rejected at startup.

Using tctc-mcp from your own app

The only supported entry point is the `tctc-mcp` bin — spawn it via npx --no-install tctc-mcp (or node_modules/.bin/tctc-mcp). Never reference the package's dist/ files directly: they are internal, their layout is unversioned, and the package's exports field refuses deep imports. A minimal MCP-SDK client example (the pattern for a web backend) is in examples/client-stdio.mjs; the release pipeline verifies the packed bin end-to-end (scripts/verify-pack.mjs).

Web application starter

Want to see tctc-mcp protecting a real API route?

tctc-openai-starter is a standalone Next.js starter that verifies wallet ownership with Sign-In with Ethereum, checks the configured role through tctc-mcp, and calls OpenAI only when the on-chain gate grants access.

Use it as a GitHub template.

Token-gating any MCP server: tctc-gate

The reverse direction lives in this repo too: tctc-gate (npm) is a transparent stdio proxy that puts an ERC-7303 role check in front of any existing MCP server, unmodified — deny comes back with a grant URL that opens the dashboard pre-filled. tctc-mcp lets agents *ask* about roles; tctc-gate *enforces* them at the boundary:

npx -y tctc-gate --config gate.json -- npx -y some-mcp-server …

Tools

Tool	Mode	Purpose
`list_roles`	both	Configured roles and their control tokens
`check_role`	both	Does an account hold a role? (live `balanceOf`, with evidence)
`check_all_roles`	both	Session-start self-assessment across all roles
`discover_roles`	both	Introspect any contract via `IERC7303` — no role config needed
`resolve_agent`	both*	ERC-8004 `agentId` → owner / agentURI / agentWallet / ERC-6551 TBA
`grant_role`	admin	Mint the control token to a subject
`revoke_role`	admin	Burn the subject's control token — the kill switch

\* registered only when the config has an identity section.

Subjects can be given as a raw address, as an ERC-8004 agentId (resolved to its ERC-6551 Token Bound Account, the recommended binding target), or omitted to use the config's self.

IERC7303 auto-discovery (v0.2)

ERC-7303 now defines an introspection interface (ethereum/ERCs#1872, merged 2026-07-11): compliant contracts expose hasRole, control-token getters, configuration events, and ERC-165 detection (interfaceId 0x4ee69337). tctc-mcp uses it two ways:

`target` roles — a role config names only the target contract; the server reads which control tokens gate the role *from the contract itself*, and the verdict is the target's own hasRole() answer:

  "roles": { "MINTER_ROLE": {

"target": { "address": "0x4C0a78803D47154B9C6F42EC4AEbab2D1C94c97D" } } }

`discover_roles` — introspect any address at run time, with no role configuration at all. Non-compliant contracts report supportsIERC7303: false; static controlTokens configs remain the fallback for pre-IERC7303 deployments.

Working example: examples/config.sepolia.discovery.json (secret-free, public RPC), verified live by scripts/e2e-discovery.mjs.

Timed roles: gasless auto-expiry (v0.3)

Delegation to an agent is usually *short-term* — "mint for one hour", "act for the duration of this task". With an expiring control token (ExpiringControlTokens), balanceOf() returns 0 once the holder's expiry passes, so the role revokes by itself, with no transaction — even if the principal forgets, goes offline, or loses keys. The ERC-7303 target contract needs no changes at all (the Sepolia expiry demo target is a byte-for-byte copy of TCTCDemoToken).

Granting: a role whose grant template has $expiresAt requires an expiry — grant_role with expiresInSeconds: 3600 is "grant MINTER_ROLE for one hour":

  "admin": { "grant": { "function": "mint(address,uint256,uint64)",

"args": ["$subject", "$typeId", "$expiresAt"] } }

Checking: check_role evidence reports expiresAt (unix seconds) when the control token exposes it, so an agent can self-report "this permission expires in 5 minutes".
Kill switch unchanged: expiry is a fail-safe, not a replacement — revoke_role (issuer burn) still revokes immediately within the validity window.

Working example: the TIMED_MINTER_ROLE in examples/config.sepolia.json, verified live by scripts/e2e-expiry.mjs (grant for 75 s → watch it expire with no further transaction).

Human dashboard

Live: [https://tctc-mcp.vercel.app/](https://tctc-mcp.vercel.app/) — while tctc-mcp exposes ERC-7303 roles to AI agents, the TCTC Dashboard exposes the same on-chain state to the humans who manage them: inspect any IERC7303 target, watch hasRole verdicts and per-control-token balanceOf evidence live, grant/revoke as the issuer (with timed grants and countdowns for expiring control tokens), and deploy new control-token collections straight from a browser wallet. Two clients of one source of truth: the chain. See dashboard/README.md for details and try-it links.

*Not just for AI-agent delegation: any ERC-7303 contract works, so the dashboard doubles as a general-purpose on-chain permission manager — issue certificate collections, grant and revoke roles, and audit who holds what, all from a browser wallet.*

Documents

docs/CONCEPT.md — background and rationale: TCTC as the authorization layer for AI agents, its relationship to ERC-8004 (Trustless Agents) and ERC-6551 (Token Bound Accounts), recommended ERC-7303 spec updates, and the adoption strategy.
docs/MCP_SERVER_SPEC.md — v1 design specification (architecture, config, tools, security, roadmap).
docs/ERC_DRAFT_EXPIRABLE_1155.md — working draft of a planned ERC, "Expirable ERC-1155 Tokens": the standard behind the timed roles above (per-holder expiry, time-aware balanceOf, expiresAt/ExpiryUpdated, interface ID 0x300e616b). Not yet submitted to ethereum/ERCs; feedback welcome.
docs/TEST_REPORT.md — v1 test report: 24 unit tests and the live Sepolia E2E (on-chain kill-switch cycle through a real MCP client).
examples/config.sepolia.json — concrete config for the Sepolia demo deployment (primary roles, static bindings) and the TCTC repo's MyComplexToken sample (COMPLEX_* roles, resolved via IERC7303 target discovery).
examples/config.sepolia.agent.json — secret-free agent-side config for the same demo deployment (public RPC, no API keys); the one used in the Quick start above.
examples/config.sepolia.discovery.json — IERC7303 auto-discovery variant: no control tokens configured, the target contract explains its own role structure.
examples/contracts/ — sources of the demo contracts deployed on Sepolia (AgentControlTokens, TCTCDemoToken, ERC7303, IERC7303).

Demo deployment (Sepolia, Etherscan-verified)

AgentControlTokens (soulbound, issuer-burnable ERC-1155): 0x12342A7F0190B3AF3F4b47546D34006EDA54eE0B
TCTCDemoToken (ERC-721 + ERC-7303 target, implements the IERC7303 introspection interface — hasRole, control-token getters, ERC-165 detectable via interfaceId 0x4ee69337): 0x4C0a78803D47154B9C6F42EC4AEbab2D1C94c97D
ExpiringControlTokens (soulbound, issuer-burnable ERC-1155 with per-holder expiry; time-aware balanceOf — the basis of timed roles): 0xb5abB6c060ed287e8B25aD121c8B46eE404fF09b
Expiry demo target (unmodified TCTCDemoToken bytecode bound to the expiring control tokens): 0x3eAb11DE9655817A2e2977A486d9D33eBD10c9Ce

Development

git clone https://github.com/kofujimura/tctc-mcp.git && cd tctc-mcp

npm install && npm run build node dist/index.js --config examples/config.sepolia.agent.json

npm test # unit tests (vitest) node scripts/e2e-live.mjs # live E2E: spawns the server via MCP stdio client

(needs ALCHEMY_API_KEY; admin phase additionally

TCTC_ADMIN_PRIVATE_KEY and E2E_SUBJECT)

Human dashboard (this repo, dashboard/): https://tctc-mcp.vercel.app/
npm package: https://www.npmjs.com/package/tctc-mcp
tctc-gate — token-gate any existing MCP server, no modification: https://www.npmjs.com/package/tctc-gate
[tctc-openai-starter](https://github.com/kofujimura/tctc-openai-

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

Tctc MCP

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

NEMO x402 Micro-Services

Crypto Derivatives Data: Perp Funding Rates, Open Interest, Basis, IV

Agent Data Tools: Prices and DeFi

README from the maker

tctc-mcp

Demo (60 seconds)

Quick start

2. Register with your MCP client, e.g. Claude Code

(read-only mode: only query tools are registered)

Admin mode (principal side): grant_role / revoke_role also registered.

Provide the issuer key ONLY via the environment:

Using tctc-mcp from your own app

Web application starter

Token-gating any MCP server: tctc-gate

Tools

IERC7303 auto-discovery (v0.2)

Timed roles: gasless auto-expiry (v0.3)

Human dashboard

Documents

Demo deployment (Sepolia, Etherscan-verified)

Development

(needs ALCHEMY_API_KEY; admin phase additionally

TCTC_ADMIN_PRIVATE_KEY and E2E_SUBJECT)

Related