Safe Mcp Server

The Safe MCP Server allows users to interact with Safe smart contract wallets, enabling them to query transaction histories, access multisig details, and decode transaction data easily through an integration with the Safe API.

Author

Safe Mcp Server logo

5ajaki

MIT License

Quick Info

GitHub GitHub Stars 2
NPM Weekly Downloads 0
Tools 1
Last Updated 9/7/2025

Tags

apis api 5ajaki safe api 5ajaki safe requests 5ajaki

Safe MCP Server

An MCP (Model Context Protocol) server implementation for interacting with Safe (formerly Gnosis Safe) smart contract wallets.

Features

  • Query Safe transactions for any Safe address
  • Get multisig transaction details
  • Decode transaction data
  • Safe API integration

Installation

npm install

Usage

npm run build
npm start

No configuration is required - the server uses the Safe Transaction API mainnet endpoint by default.

Available Tools

getSafeTransactions

Get all transactions for any Safe address. The Safe address is determined by the LLM at runtime based on the context of the conversation.

// Example tool call
getSafeTransactions({
  address: "0x123...", // Safe address determined by LLM
  limit: 100, // optional
  offset: 0, // optional
});

getMultisigTransaction

Get details of a specific multisig transaction.

getMultisigTransaction({
  safeTxHash: "0x456...", // Transaction hash to query
});

decodeTransactionData

Decode transaction data using Safe API.

decodeTransactionData({
  data: "0x789...", // Transaction data to decode
  to: "0xabc...", // Optional contract address
});

Configuration (Optional)

By default, the server uses the Safe Transaction API mainnet endpoint:

https://safe-transaction-mainnet.safe.global/api/v1

If you need to use a different endpoint (e.g., for testnet), you can set it via environment variable:

SAFE_API_URL=https://safe-transaction-goerli.safe.global/api/v1 npm start

Development

npm run dev

License

MIT