tctc-mcp
Provides Ethereum blockchain access via Alchemy RPC, enabling the MCP server to query on-chain roles (check_role, list_roles) and execute transactions (grant_role, revoke_role) on ERC-7303 contracts.
Integrates with Ethereum smart contracts implementing ERC-7303 (Token-Controlled Token Circulation), ERC-8004 (Trustless Agents), and ERC-6551 (Token Bound Accounts) to manage role-based permissions for AI agents through on-chain token minting and burning.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@tctc-mcpcheck my current on-chain roles"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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: v1 implemented — unit-tested and verified end-to-end against the Sepolia demo deployment (grant → check → revoke → check through a real MCP client).
Quick start
npm install && npm run build
# read-only mode (agent side): only query tools are registered
ALCHEMY_API_KEY=... node dist/index.js --config examples/config.sepolia.json
# admin mode (principal side): grant_role / revoke_role also registered
ALCHEMY_API_KEY=... TCTC_ADMIN_PRIVATE_KEY=0x... \
node dist/index.js --config examples/config.sepolia.jsonMCP client registration: see
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.
Related MCP server: ows-mcp-wallet
Tools
Tool | Mode | Purpose |
| both | Configured roles and their control tokens |
| both | Does an account hold a role? (live |
| both | Session-start self-assessment across all roles |
| both* | ERC-8004 |
| admin | Mint the control token to a subject |
| 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.
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/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) and the original TCTC reference deployment (
COMPLEX_*roles).examples/contracts/ — sources of the demo contracts deployed on Sepolia (
AgentControlTokens,TCTCDemoToken,ERC7303).
Demo deployment (Sepolia, Etherscan-verified)
AgentControlTokens(soulbound, issuer-burnable ERC-1155):0x12342A7F0190B3AF3F4b47546D34006EDA54eE0BTCTCDemoToken(ERC-721 + ERC-7303 target):0xa52fe39D0de852e88488faa34e723E861D0b09BD
Development
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)Related
TCTC reference implementation: https://github.com/kofujimura/TCTC
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/kofujimura/tctc-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server