Skip to main content
Glama
kukapay

tornado-cash-mcp

by kukapay
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
query_latest_depositsA
Query the most recent deposits from Tornado Cash Subgraph and return results as a formatted table.

Parameters:
    limits (int): The maximum number of deposit records to return. Must be positive. Default is 10.

Returns:
    A string containing a tabulated representation of deposit records with columns: id, amount, timestamp, commitment, blockNumber, from.
query_latest_withdrawalsB
Query the most recent withdrawals from Tornado Cash Subgraph and return results as a formatted table.

Parameters:
    limits (int): The maximum number of withdrawal records to return. Must be positive. Default is 10.

Returns:
    A string containing a tabulated representation of withdrawal records with columns: id, amount, timestamp, to, blockNumber.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.5/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: one queries deposits and the other queries withdrawals. There is no overlap or ambiguity between them, as each targets a different transaction type within the Tornado Cash domain.

Naming Consistency5/5

Both tools follow a consistent verb_noun pattern with 'query_latest_' prefix followed by the transaction type. This predictable naming scheme makes it easy to understand what each tool does at a glance.

Tool Count2/5

With only 2 tools, this server feels significantly under-scoped for a Tornado Cash integration. While deposits and withdrawals are core operations, a complete MCP server for this domain would typically include tools for other operations like querying specific transactions, getting pool statistics, or interacting with smart contracts.

Completeness2/5

The tool surface is severely incomplete for a Tornado Cash server. While it covers basic querying of deposits and withdrawals, there are significant gaps including: no ability to query specific transactions by ID, no tools for interacting with pools or contracts, no filtering capabilities beyond simple limits, and no write operations that might be expected in a privacy tool integration.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources