MCPChain

Created By
Deeptanshu-sankhwara year ago
MCPChain brings the Model Context Protocol to Web3 by anchoring agent tools, trust registries, and attestable executions on-chain.
Overview

what is MCPChain?

MCPChain is a blockchain project that implements the Model Context Protocol in the Web3 space, enabling the anchoring of agent tools, trust registries, and attestable executions on-chain.

how to use MCPChain?

To use MCPChain, developers can integrate the Model Context Protocol into their Web3 applications by following the documentation available on the project's GitHub page.

key features of MCPChain?

  • Integration of agent tools for enhanced functionality in decentralized applications.
  • Trust registries that ensure the reliability of on-chain interactions.
  • Attestable executions that provide verifiable outcomes for transactions.

use cases of MCPChain?

  1. Building decentralized applications that require trust and verification.
  2. Implementing AI agents that operate within a secure blockchain environment.
  3. Creating systems that require reliable execution of smart contracts.

FAQ from MCPChain?

  • What is the Model Context Protocol?

The Model Context Protocol is a framework that allows for the integration of various agent tools and trust mechanisms in decentralized applications.

  • Is MCPChain open source?

Yes! MCPChain is open source and available on GitHub.

  • What programming language is MCPChain built with?

MCPChain is developed using the Go programming language.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Deeptanshu-sankhwar
Star
0
Language
Go
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago