Home / MCP registry index / com.amazap/amazap
Amazap
com.amazap/amazap in the official MCP registry.
Endpoint https://amazap.com/mcp.
The registry describes it as: Save money on AI spend. Agents buy compact pay-per-call tools from one prepaid credit balance.
We read its 24 tools on 2026-10-26. 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 every week.
Tools it advertises
read_webpage lightning_node lightning_liquidity read_feed make_qr squeeze_log page_metadata read_pdf repo_digest search_catalog describe_sku quote buy buy_best orders get_order claim_failed_call balance spend_summary top_up catalog_stats report_outcome report_sku list_my_endpoint
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-amazap-amazap)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.