Browser-download delivery for agents: captures stranded downloads, delivers with a signed receipt.
Scored across 3 tools
Each tool occupies a distinct phase of the workflow: coverage answers 'which hosts are supported', transfer performs the capture/delivery, and verify checks the resulting receipt. There is no realistic scenario where an agent would confuse these three operations.
All tools share a consistent 'downloadbridge_' prefix with a single-word suffix, which makes the family easy to scan. The only minor deviation is mixing a noun ('coverage') with verbs ('transfer', 'verify'), but readability is not harmed.
Three tools is well-matched to a narrow, transactional service: check coverage, execute a transfer, verify a receipt. Nothing feels padded or missing at the surface level.
The core lifecycle (coverage → transfer → verify) is fully covered, which is strong for a focused service. However, there is no tool for checking transfer status/history, listing past transfers, or retrieving an api_token (registration is described as an external POST /register endpoint), leaving a few workaround-required gaps.
Host coverage matrix (free).
Inputs: no named parameters.
Capture + deliver a browser download with a signed receipt. $0.25/transfer; one free transfer per operator, ever. Requires api_token (from POST /register with wallet_signature proof), host_id, filename, source_url, transfer_id; optional x_payment header value for paid calls.
Inputs: host_id (required), filename (required), api_token (required), source_url (required), +2 more.
Verify a signed receipt (signature + delivered-bytes re-hash). $0.05/verify via x_payment.
Inputs: payload (required), x_payment (required), signature_b64 (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Proof of delivery for agent work: verify countersigned receipts and deliverable hashes. Free.
Agent-ready social delivery with preflight, verification, retries, diagnostics, and audit controls.
Client intake: files, copy and logins from clients, from the browser or your AI agent.
Where agents keep their word. Agent marketplace: pay on delivery, signed receipts.
Add one secure layer between your agents and this server.