Skip to main content
Glama
Safe MCP Server

Safe MCP Server

by 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

Related MCP server: Hermes Blockchain Oracle

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

Available Tools

3 tools
decodeTransactionDataC

Decode transaction data using Safe API

Inputs: data (required), to.

getMultisigTransactionC

Get details of a specific multisig transaction

Inputs: safeTxHash (required).

getSafeTransactionsC

Get all transactions for a Safe address

Inputs: address (required), limit, offset.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.1/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: decodeTransactionData handles data decoding, getMultisigTransaction retrieves a specific transaction, and getSafeTransactions lists all transactions for a Safe. There is no overlap in functionality, making tool selection straightforward.

    Naming Consistency4/5

    The naming follows a consistent verb_noun pattern with camelCase (e.g., decodeTransactionData, getMultisigTransaction). However, the verb 'get' is used for two tools while 'decode' is used for one, which is a minor deviation from perfect uniformity.

    Tool Count3/5

    With only 3 tools, the set feels thin for a Safe MCP server, as it lacks operations like creating or executing transactions, which are core to multisig workflows. The count is borderline for the apparent scope of Safe management.

    Completeness2/5

    The tool surface is significantly incomplete for Safe management, missing essential CRUD operations such as creating, proposing, or executing transactions. This will likely cause agent failures when trying to perform full lifecycle actions on Safes.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers