Home / MCP registry index / dev.moneytools/tools

MoneyTools Tools

dev.moneytools/tools in the official MCP registry. Endpoint https://tools.moneytools.dev/mcp.

The registry describes it as: 25 read-only agent utilities: token safety, approvals, tx decode, EIP-712 risk, DNS, time; free tier

We read its 105 tools on 2026-11-04. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again about every two weeks.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http tools https://tools.moneytools.dev/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "tools": {
      "url": "https://tools.moneytools.dev/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"tools","type":"http","url":"https://tools.moneytools.dev/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

token_safety_check address_profile ens_resolve gas_compare erc20_info allowance_revoke_plan tx_explain calldata_decode contract_abi signature_verify typed_data_risk x402_validate http_inspect url_metadata dns_lookup domain_rdap robots_check json_schema_validate time_convert cron_next_runs currency_convert unit_convert hash_encode qr_payment_link nft_metadata tx_status block_at_time rpc_health chain_info stablecoin_peg bridge_status dex_price safe_multisig_info contract_read abi_encode proxy_inspect event_logs token_balances ens_available erc4626_vault address_validate solana_account btc_address btc_fees vesting_schedule apr_apy liquidation_price impermanent_loss loan_amortization security_headers_audit ssl_certificate og_image_check sitemap_parse feed_parse broken_links dns_propagation spf_dmarc_check ip_owner url_parse_clean idn_homograph_check and 45 more

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-04): a6801a06e821580d. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.

Run this server? Show the check in your README

The badge reflects the latest read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/dev-moneytools-tools/badge.svg)](https://lazaretto.dev/mcp-registry/dev-moneytools-tools)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. How tool poisoning works. What we found across the registry. Check another server.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.