Hands: 138+ tools. One link.

Add Zambo once, then just ask your AI for what you need. You never have to name a tool.

Free limits differ by tool. The lead finder shows how many searches you have left in its result.

Limits are per tool, per day. No signup.

One connection

{"mcpServers":{"zambo":{"url":"https://zambo.dev/mcp"}}}

The cards above use names from the live catalog. For a broader request, start with zambo_universal; for a named capability, use capability_search.

Once you have picked the tools that fit your workflow, the $0.99 Day Pass provides 24 hours of listed access from the moment it starts. It is a separate, explicit access choice; free limits vary by tool and are listed above.

Tool contracts in plain language

zambo_universal is the broad entry point for a natural-language need. It routes the request to an available live capability, preserves a stable session when the workflow supports one, and reports whether the result is verified, previewed, blocked, or unavailable. Use it when the task is clearer than the exact tool name.

live_price looks up a supported cryptocurrency through live providers. Its response identifies the observed market data and makes a provider fallback or unavailable state explicit instead of filling a gap with an invented value. Use it when the question is about a current supported asset.

leadsignal searches for source-backed public opportunities for a stated market or location. The useful output is the source-backed lead information and its evidence context, not an unsupported claim about a private person or a result that was not observed.

provibe_audit reviews a repository or code sample for risks, technical debt, and an actionable plan. It is an audit of the supplied code or repository context. The returned findings should be read as observations and recommendations, not as a claim that a change was applied.

ghost_audit_site starts a staged website audit across SEO, AI discoverability, conversion, and presence gaps. Use ghost_audit_status to check the state of an audit already started, then use ghost_audit_report to retrieve completed findings and their evidence.

credithunt searches verified business credit programs and returns source-backed eligibility details. It is designed for discovery and comparison; the source details and eligibility conditions still need review before an application or financial decision.

prompt_shield analyzes prompt injection, jailbreak, and policy-bypass attempts. It gives a safety-oriented assessment of the supplied text and can issue a certificate when the request asks for one. It does not make the surrounding application safe by itself.

day_pass_activate starts or completes the verified day-pass access flow for a calling agent. The payment challenge and activation state are returned by the live access flow. Do not treat a request for activation as proof that payment settled until the returned state confirms it.

capability_search searches the supported catalog for the tool that best fits a use case. It is the discovery tool to use when you know what you want to accomplish but not which named capability should handle it.

Call, inspect, continue

All of these tools use the same Streamable HTTP MCP endpoint: https://zambo.dev/mcp. A client sends a JSON-RPC tools/call request with the live catalog name and the arguments shown by tools/list. The response includes the result and, for completed calls, a verifiable receipt with a stable public identity.

The receipt is part of the execution contract. It records what tool ran, when the record was created, the observed result, and the integrity material needed for later checking. A receipt does not turn a preview into a completed action, does not prove an outside outcome the server did not observe, and does not replace source review for evidence-backed tools.

When a call is blocked, paused, or waiting for access, keep the same job or session context and follow the returned recovery instruction. Do not start a duplicate task just because the first response needs a human payment or connection step. After the access step is complete, retry the same intended work and inspect the new receipt.

For the exact machine contract, call tools/list on the endpoint. The live catalog is authoritative for names, required arguments, output shapes, access scope, side effects, and idempotency. This page keeps a human-readable inventory of the named tools; it does not replace the protocol catalog.

Free connection and verification

Start without an account by adding the endpoint in the install guide. Free limits vary by tool; the cards above show each default limit. A call that completes leaves a verifiable receipt, and the public receipt page exposes the identity and verification route so another person or AI client can inspect the same execution later.

If you need 24 hours of listed access after choosing your tools, use the Day Pass. If you are evaluating the tool catalog, the execution receipt guide explains the evidence boundary and the difference between an observed execution record and a claim about the outside world.