Safe MCP Server

Created By
5ajakia year ago
An MCP server implementation for interacting with Safe (Gnosis Safe) smart contract wallets
Overview

what is Safe MCP Server?

Safe MCP Server is an implementation of an MCP (Model Context Protocol) server designed for interacting with Safe (formerly Gnosis Safe) smart contract wallets.

how to use Safe MCP Server?

To use Safe MCP Server, install the package using npm, build the project, and start the server. No configuration is required as it defaults to the Safe Transaction API mainnet endpoint.

key features of Safe MCP Server?

  • Query Safe transactions for any Safe address
  • Retrieve multisig transaction details
  • Decode transaction data
  • Integration with Safe API

use cases of Safe MCP Server?

  1. Managing and querying transactions for Gnosis Safe wallets.
  2. Analyzing multisig transaction details for auditing purposes.
  3. Decoding transaction data for better understanding of smart contract interactions.

FAQ from Safe MCP Server?

  • Can I use Safe MCP Server for testnets?

Yes! You can configure the server to use different endpoints for testnets by setting the SAFE_API_URL environment variable.

  • Is there any configuration needed to start the server?

No, the server uses the Safe Transaction API mainnet endpoint by default, requiring no additional configuration.

  • What programming language is used for Safe MCP Server?

Safe MCP Server is built using JavaScript and runs on Node.js.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
5ajaki
Star
-
Language
-
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