mcpField
M
Moralis

Moralis

Remote
pipeworx.ioFinance0Updated 1d ago

About Moralis

Moralis is an MCP server wrapping the Moralis Web3 Data API for users querying EVM wallet and ERC20 token data. Its tools cover balances, portfolio value, token holders, and decoded transaction history, and require an API key.

Key features

  1. 01Get wallet ERC20 balances and live prices
  2. 02View net worth with per-chain breakdown
  3. 03Find top ERC20 token holders
  4. 04Read decoded wallet transaction history

Use cases

  1. 01Review tokens held by an EVM wallet
  2. 02Analyze ERC20 holder distribution
  3. 03Check recent transfers, swaps, and NFT trades

MCP support

It exposes Moralis Web3 Data API tools to MCP clients for wallet, token-holder, and transaction queries; calls require a user-provided API key.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://gateway.pipeworx.io/moralis/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

mcp-moralis

Moralis MCP — wraps the Moralis Web3 Data API (moralis.com)

Part of Pipeworx — an MCP gateway connecting AI agents to 1683+ live data sources.

Tools

ToolDescription
moralis_wallet_tokensWhat tokens does wallet X hold + USD value — returns ERC20 token balances with live prices for a wallet address on a given EVM chain. Example: moralis_wallet_tokens({ address: "0xcB1C1FdE09f811B294172696404e88E658659905", chain: "eth", _apiKey: "your-key" })
moralis_wallet_net_worthTotal portfolio net worth for wallet X — returns the aggregate USD value of a wallet with a per-chain breakdown. Example: moralis_wallet_net_worth({ address: "0xcB1C1FdE09f811B294172696404e88E658659905", chain: "eth", _apiKey: "your-key" })
moralis_token_holdersTop holders of token X — returns the largest holders of an ERC20 token with balances and ownership percentages. Example: moralis_token_holders({ address: "0xdAC17F958D2ee523a2206206994597C13D831ec7", chain: "eth", _apiKey: "your-key" })
moralis_wallet_historyRecent decoded transactions for wallet X — returns a human-readable, decoded transaction history (sends, receives, swaps, NFT trades) for a wallet. Example: moralis_wallet_history({ address: "0xcB1C1FdE09f811B294172696404e88E658659905", chain: "eth", _apiKey: "your-key" })

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "moralis": {
      "url": "https://gateway.pipeworx.io/moralis/mcp"
    }
  }
}
What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/moralis/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1683+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

This pack takes your own API key (_apiKey) — we don't front one for it, so there's no curl here that would run without it. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/moralis_wallet_tokens. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:

{
  "mcpServers": {
    "moralis": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-moralis"]
    }
  }
}

Or run it directly to confirm it starts:

npx -y @pipeworx/mcp-moralis

It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call for only this pack's tools — none of the shared meta-tools the gateway connection above adds. Same source, same tools, no ask_pipeworx routing.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Moralis data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.