Zambo
Server Details
Trust Layer for AI work. Give your AI hands. Every run returns a verifiable receipt. No key needed.
- Status
- Healthy
- Uptime
- 100.0% over 18 days
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
TDQS
Scored across 19 tools
Most tools target clearly distinct domains (audits, leads, prices, PDF extraction, prompt defense), and the continuity_* family, while sharing similar names, is differentiated by descriptions. The main overlaps are capability_search vs zambo_universal (both discover/route across the catalog) and new_session vs continuity_start_thread (both manage session IDs), which could cause misselection.
All names use snake_case, which is consistent, but grouping is uneven: some families carry domain prefixes (continuity_*, ghost_audit_*), while others are bare or concatenated (credithunt, leadsignal, provibe_audit, day_pass_activate). Readable overall, but the namespace convention is not predictable.
19 tools is slightly heavy but justified for a multi-service platform spanning continuity, audits, lead gen, market data, and utilities. Each tool maps to a plausible distinct operation, though a few (capability_search, zambo_universal) feel redundant at this count.
Coverage is strong within domains: ghost_audit has site/status/report lifecycle, continuity has start/list/open/get/set_prefs, and utilities like pdf_extract, prompt_shield, and live_price cover common needs. Minor gaps exist (no thread close/delete, no access/payment status query), but agents can work around them.
Available Tools
27 toolscapability_searchCapability SearchRead-onlyIdempotentInspect
Search across the supported Zambo tool catalog for a use case. Returns relevant tools with relevance scores, descriptions, taglines, and callable API endpoints.
| Name | Required | Description | Default |
|---|---|---|---|
| q | No | Search keyword or phrase. Also accepts the natural aliases query, keyword, or search. Example: 'code audit', 'prompt injection defense', 'wallet scoring', 'lead generation', 'trust verification' | |
| query | No | Alias for q. Use q when possible. | |
| search | No | Natural-language alias for q. | |
| keyword | No | Natural-language alias for q. | |
| _zambo_key | No | Optional opaque Zambo access capability. Never place it in a URL or public log. | |
| _session_id | No | Optional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together. | |
| _caller_label | No | Optional caller label recorded as a caller-reported claim in the receipt. | |
| _continuity_ai_label | No | Optional self-reported AI client label for the private continuity timeline. Zambo does not independently verify the client. |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes | The tool's observed JSON value or plain-text result. |
continuity_get_recentContinuity: get recentRead-onlyIdempotentInspect
Reads only the private receipt timeline for the supplied job or thread ID. Returns receipt links, has_more, and a cursor for the next page. Use since to filter by an inclusive RFC3339 timestamp. Optional AI client labels are self-reported, not verified.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum receipt-backed events to return. Defaults to 20. | |
| since | No | Optional inclusive RFC3339 timestamp lower bound. Keep it unchanged while following a cursor. | |
| cursor | No | Opaque next-page cursor returned by the previous continuity_get_recent result. | |
| ai_filter | No | Optional self-reported AI client label to match, or 'unreported'. | |
| thread_id | No | Optional named thread ID. If omitted, reads the job and its named threads. | |
| _zambo_key | No | Optional opaque Zambo access capability. Never place it in a URL or public log. | |
| session_id | No | Alias for _session_id. | |
| _session_id | No | Optional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together. | |
| _caller_label | No | Optional caller label recorded as a caller-reported claim in the receipt. | |
| _continuity_ai_label | No | Optional self-reported AI client label for the private continuity timeline. Zambo does not independently verify the client. |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes | The tool's observed JSON value or plain-text result. |
continuity_list_threadsContinuity List ThreadsRead-onlyIdempotentInspect
Lists named threads owned by the supplied job ID. Thread IDs can be used as _session_id by another AI client.
| Name | Required | Description | Default |
|---|---|---|---|
| _zambo_key | No | Optional opaque Zambo access capability. Never place it in a URL or public log. | |
| session_id | No | Alias for _session_id. | |
| _session_id | No | Optional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together. | |
| _caller_label | No | Optional caller label recorded as a caller-reported claim in the receipt. | |
| _continuity_ai_label | No | Optional self-reported AI client label for the private continuity timeline. Zambo does not independently verify the client. |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes | The tool's observed JSON value or plain-text result. |
continuity_open_threadContinuity Open ThreadRead-onlyIdempotentInspect
Opens a named thread or thread ID and returns only events with stored Zambo receipts, including links to open and check each receipt.
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | Thread name under the supplied job ID. | |
| limit | No | Maximum events to return. Defaults to 100. | |
| thread_id | No | Thread ID returned by continuity_start_thread. | |
| _zambo_key | No | Optional opaque Zambo access capability. Never place it in a URL or public log. | |
| session_id | No | Alias for _session_id. | |
| _session_id | No | Optional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together. | |
| _caller_label | No | Optional caller label recorded as a caller-reported claim in the receipt. | |
| _continuity_ai_label | No | Optional self-reported AI client label for the private continuity timeline. Zambo does not independently verify the client. |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes | The tool's observed JSON value or plain-text result. |
continuity_set_prefsContinuity: set prefsDestructiveIdempotentInspect
Changes whether future successful calls are captured in the private timeline. It does not remove or hide public receipts already created.
| Name | Required | Description | Default |
|---|---|---|---|
| ai_label | No | Optional self-reported client label for a per-AI setting. It is not verified. | |
| thread_id | No | Optional named thread ID for a thread-specific setting. | |
| _zambo_key | No | Optional opaque Zambo access capability. Never place it in a URL or public log. | |
| session_id | No | Alias for _session_id. | |
| _session_id | No | Optional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together. | |
| _caller_label | No | Optional caller label recorded as a caller-reported claim in the receipt. | |
| capture_enabled | Yes | Whether future successful calls should appear in this private timeline. | |
| _continuity_ai_label | No | Optional self-reported AI client label for the private continuity timeline. Zambo does not independently verify the client. |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes | The tool's observed JSON value or plain-text result. |
continuity_start_threadContinuity Start ThreadDestructiveIdempotentInspect
Creates or reuses a named thread under an existing job ID. Pass the returned thread_id as _session_id to append work from another AI client.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Short name that another AI can use to identify this work thread. | |
| _zambo_key | No | Optional opaque Zambo access capability. Never place it in a URL or public log. | |
| session_id | No | Alias for _session_id. | |
| _session_id | No | Optional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together. | |
| _caller_label | No | Optional caller label recorded as a caller-reported claim in the receipt. | |
| _continuity_ai_label | No | Optional self-reported AI client label for the private continuity timeline. Zambo does not independently verify the client. |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes | The tool's observed JSON value or plain-text result. |
credithuntCredithuntRead-onlyIdempotentInspect
Live verified index of AI and cloud startup credit programs. Accepts optional stack, stage, and minimum value filters. Returns count, updated_at, opportunities, and api.
| Name | Required | Description | Default |
|---|---|---|---|
| stack | No | Optional stack filter. Example: ["openai","vercel","aws"]. Leave empty to include all programs. | |
| stage | No | Your stage: solo (1 person), early (2 to 10), growth (10+). Default: solo. | |
| min_value | No | Minimum credit value in USD to filter by (optional). Example: 5000 | |
| _zambo_key | No | Optional opaque Zambo access capability. Never place it in a URL or public log. | |
| _session_id | No | Optional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together. | |
| _caller_label | No | Optional caller label recorded as a caller-reported claim in the receipt. | |
| _continuity_ai_label | No | Optional self-reported AI client label for the private continuity timeline. Zambo does not independently verify the client. |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes | The tool's observed JSON value or plain-text result. |
day_pass_activateDay Pass activateDestructiveInspect
Agent-native access activation endpoint. Accepts an optional payment envelope or existing access key and returns a payment challenge or verified activation result. Activation results include receipt URL, run ID, access key, expiration, usage guidance, and a spend receipt. Activation occurs only after a verified transfer.
| Name | Required | Description | Default |
|---|---|---|---|
| sponsor | No | Explicitly sponsor another team's closed workflow; branding ownership never transfers. | |
| x_payment | No | Base64 JSON x402 payment envelope signed from the live challenge, sent as X-Payment. | |
| _zambo_key | No | Optional opaque Zambo access capability. Never place it in a URL or public log. | |
| session_id | No | Alias for _session_id. | |
| _session_id | No | Optional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together. | |
| workflow_id | No | Optional workflow to seal after verified payment. | |
| _caller_label | No | Optional caller label recorded as a caller-reported claim in the receipt. | |
| _continuity_ai_label | No | Optional self-reported AI client label for the private continuity timeline. Zambo does not independently verify the client. |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes | The tool's observed JSON value or plain-text result. |
day_pass_checkout_linkDAY Pass Checkout LinkARead-onlyIdempotentInspect
Create a 30-minute short link for a human-approved $0.99, 24-hour Day Pass by card or PayPal. Optional workflow_id targets a closed run; sponsor:true explicitly lets you pay to seal another team's run without transferring branding ownership. The link is not an order or charge.
| Name | Required | Description | Default |
|---|---|---|---|
| sponsor | No | Explicitly sponsor a closed workflow owned by another session; this never grants branding access. | |
| _zambo_key | No | Optional opaque Zambo access capability. Never place it in a URL or public log. | |
| session_id | No | Alias for _session_id. | |
| _session_id | No | Optional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together. | |
| workflow_id | No | Optional closed workflow to seal after payment. | |
| _caller_label | No | Optional caller label recorded as a caller-reported claim in the receipt. | |
| human_approved | Yes | Must be true only after the human explicitly agrees to receive a checkout link. | |
| _continuity_ai_label | No | Optional self-reported AI client label for the private continuity timeline. Zambo does not independently verify the client. | |
| workflow_manage_token | No | Optional private workflow capability. Never share it in public. |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes | The tool's observed JSON value or plain-text result. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the bar is lower, yet the description adds real context: the link expires in 30 minutes, it is not an order or charge, and sponsoring never transfers branding ownership. It does not cover rate limits or what the receipt/response contains, but the added behavioral framing is substantive.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three dense sentences with no boilerplate; the core action, price, expiry and payment methods are front-loaded before the optional parameters. It is efficient, though the 'seal a run' / 'branding ownership' phrasing assumes domain familiarity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a link-generation tool with an output schema and fully documented parameters, the description supplies the non-obvious operational facts an agent needs: approval gate, expiry, and that no order or charge results. Nothing critical is missing, though it does not address what to do after the link is issued.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% across all 9 parameters, so the schema carries the documentation burden and baseline is 3. The description only elaborates on workflow_id and sponsor, and its sponsor explanation largely restates the schema's own wording ('never grants branding access'), adding little beyond structured fields.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description gives a precise verb and resource: creating a 30-minute short link for a $0.99, 24-hour Day Pass payable by card or PayPal, with the human-approval gate stated up front. That is clearly distinguishable from day_pass_activate and day_pass_status, though no sibling is named explicitly, so it stops short of a 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explains the two conditional paths: workflow_id targets a closed run to seal after payment, and sponsor:true lets the caller pay to seal another team's run without gaining branding ownership. The human-approval precondition is stated as part of 'human-approved'. It never names an alternative tool or an explicit when-not-to-use case, so 4 rather than 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
day_pass_statusDay Pass statusARead-onlyIdempotentInspect
Check a Day Pass using _zambo_key, X-Zambo-Key, or the same _session_id used at card checkout or x402 payment. Returns active, expires_at, and calls_left without spending quota. Gateway calls are unmetered while active; product/provider limits may still apply. Never returns the key.
| Name | Required | Description | Default |
|---|---|---|---|
| _zambo_key | No | Optional opaque Zambo access capability. Never place it in a URL or public log. | |
| session_id | No | Alias for _session_id. | |
| _session_id | No | Optional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together. | |
| status_token | No | Opaque token returned with the human checkout link; it is not the Day Pass key. | |
| _caller_label | No | Optional caller label recorded as a caller-reported claim in the receipt. | |
| _continuity_ai_label | No | Optional self-reported AI client label for the private continuity timeline. Zambo does not independently verify the client. |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Adds real behavior beyond the annotations: it does not consume quota, gateway calls are unmetered while active but product/provider limits may still apply, and it never returns the key. These are meaningful operational and security traits that the readOnly/idempotent hints alone do not convey.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Four tight sentences, front-loaded with the credential options and the non-quota-spending behavior. The return-field enumeration slightly duplicates the output schema but remains compact.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a six-parameter, zero-required auth-check tool with an output schema and rich annotations, the description covers the credential alternatives, quota semantics, and the key-safety guarantee. Nothing needed to call it correctly is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the baseline is 3, but the description adds value by explaining that the key can arrive via _zambo_key or the X-Zambo-Key header and by tying _session_id to the checkout/payment flow. It stops short of clarifying how status_token relates to the other credential inputs.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('Check a Day Pass') and names the accepted credentials plus the fields returned (active, expires_at, calls_left). It is clearly distinct from siblings like day_pass_activate and day_pass_checkout_link, though it never names those siblings explicitly to route the agent.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives concrete usage context: which identifiers are accepted (_zambo_key, X-Zambo-Key header, or the same _session_id used at checkout/x402 payment). It does not state when-not-to-use or point to alternatives such as day_pass_activate or day_pass_checkout_link.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
ghost_audit_reportGhost Audit ReportRead-onlyIdempotentInspect
Full markdown report for a completed Ghost Audit. Returns the Achilles 10-stage score, severity-ranked findings, stage analysis, and recommended fixes.
| Name | Required | Description | Default |
|---|---|---|---|
| audit_id | Yes | The audit_id returned by ghost_audit_site | |
| _zambo_key | No | Optional opaque Zambo access capability. Never place it in a URL or public log. | |
| _session_id | No | Optional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together. | |
| _caller_label | No | Optional caller label recorded as a caller-reported claim in the receipt. | |
| _continuity_ai_label | No | Optional self-reported AI client label for the private continuity timeline. Zambo does not independently verify the client. |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes | The tool's observed JSON value or plain-text result. |
ghost_audit_siteGhost Audit SiteDestructiveInspect
Achilles 10-stage audit for a website. Returns SEO gaps, AI discoverability issues, conversion leaks, brand-presence gaps, competitor intelligence, a score from 0 to 100, stage findings, an audit ID, a live stream URL, and a report URL.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Full website URL to audit (e.g., https://yoursite.com). Include https://. | |
| No | Optional email tied to an active Zambo Pass or Day Pass for unlimited audits. | ||
| _zambo_key | No | Optional opaque Zambo access capability. Never place it in a URL or public log. | |
| _session_id | No | Optional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together. | |
| _caller_label | No | Optional caller label recorded as a caller-reported claim in the receipt. | |
| _continuity_ai_label | No | Optional self-reported AI client label for the private continuity timeline. Zambo does not independently verify the client. |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes | The tool's observed JSON value or plain-text result. |
ghost_audit_statusGhost Audit StatusRead-onlyIdempotentInspect
Status report for a Ghost Audit identified by audit_id. Returns whether the audit is running or complete, along with elapsed-time information and report availability.
| Name | Required | Description | Default |
|---|---|---|---|
| audit_id | Yes | The audit_id returned by ghost_audit_site | |
| _zambo_key | No | Optional opaque Zambo access capability. Never place it in a URL or public log. | |
| _session_id | No | Optional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together. | |
| _caller_label | No | Optional caller label recorded as a caller-reported claim in the receipt. | |
| _continuity_ai_label | No | Optional self-reported AI client label for the private continuity timeline. Zambo does not independently verify the client. |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes | The tool's observed JSON value or plain-text result. |
handoverHandoverARead-onlyIdempotentInspect
Package the work from this session (or any continuity thread) into one client-ready link with a verifiable receipt for each step, an in-browser hash check, which AI ran each step, what was not checked, and Accept/Flag buttons. Use when the user says 'Use zambo to hand this over to '.
| Name | Required | Description | Default |
|---|---|---|---|
| goal | No | ||
| anchor | No | ||
| redact | No | ||
| shield | No | ||
| dry_run | No | ||
| not_run | No | ||
| payment | No | ||
| summary | No | ||
| branding | No | ||
| recipient | Yes | ||
| thread_id | No | ||
| _zambo_key | No | Optional opaque Zambo access capability. Never place it in a URL or public log. | |
| visibility | No | public | |
| _session_id | No | Optional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together. | |
| not_checked | No | ||
| receipt_ids | No | ||
| deliverables | No | ||
| _caller_label | No | Optional caller label recorded as a caller-reported claim in the receipt. | |
| exclude_receipt_ids | No | ||
| _continuity_ai_label | No | Optional self-reported AI client label for the private continuity timeline. Zambo does not independently verify the client. | |
| acknowledge_warnings | No | Publish only after reviewing missing evidence or a failed/risky shield scan. Warning labels stay visible. |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes | The tool's observed JSON value or plain-text result. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and non-destructive, but the description adds real behavioral texture: the link carries per-step receipts, an in-browser hash check, which AI ran each step, and an explicit 'what was not checked' surface. It does not mention that the handover is published (visibility defaults to public) or that a Zambo access capability may be required, which matters for a tool whose output leaves the machine.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, zero filler, with the artifact definition front-loaded before the invocation trigger. The middle clause stacks a long list of package contents, but every item adds a distinct capability the agent would otherwise miss.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return values need not be described, and the description covers the trigger plus the shape of the deliverable. For a 21-parameter tool with nested redaction, payment, branding and deliverable objects, though, the absent explanation of the safety- and disclosure-relevant parameters (redact, shield, visibility, dry_run, acknowledge_warnings) leaves the definition short of what an agent needs to invoke it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 24% across 21 parameters, so the schema is doing very little work and the description must compensate — yet it names no parameter at all. High-impact inputs such as redact mode/auto_pii, shield, dry_run, visibility, payment, not_run/not_checked, and acknowledge_warnings are left entirely to the agent's inference from bare property names.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and artifact — 'Package the work from this session ... into one client-ready link' — and enumerates what the package contains (receipts, hash check, AI attribution, unchecked items, Accept/Flag buttons). That is far more than the title 'Handover' conveys. It stops short of differentiating itself from siblings handover_list and handover_status, so the agent must infer that this is the create action and those are the query actions.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives an explicit trigger: 'Use when the user says "Use zambo to hand this over to <client>"', which is unambiguous context for invocation. It offers no when-not guidance and does not point to handover_list/handover_status for inspecting or re-checking an existing handover, so the alternative-selection half of the rule set is absent.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
handover_listHandover ListBRead-onlyIdempotentInspect
List your Zambo Handovers using Zambo Pass and the same _session_id. Returns real statuses and client-ready links.
| Name | Required | Description | Default |
|---|---|---|---|
| cursor | No | ||
| _zambo_key | No | Optional opaque Zambo access capability. Never place it in a URL or public log. | |
| _session_id | Yes | Optional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together. | |
| _caller_label | No | Optional caller label recorded as a caller-reported claim in the receipt. | |
| _continuity_ai_label | No | Optional self-reported AI client label for the private continuity timeline. Zambo does not independently verify the client. |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes | The tool's observed JSON value or plain-text result. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds that results contain 'real statuses and client-ready links', hinting at return content, plus the Zambo Pass auth requirement, but says nothing about pagination behavior or what the cursor does.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences with no padding, and the core purpose is front-loaded. It is arguably over-terse for a tool with a cursor-based pagination parameter, but nothing is wasted.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return values need not be explained, and the read-only annotations carry the safety story. Still, for a five-parameter tool with a pagination cursor, the description omits any hint about how listing is scoped or paged, leaving a modest gap.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 80%, so the schema already documents cursor, _zambo_key, _caller_label, and _continuity_ai_label. The description's mention of _session_id reuse only echoes what the schema description already states, adding no new semantic detail. Baseline 3 is correct.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (List) and resource (Zambo Handovers), so the basic operation is unambiguous. However, it does not distinguish itself from the sibling tools 'handover' and 'handover_status', leaving the agent to infer the division of labor between creating, listing, and checking status.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
'using Zambo Pass and the same _session_id' supplies a real prerequisite (reuse the session id across calls), which is more than most definitions offer. But there is no explicit when-to-use versus 'handover_status' or 'handover', and no stated exclusions or conditions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
handover_statusHandover StatusARead-onlyIdempotentInspect
Check a Zambo Handover's current status and client messages without spending execution quota. Supply the owning _session_id for private deliveries.
| Name | Required | Description | Default |
|---|---|---|---|
| _zambo_key | No | Optional opaque Zambo access capability. Never place it in a URL or public log. | |
| _session_id | No | Optional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together. | |
| handover_id | Yes | ||
| _caller_label | No | Optional caller label recorded as a caller-reported claim in the receipt. | |
| _continuity_ai_label | No | Optional self-reported AI client label for the private continuity timeline. Zambo does not independently verify the client. |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes | The tool's observed JSON value or plain-text result. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, non-destructive, openWorld, but the description adds a trait annotations cannot express: it does not consume execution quota. It also flags an ownership/privacy precondition for _session_id. No return-format detail, but an output schema exists, so this is solid added context.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two tight sentences that lead with the action and the cost benefit, then the conditional parameter requirement. Nothing is redundant or padded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With annotations covering the safety profile and an output schema covering return values, the description only needs to add cost and privacy context, which it does. It could still say what 'client messages' means or when status is stale, but nothing critical is missing for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Coverage is 80% and the schema already documents the four underscore-prefixed optional params. The description adds genuine meaning by telling the agent when _session_id becomes effectively required (private deliveries), which the schema's 'bind a Day Pass' text does not state.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (check) and resource (a Zambo Handover's current status and client messages), which is enough to separate it from handover_list and handover. It does not explicitly name those siblings as alternatives, so it stops short of a 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives one conditional usage instruction (supply _session_id for private deliveries) and an implicit cost-based reason to prefer this over a full execution. There is no explicit when-not guidance or named alternative, so usage remains implied rather than spelled out.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
journal_logJournal logDestructiveInspect
Free anonymous or authenticated append-only log for an action performed outside Zambo. The entry is recorded as an agent-reported claim; Zambo does not claim it ran or observed the action. Limited to 20 calls per IP per day on the free tier.
| Name | Required | Description | Default |
|---|---|---|---|
| inputs | No | Optional local input object. It is redacted and hashed, then discarded. | |
| job_id | Yes | Stable job or session identifier shared by the agent. | |
| metadata | No | Optional redacted display metadata. | |
| tool_name | Yes | Tool or action name reported by the agent. | |
| _zambo_key | No | Optional opaque Zambo access capability. Never place it in a URL or public log. | |
| started_at | No | RFC 3339 start timestamp. | |
| _session_id | No | Optional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together. | |
| duration_ms | No | Reported duration in milliseconds. | |
| completed_at | No | RFC 3339 completion timestamp. | |
| _caller_label | No | Optional caller label recorded as a caller-reported claim in the receipt. | |
| executor_identity | Yes | Agent, client, or local executor that reported the action. | |
| external_executor | No | External server or executor name when relevant. | |
| _continuity_ai_label | No | Optional self-reported AI client label for the private continuity timeline. Zambo does not independently verify the client. | |
| redacted_inputs_hash | No | Hash of redacted inputs. Raw inputs are never stored. |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes | The tool's observed JSON value or plain-text result. |
leadsignalLeadsignalRead-onlyInspect
AI lead generation for contractors and local service businesses. Accepts a trade type and city. Returns qualified local leads with available contact information.
| Name | Required | Description | Default |
|---|---|---|---|
| city | Yes | City and optional state. Example: 'Chicago', 'Denver CO', 'Austin Texas' | |
| trade | Yes | The trade or service type. Example: 'plumber', 'HVAC', 'electrician', 'roofer', 'general contractor' | |
| _zambo_key | No | Optional opaque Zambo access capability. Never place it in a URL or public log. | |
| _session_id | No | Optional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together. | |
| _caller_label | No | Optional caller label recorded as a caller-reported claim in the receipt. | |
| _continuity_ai_label | No | Optional self-reported AI client label for the private continuity timeline. Zambo does not independently verify the client. |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes | The tool's observed JSON value or plain-text result. |
live_priceLive PriceRead-onlyIdempotentInspect
Real-time cryptocurrency price lookup for supported coins. Uses CoinGecko first, Coinbase as a secondary no-key provider, then the most recent cached verified value with its age if both live providers are unavailable. Returns live USD price, 24-hour percentage change, and market capitalization when verified.
| Name | Required | Description | Default |
|---|---|---|---|
| coin | No | Alias for symbol. Accepts the same coin ticker or name, for example BTC. | |
| symbol | No | Coin ticker or name - BTC, ETH, SOL, DOGE, BNB, XRP, MATIC, AVAX, ADA, LINK, DOT, UNI, ATOM, NEAR, APT, OP, ARB, SUI, PEPE, WIF, BONK, TON, TRX, LTC, SHIB. Case-insensitive. | |
| _zambo_key | No | Optional opaque Zambo access capability. Never place it in a URL or public log. | |
| _session_id | No | Optional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together. | |
| _caller_label | No | Optional caller label recorded as a caller-reported claim in the receipt. | |
| _continuity_ai_label | No | Optional self-reported AI client label for the private continuity timeline. Zambo does not independently verify the client. |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes | The tool's observed JSON value or plain-text result. |
new_sessionNew sessionRead-onlyInspect
Starts fresh session context and returns a new session_id. Reuse that ID on subsequent calls for continuity; changing or omitting it starts clean context.
| Name | Required | Description | Default |
|---|---|---|---|
| _zambo_key | No | Optional opaque Zambo access capability. Never place it in a URL or public log. | |
| _session_id | No | Optional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together. | |
| _caller_label | No | Optional caller label recorded as a caller-reported claim in the receipt. | |
| _continuity_ai_label | No | Optional self-reported AI client label for the private continuity timeline. Zambo does not independently verify the client. |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes | The tool's observed JSON value or plain-text result. |
pdf_extractPDF ExtractRead-onlyIdempotentInspect
Fetch and extract text content from any public URL - PDF documents, web pages, articles, docs. Returns the extracted text, word count, and a summary. Works on research papers, contracts, articles, reports. Use when user says 'read this PDF', 'extract from this URL', 'summarize this document', 'what does this say'.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Public URL to the document or webpage to extract and summarize. | |
| max_chars | No | Max characters of raw text to return (default: 4000, max: 8000). | |
| summarize | No | Also generate an AI summary. Default: true. | |
| _zambo_key | No | Optional opaque Zambo access capability. Never place it in a URL or public log. | |
| _session_id | No | Optional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together. | |
| _caller_label | No | Optional caller label recorded as a caller-reported claim in the receipt. | |
| _continuity_ai_label | No | Optional self-reported AI client label for the private continuity timeline. Zambo does not independently verify the client. |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes | The tool's observed JSON value or plain-text result. |
prompt_shieldPrompt ShieldRead-onlyIdempotentInspect
Detection and analysis of prompt injection, jailbreak, and policy-bypass attempts. Returns an injection risk score, a safe/review/block recommendation, attack indicators, and a safe rewritten version when available.
| Name | Required | Description | Default |
|---|---|---|---|
| mode | No | 'fast' = pattern scan only (default), 'deep' = pattern + Groq semantic analysis | |
| No | Zambo Pass email for unlimited calls (optional) | ||
| prompt | Yes | The user input or prompt to validate for injection/jailbreak (max 16K chars) | |
| system | No | Your system prompt - also scanned for prompt leak attempts (optional) | |
| context | No | Describe your app for better contextual analysis (optional) | |
| _zambo_key | No | Optional opaque Zambo access capability. Never place it in a URL or public log. | |
| _session_id | No | Optional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together. | |
| certificate | No | If true, freeze this scan as a permanent public certificate and return certificate_url (optional) | |
| _caller_label | No | Optional caller label recorded as a caller-reported claim in the receipt. | |
| _continuity_ai_label | No | Optional self-reported AI client label for the private continuity timeline. Zambo does not independently verify the client. |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes | The tool's observed JSON value or plain-text result. |
provibe_auditProvibe AuditRead-onlyIdempotentInspect
AI code audit for a public GitHub repository. Returns a Provibe score from 0 to 100, security vulnerabilities, a dead-code map, and an execution plan for addressing the findings.
| Name | Required | Description | Default |
|---|---|---|---|
| No | Zambo Pass email for full audit (optional - without it you get the free teaser: score + top 3 issues). Get pass: https://zambo.dev/upgrade?tool=provibe_audit&tier=monthly | ||
| repo_url | Yes | Public GitHub repository URL. Example: https://github.com/owner/my-saas | |
| _zambo_key | No | Optional opaque Zambo access capability. Never place it in a URL or public log. | |
| _session_id | No | Optional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together. | |
| vibe_context | No | Optional context: language, framework, specific concerns, or what the project does | |
| _caller_label | No | Optional caller label recorded as a caller-reported claim in the receipt. | |
| _continuity_ai_label | No | Optional self-reported AI client label for the private continuity timeline. Zambo does not independently verify the client. |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes | The tool's observed JSON value or plain-text result. |
workflow_closeWorkflow CloseARead-onlyIdempotentInspect
Create or return an immutable snapshot of this job's eligible receipts. Repeating the call with unchanged receipt data returns the same snapshot workflow_id; later calls after new receipts create a separate snapshot while session_workflow_id continues identifying the live ledger. Both identifiers are unbound metadata excluded from canonical receipt bytes. The first close returns a one-time private workflow_manage_token; retries do not rotate or reissue it. The workflow_close summary receipt is excluded from the step count. Records Zambo's claims, not issuer authentication.
| Name | Required | Description | Default |
|---|---|---|---|
| _zambo_key | No | Optional opaque Zambo access capability. Never place it in a URL or public log. | |
| session_id | No | Alias for _session_id. | |
| _session_id | Yes | Optional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together. | |
| _caller_label | No | Optional caller label recorded as a caller-reported claim in the receipt. | |
| _continuity_ai_label | No | Optional self-reported AI client label for the private continuity timeline. Zambo does not independently verify the client. |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes | The tool's observed JSON value or plain-text result. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the annotations, it discloses the one-time private workflow_manage_token and that retries neither rotate nor reissue it, the exclusion of the close summary receipt from the step count, the non-canonical status of the session_workflow_id/workflow_id metadata, and the trust boundary ('Records Zambo's claims, not issuer authentication'). The idempotent/non-destructive/read-only claims in the annotations are actively reinforced by the immutable-snapshot and repeat-call semantics, adding real context rather than repeating structured fields.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Five tightly packed sentences, front-loaded with the core action before the idempotency, token, and trust details. Everything earns its place, though the receipt-byte jargon makes it denser than ideal for a quick scan.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With an output schema present, 100% schema coverage, and full annotations, the description only needed to cover behavioral quirks — and it does: idempotency semantics, token lifecycle, step-count exclusion, metadata treatment, and honest trust claims. Nothing an agent needs to call it correctly is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already documents all five inputs including aliases and the _zambo_key secrecy note. The description adds little about the input parameters themselves (it discusses identifiers that are largely outputs), so the baseline of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource: 'Create or return an immutable snapshot of this job's eligible receipts.' It also distinguishes the snapshot workflow_id from the live-ledger session_workflow_id, giving the agent a clear mental model of what it produces. It never names or contrasts with the obvious sibling workflow_seal, so it falls short of full sibling differentiation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is implied rather than stated: the agent learns that repeating the call with unchanged receipts yields the same snapshot, and that later calls create a new snapshot. There is no explicit when-to-use guidance and no routing to or away from alternatives such as workflow_seal or the continuity tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
workflow_sealWorkflow SealAIdempotentInspect
Seals a closed workflow for durable export. Requires the matching job session and an active pass. Never spends, captures, or starts a payment. The export remains a Zambo claim, not issuer authentication.
| Name | Required | Description | Default |
|---|---|---|---|
| action | No | Seal the paid snapshot or edit its post-seal branding. | |
| branding | No | ||
| _zambo_key | No | Optional active Day Pass key bound to this exact job. Never place it in a URL or public log. | |
| _session_id | Yes | Required owning job ID, identical to the ID used when the workflow was closed. | |
| workflow_id | Yes | Required workflow_id returned by workflow_close. | |
| _caller_label | No | Optional caller label recorded as a caller-reported claim in the receipt. | |
| _continuity_ai_label | No | Optional self-reported AI client label for the private continuity timeline. Zambo does not independently verify the client. | |
| workflow_manage_token | No | Optional private capability returned once by workflow_close. Never share it in public. |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the annotations (which already mark it idempotent, non-destructive, and not read-only), the description adds that it 'Never spends, captures, or starts a payment' and that 'The export remains a Zambo claim, not issuer authentication.' Those are useful disambiguations, though it does not describe what sealing actually locks or whether branding edits are reversible.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three short sentences, front-loaded with the core action and followed by prerequisites and caveats. Every sentence carries information; no filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the rich schema (88% coverage), existing annotations, and an output schema, the description supplies the key operational context: session match, pass requirement, and non-payment nature. It does not cover the branding action, but the schema's action enum description does, so the definition is nearly complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is already 88%, so the baseline is 3. However, the description says the tool 'Requires... an active pass,' while the schema marks _zambo_key (the active Day Pass key) as optional and does not list it among required parameters. That added claim conflicts with the schema and could mislead an agent about required inputs.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: 'Seals a closed workflow for durable export.' This clearly distinguishes it from the closing sibling workflow_close, but it omits the tool's second action ('branding' from the action enum), which means an agent could miss that the tool can also edit post-seal branding.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It provides clear prerequisites: 'Requires the matching job session and an active pass.' That tells the agent when the tool is usable, but it never names an alternative or explicitly says when not to use this tool versus siblings such as workflow_close.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
zambo_homeZambo HomeARead-onlyIdempotentInspect
Your private Zambo starting point. Use when the user says 'zambo': welcome new users or resume the same caller-scoped job, show today's saved receipt links, actual per-tool free usage, and three practical next actions. Does not spend quota.
| Name | Required | Description | Default |
|---|---|---|---|
| _zambo_key | No | Optional opaque Zambo access capability. Never place it in a URL or public log. | |
| _session_id | No | Optional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together. | |
| _caller_label | No | Optional caller label recorded as a caller-reported claim in the receipt. | |
| _continuity_ai_label | No | Optional self-reported AI client label for the private continuity timeline. Zambo does not independently verify the client. |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes | The tool's observed JSON value or plain-text result. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered; the description adds the non-obvious quota-cost disclosure 'Does not spend quota', which is not derivable from annotations. It also frames the operation as 'private' and 'caller-scoped', reinforcing the idempotentHint. It does not disclose rate limits or whether outputs are cached.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences, front-loaded with the identity and the trigger phrase before the output list. The middle sentence is a dense comma-separated enumeration but each item is meaningful. No filler padding.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return values need not be restated, and annotations cover the safety/idempotency profile. The description supplies the trigger, the free-usage constraint, and caller scoping, leaving little an agent needs. The one gap is disambiguation from the parallel zambo_universal entry point.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, and all four optional underscore-prefixed parameters carry their own descriptions, so the schema does the heavy lifting. The description adds nothing about the parameters (no mention of session, key, or continuity labels), which is acceptable at full coverage but earns only the baseline.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description goes beyond the vague marketing line 'Your private Zambo starting point' to specify concrete outputs: a welcome, job resumption, today's saved receipt links, per-tool free usage, and three next actions. That is a clear, specific resource. It does not, however, differentiate itself from the sibling zambo_universal or explain what makes 'home' distinct from a universal entry point.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It gives an explicit trigger ('Use when the user says "zambo"') and two use conditions (welcome new users, resume the same caller-scoped job). It states no when-not conditions and names no alternative sibling, so routing against zambo_universal is left to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
zambo_universalZambo UniversalDestructiveInspect
Universal Zambo entry point for routing natural-language requests across supported Zambo tools through one MCP connection. Covers strategy, code audits, lead generation, wallet intelligence, provenance certificates, swarm coordination, and live market data. Returns a route, execution state, downstream tool results when available, and receipt information.
| Name | Required | Description | Default |
|---|---|---|---|
| mode | No | Collaboration mode. execute routes and performs the request; continue uses the current session trail; verify checks whether the current session has completed a request. Default: execute. | |
| need | Yes | Natural language description of what you need. Any length. Also accepts: message, query, prompt, input, goal, text. Example: 'How do I protect my AI agent from prompt injection?' | |
| No | Optional email, only with the user's consent. Namespaces Pass access and a compact working trail so the same user can continue across AI clients without restarting. | ||
| format | No | Response format. Default: json. | |
| context | No | Optional extra context. Supported keys: repo_url, goal, trade, city, wallet, domain. Example: { "repo_url": "https://github.com/owner/repo" } | |
| remember | No | Optional explicit fact to persist in this stable session. It is returned by mode:'verify'; only use after the user asks you to remember it or clearly consents. | |
| _zambo_key | No | Optional opaque Zambo access capability. Never place it in a URL or public log. | |
| session_id | No | Alias for _session_id. Use one stable ID for the whole conversation so Zambo and the host AI do not repeat completed steps. | |
| _session_id | No | Optional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together. | |
| session_code | No | Optional ZAMBO-XXXX handoff code from Telegram /export. Loads that saved conversation into this request so another AI can continue immediately. | |
| _caller_label | No | Optional caller label recorded as a caller-reported claim in the receipt. | |
| _continuity_ai_label | No | Optional self-reported AI client label for the private continuity timeline. Zambo does not independently verify the client. |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes | The tool's observed JSON value or plain-text result. |
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
3 tool updates
- Added
handover - Added
handover_list - Added
handover_status
2 tool updates
- Changed
credithunt2 fields changed- changed
Input schema / properties / stack / typePrevious value: -"array"New value: +[ + "array", + "string" +] - changed
Input schema / properties / stage / enumPrevious value: -[ - "solo", - "early", - "growth" -]New value: +[ + "solo", + "early", + "growth", + "seed", + "pre-seed", + "series A", + "series B", + "series C" +]
- Added
zambo_home
6 tool updates
- Changed
day_pass_activate3 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "payment_method": "x402" - } -]New value: +[ + { + "_session_id": "73513c44-6969-435e-86eb-0fc262521fd1" + } +] - added
Input schema / properties / sponsorAdded value: +{ + "description": "Explicitly sponsor another team's closed workflow; branding ownership never transfers.", + "type": "boolean" +} - added
Input schema / properties / workflow_idAdded value: +{ + "description": "Optional workflow to seal after verified payment.", + "format": "uuid", + "type": "string" +}
- Added
day_pass_checkout_link - Changed
day_pass_status5 fields changed- added
Output schema / properties / result / additionalPropertiesAdded value: +true - removed
Output schema / properties / result / descriptionRemoved value: -"The tool's observed JSON value or plain-text result." - added
Output schema / properties / result / propertiesAdded value: +{ + "active": { + "type": "boolean" + }, + "calls_left": { + "oneOf": [ + { + "minimum": 0, + "type": "integer" + }, + { + "type": "string" + } + ] + }, + "calls_left_scope": { + "type": "string" + }, + "expires_at": { + "type": [ + "string", + "null" + ] + }, + "seals": { + "items": { + "additionalProperties": false, + "properties": { + "sealed_at": { + "type": "string" + }, + "workflow_id": { + "type": "string" + }, + "workflow_url": { + "type": "string" + } + }, + "required": [ + "workflow_id", + "workflow_url", + "sealed_at" + ], + "type": "object" + }, + "type": "array" + }, + "session_bound": { + "type": "boolean" + }, + "status": { + "type": "string" + } +} - added
Output schema / properties / result / requiredAdded value: +[ + "status", + "active", + "expires_at", + "calls_left", + "seals" +] - added
Output schema / properties / result / typeAdded value: +"object"
- Changed
provibe_audit1 field changed- changed
Input schema / properties / email / descriptionPrevious value: -"Zambo Pass email for full audit (optional - without it you get the free teaser: score + top 3 issues). Get pass: https://zambo.dev/#zambo-pass"New value: +"Zambo Pass email for full audit (optional - without it you get the free teaser: score + top 3 issues). Get pass: https://zambo.dev/upgrade?tool=provibe_audit&tier=monthly"
- Added
workflow_close - Added
workflow_seal
20 tool updates
- Changed
capability_search3 fields changed- changed
Input schema / properties / _caller_label / descriptionPrevious value: -"Optional self-reported caller label. It is recorded as a claim, not independently verified."New value: +"Optional caller label recorded as a caller-reported claim in the receipt." - changed
Input schema / properties / _session_id / descriptionPrevious value: -"Optional stable Zambo session ID used to preserve continuity across tool calls."New value: +"Optional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together." - added
Input schema / properties / _zambo_keyAdded value: +{ + "description": "Optional opaque Zambo access capability. Never place it in a URL or public log.", + "maxLength": 160, + "type": "string" +}
- Changed
continuity_get_recent3 fields changed- changed
Input schema / properties / _caller_label / descriptionPrevious value: -"Optional self-reported caller label. It is recorded as a claim, not independently verified."New value: +"Optional caller label recorded as a caller-reported claim in the receipt." - changed
Input schema / properties / _session_id / descriptionPrevious value: -"Optional stable Zambo session ID used to preserve continuity across tool calls."New value: +"Optional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together." - added
Input schema / properties / _zambo_keyAdded value: +{ + "description": "Optional opaque Zambo access capability. Never place it in a URL or public log.", + "maxLength": 160, + "type": "string" +}
- Changed
continuity_list_threads3 fields changed- changed
Input schema / properties / _caller_label / descriptionPrevious value: -"Optional self-reported caller label. It is recorded as a claim, not independently verified."New value: +"Optional caller label recorded as a caller-reported claim in the receipt." - changed
Input schema / properties / _session_id / descriptionPrevious value: -"Optional stable Zambo session ID used to preserve continuity across tool calls."New value: +"Optional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together." - added
Input schema / properties / _zambo_keyAdded value: +{ + "description": "Optional opaque Zambo access capability. Never place it in a URL or public log.", + "maxLength": 160, + "type": "string" +}
- Changed
continuity_open_thread3 fields changed- changed
Input schema / properties / _caller_label / descriptionPrevious value: -"Optional self-reported caller label. It is recorded as a claim, not independently verified."New value: +"Optional caller label recorded as a caller-reported claim in the receipt." - changed
Input schema / properties / _session_id / descriptionPrevious value: -"Optional stable Zambo session ID used to preserve continuity across tool calls."New value: +"Optional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together." - added
Input schema / properties / _zambo_keyAdded value: +{ + "description": "Optional opaque Zambo access capability. Never place it in a URL or public log.", + "maxLength": 160, + "type": "string" +}
- Changed
continuity_set_prefs3 fields changed- changed
Input schema / properties / _caller_label / descriptionPrevious value: -"Optional self-reported caller label. It is recorded as a claim, not independently verified."New value: +"Optional caller label recorded as a caller-reported claim in the receipt." - changed
Input schema / properties / _session_id / descriptionPrevious value: -"Optional stable Zambo session ID used to preserve continuity across tool calls."New value: +"Optional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together." - added
Input schema / properties / _zambo_keyAdded value: +{ + "description": "Optional opaque Zambo access capability. Never place it in a URL or public log.", + "maxLength": 160, + "type": "string" +}
- Changed
continuity_start_thread3 fields changed- changed
Input schema / properties / _caller_label / descriptionPrevious value: -"Optional self-reported caller label. It is recorded as a claim, not independently verified."New value: +"Optional caller label recorded as a caller-reported claim in the receipt." - changed
Input schema / properties / _session_id / descriptionPrevious value: -"Optional stable Zambo session ID used to preserve continuity across tool calls."New value: +"Optional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together." - added
Input schema / properties / _zambo_keyAdded value: +{ + "description": "Optional opaque Zambo access capability. Never place it in a URL or public log.", + "maxLength": 160, + "type": "string" +}
- Changed
credithunt3 fields changed- changed
Input schema / properties / _caller_label / descriptionPrevious value: -"Optional self-reported caller label. It is recorded as a claim, not independently verified."New value: +"Optional caller label recorded as a caller-reported claim in the receipt." - changed
Input schema / properties / _session_id / descriptionPrevious value: -"Optional stable Zambo session ID used to preserve continuity across tool calls."New value: +"Optional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together." - added
Input schema / properties / _zambo_keyAdded value: +{ + "description": "Optional opaque Zambo access capability. Never place it in a URL or public log.", + "maxLength": 160, + "type": "string" +}
- Changed
day_pass_activate4 fields changed- changed
Input schema / properties / _caller_label / descriptionPrevious value: -"Optional self-reported caller label. It is recorded as a claim, not independently verified."New value: +"Optional caller label recorded as a caller-reported claim in the receipt." - changed
Input schema / properties / _session_id / descriptionPrevious value: -"Optional stable Zambo session ID used to preserve continuity across tool calls."New value: +"Optional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together." - added
Input schema / properties / _zambo_keyAdded value: +{ + "description": "Optional opaque Zambo access capability. Never place it in a URL or public log.", + "maxLength": 160, + "type": "string" +} - removed
Input schema / properties / human_approvedRemoved value: -{ - "description": "Must be true only after the human explicitly approved this $0.99 USDC payment. Required when sending x_payment.", - "type": "boolean" -}
- Changed
day_pass_status4 fields changed- changed
Input schema / properties / _caller_label / descriptionPrevious value: -"Optional self-reported caller label. It is recorded as a claim, not independently verified."New value: +"Optional caller label recorded as a caller-reported claim in the receipt." - changed
Input schema / properties / _session_id / descriptionPrevious value: -"Optional stable Zambo session ID used to preserve continuity across tool calls."New value: +"Optional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together." - changed
Input schema / properties / _zambo_key / descriptionPrevious value: -"Optional Day Pass capability key. Never include it in a URL or public log."New value: +"Optional opaque Zambo access capability. Never place it in a URL or public log." - added
Input schema / properties / _zambo_key / maxLengthAdded value: +160
- Changed
ghost_audit_report3 fields changed- changed
Input schema / properties / _caller_label / descriptionPrevious value: -"Optional self-reported caller label. It is recorded as a claim, not independently verified."New value: +"Optional caller label recorded as a caller-reported claim in the receipt." - changed
Input schema / properties / _session_id / descriptionPrevious value: -"Optional stable Zambo session ID used to preserve continuity across tool calls."New value: +"Optional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together." - added
Input schema / properties / _zambo_keyAdded value: +{ + "description": "Optional opaque Zambo access capability. Never place it in a URL or public log.", + "maxLength": 160, + "type": "string" +}
- Changed
ghost_audit_site3 fields changed- changed
Input schema / properties / _caller_label / descriptionPrevious value: -"Optional self-reported caller label. It is recorded as a claim, not independently verified."New value: +"Optional caller label recorded as a caller-reported claim in the receipt." - changed
Input schema / properties / _session_id / descriptionPrevious value: -"Optional stable Zambo session ID used to preserve continuity across tool calls."New value: +"Optional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together." - added
Input schema / properties / _zambo_keyAdded value: +{ + "description": "Optional opaque Zambo access capability. Never place it in a URL or public log.", + "maxLength": 160, + "type": "string" +}
- Changed
ghost_audit_status3 fields changed- changed
Input schema / properties / _caller_label / descriptionPrevious value: -"Optional self-reported caller label. It is recorded as a claim, not independently verified."New value: +"Optional caller label recorded as a caller-reported claim in the receipt." - changed
Input schema / properties / _session_id / descriptionPrevious value: -"Optional stable Zambo session ID used to preserve continuity across tool calls."New value: +"Optional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together." - added
Input schema / properties / _zambo_keyAdded value: +{ + "description": "Optional opaque Zambo access capability. Never place it in a URL or public log.", + "maxLength": 160, + "type": "string" +}
- Changed
journal_log3 fields changed- changed
Input schema / properties / _caller_label / descriptionPrevious value: -"Optional self-reported caller label. It is recorded as a claim, not independently verified."New value: +"Optional caller label recorded as a caller-reported claim in the receipt." - changed
Input schema / properties / _session_id / descriptionPrevious value: -"Optional stable Zambo session ID used to preserve continuity across tool calls."New value: +"Optional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together." - added
Input schema / properties / _zambo_keyAdded value: +{ + "description": "Optional opaque Zambo access capability. Never place it in a URL or public log.", + "maxLength": 160, + "type": "string" +}
- Changed
leadsignal3 fields changed- changed
Input schema / properties / _caller_label / descriptionPrevious value: -"Optional self-reported caller label. It is recorded as a claim, not independently verified."New value: +"Optional caller label recorded as a caller-reported claim in the receipt." - changed
Input schema / properties / _session_id / descriptionPrevious value: -"Optional stable Zambo session ID used to preserve continuity across tool calls."New value: +"Optional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together." - added
Input schema / properties / _zambo_keyAdded value: +{ + "description": "Optional opaque Zambo access capability. Never place it in a URL or public log.", + "maxLength": 160, + "type": "string" +}
- Changed
live_price3 fields changed- changed
Input schema / properties / _caller_label / descriptionPrevious value: -"Optional self-reported caller label. It is recorded as a claim, not independently verified."New value: +"Optional caller label recorded as a caller-reported claim in the receipt." - changed
Input schema / properties / _session_id / descriptionPrevious value: -"Optional stable Zambo session ID used to preserve continuity across tool calls."New value: +"Optional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together." - added
Input schema / properties / _zambo_keyAdded value: +{ + "description": "Optional opaque Zambo access capability. Never place it in a URL or public log.", + "maxLength": 160, + "type": "string" +}
- Changed
new_session3 fields changed- changed
Input schema / properties / _caller_label / descriptionPrevious value: -"Optional self-reported caller label. It is recorded as a claim, not independently verified."New value: +"Optional caller label recorded as a caller-reported claim in the receipt." - changed
Input schema / properties / _session_id / descriptionPrevious value: -"Optional stable Zambo session ID used to preserve continuity across tool calls."New value: +"Optional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together." - added
Input schema / properties / _zambo_keyAdded value: +{ + "description": "Optional opaque Zambo access capability. Never place it in a URL or public log.", + "maxLength": 160, + "type": "string" +}
- Changed
pdf_extract3 fields changed- changed
Input schema / properties / _caller_label / descriptionPrevious value: -"Optional self-reported caller label. It is recorded as a claim, not independently verified."New value: +"Optional caller label recorded as a caller-reported claim in the receipt." - changed
Input schema / properties / _session_id / descriptionPrevious value: -"Optional stable Zambo session ID used to preserve continuity across tool calls."New value: +"Optional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together." - added
Input schema / properties / _zambo_keyAdded value: +{ + "description": "Optional opaque Zambo access capability. Never place it in a URL or public log.", + "maxLength": 160, + "type": "string" +}
- Changed
prompt_shield3 fields changed- changed
Input schema / properties / _caller_label / descriptionPrevious value: -"Optional self-reported caller label. It is recorded as a claim, not independently verified."New value: +"Optional caller label recorded as a caller-reported claim in the receipt." - changed
Input schema / properties / _session_id / descriptionPrevious value: -"Optional stable Zambo session ID used to preserve continuity across tool calls."New value: +"Optional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together." - added
Input schema / properties / _zambo_keyAdded value: +{ + "description": "Optional opaque Zambo access capability. Never place it in a URL or public log.", + "maxLength": 160, + "type": "string" +}
- Changed
provibe_audit3 fields changed- changed
Input schema / properties / _caller_label / descriptionPrevious value: -"Optional self-reported caller label. It is recorded as a claim, not independently verified."New value: +"Optional caller label recorded as a caller-reported claim in the receipt." - changed
Input schema / properties / _session_id / descriptionPrevious value: -"Optional stable Zambo session ID used to preserve continuity across tool calls."New value: +"Optional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together." - added
Input schema / properties / _zambo_keyAdded value: +{ + "description": "Optional opaque Zambo access capability. Never place it in a URL or public log.", + "maxLength": 160, + "type": "string" +}
- Changed
zambo_universal3 fields changed- changed
Input schema / properties / _caller_label / descriptionPrevious value: -"Optional self-reported caller label. It is recorded as a claim, not independently verified."New value: +"Optional caller label recorded as a caller-reported claim in the receipt." - changed
Input schema / properties / _session_id / descriptionPrevious value: -"Optional stable Zambo session ID used to preserve continuity across tool calls."New value: +"Optional stable bot-job ID. Reuse it across calls to bind a Day Pass and keep the job ledger together." - added
Input schema / properties / _zambo_keyAdded value: +{ + "description": "Optional opaque Zambo access capability. Never place it in a URL or public log.", + "maxLength": 160, + "type": "string" +}
20 tool updates
- Changed
capability_search6 fields changed- changed
Output schema / additionalPropertiesPrevious value: -trueNew value: +false - removed
Output schema / properties / countRemoved value: -{ - "type": "number" -} - removed
Output schema / properties / matchedRemoved value: -{ - "items": { - "type": "string" - }, - "type": "array" -} - added
Output schema / properties / resultAdded value: +{ + "description": "The tool's observed JSON value or plain-text result." +} - removed
Output schema / properties / toolsRemoved value: -{ - "items": { - "type": "object" - }, - "type": "array" -} - added
Output schema / requiredAdded value: +[ + "result" +]
- Changed
continuity_get_recent9 fields changed- changed
Output schema / additionalPropertiesPrevious value: -trueNew value: +false - removed
Output schema / properties / cursorRemoved value: -{ - "type": "string" -} - removed
Output schema / properties / eventsRemoved value: -{ - "items": { - "type": "string" - }, - "type": "array" -} - removed
Output schema / properties / handoff_textRemoved value: -{ - "type": "string" -} - removed
Output schema / properties / has_moreRemoved value: -{ - "type": "boolean" -} - removed
Output schema / properties / next_cursorRemoved value: -{ - "type": "string" -} - added
Output schema / properties / resultAdded value: +{ + "description": "The tool's observed JSON value or plain-text result." +} - removed
Output schema / properties / statusRemoved value: -{ - "type": "string" -} - added
Output schema / requiredAdded value: +[ + "result" +]
- Changed
continuity_list_threads5 fields changed- changed
Output schema / additionalPropertiesPrevious value: -trueNew value: +false - added
Output schema / properties / resultAdded value: +{ + "description": "The tool's observed JSON value or plain-text result." +} - removed
Output schema / properties / statusRemoved value: -{ - "type": "string" -} - removed
Output schema / properties / threadsRemoved value: -{ - "items": { - "type": "string" - }, - "type": "array" -} - added
Output schema / requiredAdded value: +[ + "result" +]
- Changed
continuity_open_thread7 fields changed- changed
Output schema / additionalPropertiesPrevious value: -trueNew value: +false - removed
Output schema / properties / eventsRemoved value: -{ - "items": { - "type": "string" - }, - "type": "array" -} - removed
Output schema / properties / handoff_textRemoved value: -{ - "type": "string" -} - added
Output schema / properties / resultAdded value: +{ + "description": "The tool's observed JSON value or plain-text result." +} - removed
Output schema / properties / statusRemoved value: -{ - "type": "string" -} - removed
Output schema / properties / thread_idRemoved value: -{ - "type": "string" -} - added
Output schema / requiredAdded value: +[ + "result" +]
- Changed
continuity_set_prefs7 fields changed- changed
Output schema / additionalPropertiesPrevious value: -trueNew value: +false - removed
Output schema / properties / capture_enabledRemoved value: -{ - "type": "boolean" -} - removed
Output schema / properties / public_receipts_remainRemoved value: -{ - "type": "boolean" -} - added
Output schema / properties / resultAdded value: +{ + "description": "The tool's observed JSON value or plain-text result." +} - removed
Output schema / properties / scope_typeRemoved value: -{ - "type": "string" -} - removed
Output schema / properties / statusRemoved value: -{ - "type": "string" -} - added
Output schema / requiredAdded value: +[ + "result" +]
- Changed
continuity_start_thread7 fields changed- changed
Output schema / additionalPropertiesPrevious value: -trueNew value: +false - removed
Output schema / properties / nameRemoved value: -{ - "type": "string" -} - added
Output schema / properties / resultAdded value: +{ + "description": "The tool's observed JSON value or plain-text result." +} - removed
Output schema / properties / session_idRemoved value: -{ - "type": "string" -} - removed
Output schema / properties / statusRemoved value: -{ - "type": "string" -} - removed
Output schema / properties / thread_idRemoved value: -{ - "type": "string" -} - added
Output schema / requiredAdded value: +[ + "result" +]
- Changed
credithunt7 fields changed- changed
Output schema / additionalPropertiesPrevious value: -trueNew value: +false - removed
Output schema / properties / apiRemoved value: -{ - "additionalProperties": true, - "type": "object" -} - removed
Output schema / properties / countRemoved value: -{ - "type": "number" -} - removed
Output schema / properties / opportunitiesRemoved value: -{ - "items": { - "type": "object" - }, - "type": "array" -} - added
Output schema / properties / resultAdded value: +{ + "description": "The tool's observed JSON value or plain-text result." +} - removed
Output schema / properties / updated_atRemoved value: -{ - "type": "string" -} - added
Output schema / requiredAdded value: +[ + "result" +]
- Changed
day_pass_activate9 fields changed- changed
Output schema / additionalPropertiesPrevious value: -trueNew value: +false - removed
Output schema / properties / access_keyRemoved value: -{ - "type": "string" -} - removed
Output schema / properties / activatedRemoved value: -{ - "type": "boolean" -} - removed
Output schema / properties / already_activeRemoved value: -{ - "type": "boolean" -} - removed
Output schema / properties / expires_atRemoved value: -{ - "type": "string" -} - removed
Output schema / properties / how_to_useRemoved value: -{ - "additionalProperties": true, - "type": "object" -} - added
Output schema / properties / resultAdded value: +{ + "description": "The tool's observed JSON value or plain-text result." +} - removed
Output schema / properties / x711_creditsRemoved value: -{ - "type": "number" -} - added
Output schema / requiredAdded value: +[ + "result" +]
- Changed
day_pass_status9 fields changed- changed
Output schema / additionalPropertiesPrevious value: -trueNew value: +false - removed
Output schema / properties / activeRemoved value: -{ - "type": "boolean" -} - removed
Output schema / properties / calls_leftRemoved value: -{ - "oneOf": [ - { - "type": "string" - }, - { - "type": "number" - } - ] -} - removed
Output schema / properties / calls_left_scopeRemoved value: -{ - "type": "string" -} - removed
Output schema / properties / expires_atRemoved value: -{ - "oneOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] -} - added
Output schema / properties / resultAdded value: +{ + "description": "The tool's observed JSON value or plain-text result." +} - removed
Output schema / properties / session_boundRemoved value: -{ - "type": "boolean" -} - removed
Output schema / properties / statusRemoved value: -{ - "type": "string" -} - added
Output schema / requiredAdded value: +[ + "result" +]
- Changed
ghost_audit_report6 fields changed- changed
Output schema / additionalPropertiesPrevious value: -trueNew value: +false - removed
Output schema / properties / audit_idRemoved value: -{ - "type": "string" -} - removed
Output schema / properties / reportRemoved value: -{ - "type": "string" -} - added
Output schema / properties / resultAdded value: +{ + "description": "The tool's observed JSON value or plain-text result." +} - removed
Output schema / properties / statusRemoved value: -{ - "oneOf": [ - { - "type": "string" - }, - { - "type": "string" - } - ] -} - added
Output schema / requiredAdded value: +[ + "result" +]
- Changed
ghost_audit_site8 fields changed- changed
Output schema / additionalPropertiesPrevious value: -trueNew value: +false - removed
Output schema / properties / audit_idRemoved value: -{ - "type": "string" -} - removed
Output schema / properties / download_urlRemoved value: -{ - "type": "string" -} - added
Output schema / properties / resultAdded value: +{ + "description": "The tool's observed JSON value or plain-text result." +} - removed
Output schema / properties / stagesRemoved value: -{ - "items": { - "type": "string" - }, - "type": "array" -} - removed
Output schema / properties / statusRemoved value: -{ - "type": "string" -} - removed
Output schema / properties / stream_urlRemoved value: -{ - "type": "string" -} - added
Output schema / requiredAdded value: +[ + "result" +]
- Changed
ghost_audit_status6 fields changed- changed
Output schema / additionalPropertiesPrevious value: -trueNew value: +false - removed
Output schema / properties / audit_idRemoved value: -{ - "type": "string" -} - removed
Output schema / properties / readyRemoved value: -{ - "type": "boolean" -} - added
Output schema / properties / resultAdded value: +{ + "description": "The tool's observed JSON value or plain-text result." +} - removed
Output schema / properties / statusRemoved value: -{ - "oneOf": [ - { - "type": "string" - }, - { - "type": "string" - } - ] -} - added
Output schema / requiredAdded value: +[ + "result" +]
- Changed
journal_log6 fields changed- changed
Output schema / additionalPropertiesPrevious value: -trueNew value: +false - removed
Output schema / properties / provenance_classRemoved value: -{ - "type": "string" -} - added
Output schema / properties / resultAdded value: +{ + "description": "The tool's observed JSON value or plain-text result." +} - removed
Output schema / properties / statusRemoved value: -{ - "type": "string" -} - removed
Output schema / properties / verify_urlRemoved value: -{ - "type": "string" -} - added
Output schema / requiredAdded value: +[ + "result" +]
- Changed
leadsignal7 fields changed- changed
Output schema / additionalPropertiesPrevious value: -trueNew value: +false - removed
Output schema / properties / cityRemoved value: -{ - "type": "string" -} - removed
Output schema / properties / countRemoved value: -{ - "type": "number" -} - removed
Output schema / properties / leadsRemoved value: -{ - "items": { - "type": "object" - }, - "type": "array" -} - added
Output schema / properties / resultAdded value: +{ + "description": "The tool's observed JSON value or plain-text result." +} - removed
Output schema / properties / tradeRemoved value: -{ - "type": "string" -} - added
Output schema / requiredAdded value: +[ + "result" +]
- Changed
live_price4 fields changed- changed
Output schema / additionalPropertiesPrevious value: -trueNew value: +false - added
Output schema / properties / result / descriptionAdded value: +"The tool's observed JSON value or plain-text result." - removed
Output schema / properties / result / typeRemoved value: -"string" - added
Output schema / requiredAdded value: +[ + "result" +]
- Changed
new_session6 fields changed- changed
Output schema / additionalPropertiesPrevious value: -trueNew value: +false - removed
Output schema / properties / instructionsRemoved value: -{ - "type": "string" -} - added
Output schema / properties / resultAdded value: +{ + "description": "The tool's observed JSON value or plain-text result." +} - removed
Output schema / properties / session_idRemoved value: -{ - "type": "string" -} - removed
Output schema / properties / statusRemoved value: -{ - "type": "string" -} - added
Output schema / requiredAdded value: +[ + "result" +]
- Changed
pdf_extract4 fields changed- changed
Output schema / additionalPropertiesPrevious value: -trueNew value: +false - added
Output schema / properties / result / descriptionAdded value: +"The tool's observed JSON value or plain-text result." - removed
Output schema / properties / result / typeRemoved value: -"string" - added
Output schema / requiredAdded value: +[ + "result" +]
- Changed
prompt_shield6 fields changed- changed
Output schema / additionalPropertiesPrevious value: -trueNew value: +false - added
Output schema / properties / resultAdded value: +{ + "description": "The tool's observed JSON value or plain-text result." +} - removed
Output schema / properties / safeRemoved value: -{ - "type": "boolean" -} - removed
Output schema / properties / sanitizedRemoved value: -{ - "type": "string" -} - removed
Output schema / properties / threatsRemoved value: -{ - "items": { - "type": "string" - }, - "type": "array" -} - added
Output schema / requiredAdded value: +[ + "result" +]
- Changed
provibe_audit7 fields changed- changed
Output schema / additionalPropertiesPrevious value: -trueNew value: +false - removed
Output schema / properties / dead_codeRemoved value: -{ - "items": { - "type": "string" - }, - "type": "array" -} - removed
Output schema / properties / execution_planRemoved value: -{ - "type": "string" -} - removed
Output schema / properties / provibe_scoreRemoved value: -{ - "type": "number" -} - added
Output schema / properties / resultAdded value: +{ + "description": "The tool's observed JSON value or plain-text result." +} - removed
Output schema / properties / vulnerabilitiesRemoved value: -{ - "items": { - "type": "string" - }, - "type": "array" -} - added
Output schema / requiredAdded value: +[ + "result" +]
- Changed
zambo_universal15 fields changed- changed
Output schema / additionalPropertiesPrevious value: -trueNew value: +false - removed
Output schema / properties / executedRemoved value: -{ - "type": "boolean" -} - removed
Output schema / properties / executed_toolsRemoved value: -{ - "items": { - "type": "string" - }, - "type": "array" -} - removed
Output schema / properties / groundingRemoved value: -{ - "oneOf": [ - { - "type": "string" - }, - { - "type": "string" - }, - { - "type": "string" - }, - { - "type": "string" - } - ] -} - removed
Output schema / properties / observed_statusRemoved value: -{ - "oneOf": [ - { - "type": "string" - }, - { - "type": "string" - }, - { - "type": "string" - }, - { - "type": "string" - }, - { - "type": "string" - } - ] -} - removed
Output schema / properties / okRemoved value: -{ - "type": "boolean" -} - removed
Output schema / properties / planned_toolsRemoved value: -{ - "items": { - "type": "string" - }, - "type": "array" -} - added
Output schema / properties / result / descriptionAdded value: +"The tool's observed JSON value or plain-text result." - removed
Output schema / properties / result / typeRemoved value: -"string" - removed
Output schema / properties / result_statusRemoved value: -{ - "oneOf": [ - { - "type": "string" - }, - { - "type": "string" - }, - { - "type": "string" - }, - { - "type": "string" - }, - { - "type": "string" - } - ] -} - removed
Output schema / properties / run_idRemoved value: -{ - "type": "string" -} - removed
Output schema / properties / sourcesRemoved value: -{ - "items": { - "type": "object" - }, - "type": "array" -} - removed
Output schema / properties / understoodRemoved value: -{ - "type": "string" -} - removed
Output schema / properties / verifyRemoved value: -{ - "additionalProperties": true, - "type": "object" -} - added
Output schema / requiredAdded value: +[ + "result" +]
5 tool updates
- Changed
day_pass_activate1 field changed- added
Input schema / properties / session_idAdded value: +{ + "description": "Alias for _session_id.", + "maxLength": 64, + "type": "string" +}
- Added
day_pass_status - Changed
ghost_audit_report2 fields changed- added
Output schema / properties / status / oneOfAdded value: +[ + { + "type": "string" + }, + { + "type": "string" + } +] - removed
Output schema / properties / status / typeRemoved value: -"string"
- Changed
ghost_audit_status2 fields changed- added
Output schema / properties / status / oneOfAdded value: +[ + { + "type": "string" + }, + { + "type": "string" + } +] - removed
Output schema / properties / status / typeRemoved value: -"string"
- Changed
zambo_universal6 fields changed- added
Output schema / properties / grounding / oneOfAdded value: +[ + { + "type": "string" + }, + { + "type": "string" + }, + { + "type": "string" + }, + { + "type": "string" + } +] - removed
Output schema / properties / grounding / typeRemoved value: -"string" - added
Output schema / properties / observed_status / oneOfAdded value: +[ + { + "type": "string" + }, + { + "type": "string" + }, + { + "type": "string" + }, + { + "type": "string" + }, + { + "type": "string" + } +] - removed
Output schema / properties / observed_status / typeRemoved value: -"string" - added
Output schema / properties / result_status / oneOfAdded value: +[ + { + "type": "string" + }, + { + "type": "string" + }, + { + "type": "string" + }, + { + "type": "string" + }, + { + "type": "string" + } +] - removed
Output schema / properties / result_status / typeRemoved value: -"string"
19 tool updates
- Changed
capability_search2 fields changed- added
Input schema / properties / _caller_labelAdded value: +{ + "description": "Optional self-reported caller label. It is recorded as a claim, not independently verified.", + "maxLength": 80, + "type": "string" +} - added
Input schema / properties / _session_idAdded value: +{ + "description": "Optional stable Zambo session ID used to preserve continuity across tool calls.", + "maxLength": 64, + "type": "string" +}
- Changed
continuity_get_recent8 fields changed- added
Input schema / properties / _caller_labelAdded value: +{ + "description": "Optional self-reported caller label. It is recorded as a claim, not independently verified.", + "maxLength": 80, + "type": "string" +} - changed
Input schema / properties / _session_id / descriptionPrevious value: -"The existing Zambo job ID shared across AI clients."New value: +"Optional stable Zambo session ID used to preserve continuity across tool calls." - added
Input schema / properties / _session_id / maxLengthAdded value: +64 - added
Input schema / properties / cursorAdded value: +{ + "description": "Opaque next-page cursor returned by the previous continuity_get_recent result.", + "type": "string" +} - added
Input schema / properties / sinceAdded value: +{ + "description": "Optional inclusive RFC3339 timestamp lower bound. Keep it unchanged while following a cursor.", + "format": "date-time", + "type": "string" +} - added
Output schema / properties / cursorAdded value: +{ + "type": "string" +} - added
Output schema / properties / has_moreAdded value: +{ + "type": "boolean" +} - added
Output schema / properties / next_cursorAdded value: +{ + "type": "string" +}
- Changed
continuity_list_threads3 fields changed- added
Input schema / properties / _caller_labelAdded value: +{ + "description": "Optional self-reported caller label. It is recorded as a claim, not independently verified.", + "maxLength": 80, + "type": "string" +} - changed
Input schema / properties / _session_id / descriptionPrevious value: -"The existing Zambo job ID that owns these threads."New value: +"Optional stable Zambo session ID used to preserve continuity across tool calls." - added
Input schema / properties / _session_id / maxLengthAdded value: +64
- Changed
continuity_open_thread3 fields changed- added
Input schema / properties / _caller_labelAdded value: +{ + "description": "Optional self-reported caller label. It is recorded as a claim, not independently verified.", + "maxLength": 80, + "type": "string" +} - changed
Input schema / properties / _session_id / descriptionPrevious value: -"The parent job ID, when opening by name."New value: +"Optional stable Zambo session ID used to preserve continuity across tool calls." - added
Input schema / properties / _session_id / maxLengthAdded value: +64
- Changed
continuity_set_prefs3 fields changed- added
Input schema / properties / _caller_labelAdded value: +{ + "description": "Optional self-reported caller label. It is recorded as a claim, not independently verified.", + "maxLength": 80, + "type": "string" +} - changed
Input schema / properties / _session_id / descriptionPrevious value: -"Existing Zambo job ID."New value: +"Optional stable Zambo session ID used to preserve continuity across tool calls." - added
Input schema / properties / _session_id / maxLengthAdded value: +64
- Changed
continuity_start_thread3 fields changed- added
Input schema / properties / _caller_labelAdded value: +{ + "description": "Optional self-reported caller label. It is recorded as a claim, not independently verified.", + "maxLength": 80, + "type": "string" +} - changed
Input schema / properties / _session_id / descriptionPrevious value: -"Existing Zambo job ID that will own the new thread."New value: +"Optional stable Zambo session ID used to preserve continuity across tool calls." - added
Input schema / properties / _session_id / maxLengthAdded value: +64
- Changed
credithunt2 fields changed- added
Input schema / properties / _caller_labelAdded value: +{ + "description": "Optional self-reported caller label. It is recorded as a claim, not independently verified.", + "maxLength": 80, + "type": "string" +} - added
Input schema / properties / _session_idAdded value: +{ + "description": "Optional stable Zambo session ID used to preserve continuity across tool calls.", + "maxLength": 64, + "type": "string" +}
- Changed
day_pass_activate2 fields changed- added
Input schema / properties / _caller_labelAdded value: +{ + "description": "Optional self-reported caller label. It is recorded as a claim, not independently verified.", + "maxLength": 80, + "type": "string" +} - added
Input schema / properties / _session_idAdded value: +{ + "description": "Optional stable Zambo session ID used to preserve continuity across tool calls.", + "maxLength": 64, + "type": "string" +}
- Changed
ghost_audit_report2 fields changed- added
Input schema / properties / _caller_labelAdded value: +{ + "description": "Optional self-reported caller label. It is recorded as a claim, not independently verified.", + "maxLength": 80, + "type": "string" +} - added
Input schema / properties / _session_idAdded value: +{ + "description": "Optional stable Zambo session ID used to preserve continuity across tool calls.", + "maxLength": 64, + "type": "string" +}
- Changed
ghost_audit_site2 fields changed- added
Input schema / properties / _caller_labelAdded value: +{ + "description": "Optional self-reported caller label. It is recorded as a claim, not independently verified.", + "maxLength": 80, + "type": "string" +} - added
Input schema / properties / _session_idAdded value: +{ + "description": "Optional stable Zambo session ID used to preserve continuity across tool calls.", + "maxLength": 64, + "type": "string" +}
- Changed
ghost_audit_status2 fields changed- added
Input schema / properties / _caller_labelAdded value: +{ + "description": "Optional self-reported caller label. It is recorded as a claim, not independently verified.", + "maxLength": 80, + "type": "string" +} - added
Input schema / properties / _session_idAdded value: +{ + "description": "Optional stable Zambo session ID used to preserve continuity across tool calls.", + "maxLength": 64, + "type": "string" +}
- Changed
journal_log6 fields changed- added
Input schema / properties / _caller_labelAdded value: +{ + "description": "Optional self-reported caller label. It is recorded as a claim, not independently verified.", + "maxLength": 80, + "type": "string" +} - added
Input schema / properties / _session_idAdded value: +{ + "description": "Optional stable Zambo session ID used to preserve continuity across tool calls.", + "maxLength": 64, + "type": "string" +} - added
Output schema / properties / provenance_classAdded value: +{ + "type": "string" +} - removed
Output schema / properties / resultRemoved value: -{ - "type": "string" -} - added
Output schema / properties / statusAdded value: +{ + "type": "string" +} - added
Output schema / properties / verify_urlAdded value: +{ + "type": "string" +}
- Changed
leadsignal2 fields changed- added
Input schema / properties / _caller_labelAdded value: +{ + "description": "Optional self-reported caller label. It is recorded as a claim, not independently verified.", + "maxLength": 80, + "type": "string" +} - added
Input schema / properties / _session_idAdded value: +{ + "description": "Optional stable Zambo session ID used to preserve continuity across tool calls.", + "maxLength": 64, + "type": "string" +}
- Changed
live_price2 fields changed- added
Input schema / properties / _caller_labelAdded value: +{ + "description": "Optional self-reported caller label. It is recorded as a claim, not independently verified.", + "maxLength": 80, + "type": "string" +} - added
Input schema / properties / _session_idAdded value: +{ + "description": "Optional stable Zambo session ID used to preserve continuity across tool calls.", + "maxLength": 64, + "type": "string" +}
- Changed
new_session2 fields changed- added
Input schema / properties / _caller_labelAdded value: +{ + "description": "Optional self-reported caller label. It is recorded as a claim, not independently verified.", + "maxLength": 80, + "type": "string" +} - added
Input schema / properties / _session_idAdded value: +{ + "description": "Optional stable Zambo session ID used to preserve continuity across tool calls.", + "maxLength": 64, + "type": "string" +}
- Changed
pdf_extract2 fields changed- added
Input schema / properties / _caller_labelAdded value: +{ + "description": "Optional self-reported caller label. It is recorded as a claim, not independently verified.", + "maxLength": 80, + "type": "string" +} - added
Input schema / properties / _session_idAdded value: +{ + "description": "Optional stable Zambo session ID used to preserve continuity across tool calls.", + "maxLength": 64, + "type": "string" +}
- Changed
prompt_shield2 fields changed- added
Input schema / properties / _caller_labelAdded value: +{ + "description": "Optional self-reported caller label. It is recorded as a claim, not independently verified.", + "maxLength": 80, + "type": "string" +} - added
Input schema / properties / _session_idAdded value: +{ + "description": "Optional stable Zambo session ID used to preserve continuity across tool calls.", + "maxLength": 64, + "type": "string" +}
- Changed
provibe_audit2 fields changed- added
Input schema / properties / _caller_labelAdded value: +{ + "description": "Optional self-reported caller label. It is recorded as a claim, not independently verified.", + "maxLength": 80, + "type": "string" +} - added
Input schema / properties / _session_idAdded value: +{ + "description": "Optional stable Zambo session ID used to preserve continuity across tool calls.", + "maxLength": 64, + "type": "string" +}
- Changed
zambo_universal3 fields changed- added
Input schema / properties / _caller_labelAdded value: +{ + "description": "Optional self-reported caller label. It is recorded as a claim, not independently verified.", + "maxLength": 80, + "type": "string" +} - changed
Input schema / properties / _session_id / descriptionPrevious value: -"Stable ID generated by the host AI once per conversation and reused on every Zambo call. Enables a shared working trail across multi-step tasks."New value: +"Optional stable Zambo session ID used to preserve continuity across tool calls." - added
Input schema / properties / _session_id / maxLengthAdded value: +64
1 tool update
- Changed
day_pass_activate1 field changed- added
Input schema / properties / human_approvedAdded value: +{ + "description": "Must be true only after the human explicitly approved this $0.99 USDC payment. Required when sending x_payment.", + "type": "boolean" +}
1 tool update
- Changed
credithunt5 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "query": "AI startup credits" - } -]New value: +[ + { + "min_value": 5000, + "stack": [ + "openai", + "vercel" + ], + "stage": "early" + } +] - changed
Input schema / properties / stack / descriptionPrevious value: -"Your tech stack for matched recommendations. Example: [\"openai\",\"vercel\",\"aws\"]. Leave empty to get all programs."New value: +"Optional stack filter. Example: [\"openai\",\"vercel\",\"aws\"]. Leave empty to include all programs." - added
Output schema / properties / apiAdded value: +{ + "additionalProperties": true, + "type": "object" +} - removed
Output schema / properties / matchedRemoved value: -{ - "items": { - "type": "object" - }, - "type": "array" -} - added
Output schema / properties / updated_atAdded value: +{ + "type": "string" +}
1 tool update
- Changed
credithunt2 fields changed- added
Output schema / properties / opportunitiesAdded value: +{ + "items": { + "type": "object" + }, + "type": "array" +} - removed
Output schema / properties / programsRemoved value: -{ - "items": { - "type": "object" - }, - "type": "array" -}
19 tool updates
- Changed
capability_search1 field changed- added
Input schema / properties / _continuity_ai_labelAdded value: +{ + "description": "Optional self-reported AI client label for the private continuity timeline. Zambo does not independently verify the client.", + "maxLength": 48, + "type": "string" +}
- Added
continuity_get_recent - Added
continuity_list_threads - Added
continuity_open_thread - Added
continuity_set_prefs - Added
continuity_start_thread - Changed
credithunt2 fields changed- added
Input schema / properties / _continuity_ai_labelAdded value: +{ + "description": "Optional self-reported AI client label for the private continuity timeline. Zambo does not independently verify the client.", + "maxLength": 48, + "type": "string" +} - changed
Input schema / properties / stage / descriptionPrevious value: -"Your stage: solo (1 person), early (2–10), growth (10+). Default: solo."New value: +"Your stage: solo (1 person), early (2 to 10), growth (10+). Default: solo."
- Changed
day_pass_activate1 field changed- added
Input schema / properties / _continuity_ai_labelAdded value: +{ + "description": "Optional self-reported AI client label for the private continuity timeline. Zambo does not independently verify the client.", + "maxLength": 48, + "type": "string" +}
- Changed
ghost_audit_report1 field changed- added
Input schema / properties / _continuity_ai_labelAdded value: +{ + "description": "Optional self-reported AI client label for the private continuity timeline. Zambo does not independently verify the client.", + "maxLength": 48, + "type": "string" +}
- Changed
ghost_audit_site1 field changed- added
Input schema / properties / _continuity_ai_labelAdded value: +{ + "description": "Optional self-reported AI client label for the private continuity timeline. Zambo does not independently verify the client.", + "maxLength": 48, + "type": "string" +}
- Changed
ghost_audit_status1 field changed- added
Input schema / properties / _continuity_ai_labelAdded value: +{ + "description": "Optional self-reported AI client label for the private continuity timeline. Zambo does not independently verify the client.", + "maxLength": 48, + "type": "string" +}
- Changed
journal_log1 field changed- added
Input schema / properties / _continuity_ai_labelAdded value: +{ + "description": "Optional self-reported AI client label for the private continuity timeline. Zambo does not independently verify the client.", + "maxLength": 48, + "type": "string" +}
- Changed
leadsignal1 field changed- added
Input schema / properties / _continuity_ai_labelAdded value: +{ + "description": "Optional self-reported AI client label for the private continuity timeline. Zambo does not independently verify the client.", + "maxLength": 48, + "type": "string" +}
- Changed
live_price2 fields changed- added
Input schema / properties / _continuity_ai_labelAdded value: +{ + "description": "Optional self-reported AI client label for the private continuity timeline. Zambo does not independently verify the client.", + "maxLength": 48, + "type": "string" +} - changed
Input schema / properties / symbol / descriptionPrevious value: -"Coin ticker or name — BTC, ETH, SOL, DOGE, BNB, XRP, MATIC, AVAX, ADA, LINK, DOT, UNI, ATOM, NEAR, APT, OP, ARB, SUI, PEPE, WIF, BONK, TON, TRX, LTC, SHIB. Case-insensitive."New value: +"Coin ticker or name - BTC, ETH, SOL, DOGE, BNB, XRP, MATIC, AVAX, ADA, LINK, DOT, UNI, ATOM, NEAR, APT, OP, ARB, SUI, PEPE, WIF, BONK, TON, TRX, LTC, SHIB. Case-insensitive."
- Changed
new_session1 field changed- added
Input schema / properties / _continuity_ai_labelAdded value: +{ + "description": "Optional self-reported AI client label for the private continuity timeline. Zambo does not independently verify the client.", + "maxLength": 48, + "type": "string" +}
- Added
pdf_extract - Changed
prompt_shield2 fields changed- added
Input schema / properties / _continuity_ai_labelAdded value: +{ + "description": "Optional self-reported AI client label for the private continuity timeline. Zambo does not independently verify the client.", + "maxLength": 48, + "type": "string" +} - changed
Input schema / properties / system / descriptionPrevious value: -"Your system prompt — also scanned for prompt leak attempts (optional)"New value: +"Your system prompt - also scanned for prompt leak attempts (optional)"
- Changed
provibe_audit2 fields changed- added
Input schema / properties / _continuity_ai_labelAdded value: +{ + "description": "Optional self-reported AI client label for the private continuity timeline. Zambo does not independently verify the client.", + "maxLength": 48, + "type": "string" +} - changed
Input schema / properties / email / descriptionPrevious value: -"Zambo Pass email for full audit (optional — without it you get the free teaser: score + top 3 issues). Get pass: https://zambo.dev/#zambo-pass"New value: +"Zambo Pass email for full audit (optional - without it you get the free teaser: score + top 3 issues). Get pass: https://zambo.dev/#zambo-pass"
- Changed
zambo_universal1 field changed- added
Input schema / properties / _continuity_ai_labelAdded value: +{ + "description": "Optional self-reported AI client label for the private continuity timeline. Zambo does not independently verify the client.", + "maxLength": 48, + "type": "string" +}
13 tool updates
- First observed
capability_search - First observed
credithunt - First observed
day_pass_activate - First observed
ghost_audit_report - First observed
ghost_audit_site - First observed
ghost_audit_status - First observed
journal_log - First observed
leadsignal - First observed
live_price - First observed
new_session - First observed
prompt_shield - First observed
provibe_audit - First observed
zambo_universal
Related MCP Connectors
Issue signed receipts for AI agent actions; verify any receipt offline - free, no account.
Hand off AI work with a signed Verification Receipt — an independent verifier proves it runs.
Governed AI actions with signed, verifiable receipts: free keyless reads, human-approved writes.
Give your AI hands. One URL. Type a job. Get a receipt.
Related MCP Servers
AlicenseAqualityAmaintenanceThe accountability layer for AI agents — a named human's signed yes before an agent does anything irreversible (payment, record change, deploy), then an offline-verifiable Trust Receipt. Apache-2.0, formally verified.3611Apache 2.0- AlicenseAqualityAmaintenanceCryptographic receipts for AI outputs — signed, chain-anchored, $0.001/call6423 npmMIT
- AlicenseAqualityBmaintenanceEnables AI agents to create cryptographically verifiable receipts of their delegated work, with capabilities for multi-party approval and offline verification.1154 npmApache 2.0

EVIDIQ Notary MCPofficial
AlicenseNot gradedqualityBmaintenanceCryptographic receipt layer for AI inferences. Enables notarization and verification of AI outputs with on-chain proofs via x402 payment.1MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.