Home / MCP registry index / shop.grokzilla/micro-pay

Grokzilla micro pay

shop.grokzilla/micro-pay in the official MCP registry. Endpoint https://grokzilla.shop/mcp. Source: github.com/nicsins/ai-micro-pay.

The registry describes it as: 32 x402 pay-per-call tools: SEO, agent audits, JSON/text utils, OSINT. USDC on Base; $1=300 calls

Connect it

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

claude mcp add --transport http micro-pay https://grokzilla.shop/mcp

{
  "mcpServers": {
    "micro-pay": {
      "url": "https://grokzilla.shop/mcp"
    }
  }
}

code --add-mcp '{"name":"micro-pay","type":"http","url":"https://grokzilla.shop/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.

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

Tools it advertises

list_skills get_skill osint_graph seo seo_v2 seo_compare agent_ready_audit agent_ready_kit agent_ready_recheck ai_detector json_flatten json_sort text_diff url_normalize html_clean json_schema_validate keyword_extract token_count sha256 uuid_mint slugify pii_redact csv_normalize base64 epoch_convert url_to_markdown token_risk json_repair cron_next token_price email_check news_brief ip_intel llm_cost_quote address_validate gas_price erc20_meta dns_lookup name_resolve tx_status hex_decode block_number whois_rdap

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-10-30): fde9ab1bcb647875. 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.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/shop-grokzilla-micro-pay/badge.svg)](https://lazaretto.dev/mcp-registry/shop-grokzilla-micro-pay)

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. What we found across the registry.

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

Related

Crypto and Web3 MCP servers · Analytics and SEO MCP servers