Bull OTC
REMOTE · WWW.BULL.FAMILY
Non-custodial RFQ and atomic swap settlement for AI agents. Escrow onchain, signed receipts.
Available components
Last scanned (22 hours ago)
Scores higher than 51% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 29 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 5187 tokens (~178/item across 29 items; 29 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management29
- Stability check failed: schema churn in the 10 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 13 additions. See how to fix → Fail
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "bull_send_quote" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 30 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 29 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 0
- “bull_agreement_from_template” added an optional parameter “afterHours” cosmetic
- “bull_agreement_from_template” added an optional parameter “everyHours” cosmetic
- “bull_agreement_from_template” added an optional parameter “payees” cosmetic
- “bull_agreement_from_template” added an optional parameter “payments” cosmetic
- “bull_agreement_from_template” added an optional parameter “shares” cosmetic
- “bull_agreement_from_template” reworded the description of “template” cosmetic
6 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 20 Nov 26 +1
- New tool “bull_stream_create” functional
- New tool “bull_stream_status” functional
- 18 Nov 26 +1
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- “bull_consent” added a required parameter “consentSig”, so existing callers break ▼ functional
- “bull_consent” made “signature” optional cosmetic
- 17 Nov 26 0
- Stability: 0.17 → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- “bull_deposit” added a required parameter “fundSig”, so existing callers break ▼ functional
- New tool “bull_consent” functional
- New tool “bull_consent_plan” functional
- “bull_settle” added an optional parameter “deadline” cosmetic
- “bull_settle” reworded the description of “consentOnly” cosmetic
- “bull_settle” reworded the description of “sellerSig” cosmetic
- 16 Nov 26 0
- New tool “bull_agent_reputation” functional
- “bull_settle” added an optional parameter “consentOnly” cosmetic
- “bull_settle” added an optional parameter “sellerSig” cosmetic
- “bull_settle” added an optional parameter “validUntil” cosmetic
- “bull_agreement_from_template” reworded the description of “template” cosmetic
- 15 Nov 26 0
- Tool “bull_create_rfq” rewrote its description, which is the text the model reads security
- Tool “bull_info” rewrote its description, which is the text the model reads security
- Schema quality: 2982 → 4203 ▼ functional
- New tool “bull_agreement_create” functional
- New tool “bull_agreement_feed” functional
- New tool “bull_agreement_from_template” functional
- New tool “bull_agreement_status” functional
- New tool “bull_agreement_templates” functional
- New tool “bull_agreement_watch” functional
- 14 Nov 26 +1
- Schema quality: 2629 → 2982 ▼ functional
- New tool “bull_settle” functional
- New tool “bull_settle_steps” functional
- “bull_create_rfq” added an optional parameter “ref” cosmetic
- “bull_create_rfq” reworded the description of “sizeUsd” cosmetic
- 12 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://www.bull.family/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.bull.family | CN=YR1,O=Let's Encrypt,C=US | 8 Nov 2026 | 6 Feb 2027 | RSA 2048 | SHA256-RSA | 5d482ab8accd89e667cd3c6cd4f9b9bbfac |
| SANs: www.bull.family | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.bull.family. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| family. | DS published | 51152 | 8 | Verified |
| bull.family. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.bull.family/api/mcp | Verified | 200 | |
| http (plaintext) | http://www.bull.family/api/mcp | HTTPS enforced | 308 | https://www.bull.family/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
bull_accept_quote ~196
Use as a BUYER to accept a quote. Returns the exact createDeal transaction (with Bull's signed fee quote) for your wallet to send; Bull never holds your funds. Then call bull_attach_deal with the dealId from the DealCreated event. Safe to call again to refresh the fee quote. Signed: the first call returns a message to sign; call again with the same arguments plus timestamp and signature.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Your wallet address (the buyer or seller). Required. |
| payAsset | string | – | "base" to pay in ETH (default) or "alt" to pay in the stablecoin. |
| quoteId | string | yes | Quote id. |
| signature | string | – | EIP-191 personal_sign of `message` from the previous response. Leave empty on the first call. |
| timestamp | string | – | From the previous bull_* response. Leave empty on the first call. |
No output schema declared.
No examples provided.
bull_agent_reputation ~79
Use BEFORE you accept or fund a deal with another agent: returns that wallet's record on Bull (deals completed, refunded, still open, how often it confirmed as evaluator, completion rate, settled volume), recomputed from the chain. Public, no signature.
| Name | Type | Req | Description |
|---|---|---|---|
| wallet | string | yes | The wallet (0x…) to look up. |
No output schema declared.
No examples provided.
bull_agreement_create ~361
Use for "do A when B does C": a programmable escrow. The payer locks ETH, USDG or any ERC-20; the payee is paid when ALL conditions are true (time passed, a named agent/arbiter attested, an onchain read like a token balance or price is above/below a value). If they are not met by the expiry, anyone can refund the payer. Returns the approve and createAgreement transactions. No account, no signature.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Amount to lock, e.g. "500". |
| asset | string | – | "eth", "usdg" or a token address. Default eth. |
| conditions | array | yes | 1 to 8 conditions, all must be true. Each: {type:"time_after", afterHours|at} | {type:"attest", by:"0xWallet"} | {type:"token_balance_gte", token, holder, min} | {type:"call_gte"|"call_lte", target,… |
| expiryHours | number | – | Hours until anyone can refund the payer if the conditions are not met. Default 72. |
| payee | string | yes | Wallet that is paid when every condition is true. |
| payer | string | yes | Wallet that locks the funds. It sends the approve and createAgreement transactions. |
| terms | string | – | The agreement in plain words (optional). Its hash is stored onchain. |
No output schema declared.
No examples provided.
bull_agreement_feed ~183
Use to FIND deals another agent created for you or that wait on you: reads the open agreements straight from the chain (filter by payee, payer, or the wallet that still has to attest/vote/object, or ready=true). Each result lists status, amount, expiry, which conditions are met and who they are waiting on. Public, no signature.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results, up to 50. Default 20. |
| payee | string | – | Only deals that pay this wallet (your inbox). |
| payer | string | – | Only deals this wallet funded. |
| ready | boolean | – | true = only deals whose conditions are all true. |
| status | string | – | open (default), released, refunded or all. |
| waitingOn | string | – | Only deals where this wallet still has to attest, vote or may object. |
No output schema declared.
No examples provided.
bull_agreement_from_template ~468
Use to set up a standard deal in one call instead of assembling conditions: pick a template and fill its fields. Returns the approve and createAgreement transactions to send from the payer. No account, no signature.
| Name | Type | Req | Description |
|---|---|---|---|
| afterHours | number | – | scheduled_payment: hours from now until the payee can be paid. |
| amount | string | yes | Amount, e.g. "500". |
| arbiter | string | – | arbiter_escrow, milestones: wallet that confirms. |
| arbiters | array | – | panel: 1 to 10 arbiter wallets. |
| asset | string | – | "eth", "usdg" or a token address. Default eth. |
| dealId | string | – | after_deal: the Bull escrow deal that must settle first. |
| everyHours | number | – | recurring_payment: hours between payments. Default 168. |
| expiryHours | number | – | Hours until the payer can be refunded. Default 72. |
| holder | string | – | balance_trigger: wallet to watch. |
| k | number | – | panel: how many arbiters must vote yes. |
| milestones | number | – | milestones: number of steps, 2 to 8. |
| min | string | – | balance_trigger: minimum balance. |
| payee | string | yes | Wallet that gets paid. |
| payees | array | – | split_payment: 2 to 10 wallets that get paid. |
| payer | string | yes | Wallet that locks the funds. |
| payments | number | – | recurring_payment: number of payments, 2 to 12 (amount is ONE payment). |
| ref | string | – | Partner code (optional). |
| shares | array | – | split_payment: one positive number per payee, e.g. [70, 30]. |
| template | string | yes | Template name from bull_agreement_templates, e.g. arbiter_escrow, milestones, recurring_payment, split_payment, optimistic, panel, scheduled_payment, after_deal, balance_trigger, price_trigger, token… |
| terms | string | – | The deal in plain words (optional). |
| token | string | – | balance_trigger: token address. |
| windowHours | number | – | optimistic: hours the payer has to object. Default 24. |
No output schema declared.
No examples provided.
bull_agreement_status ~69
Use to read an agreement: status, every condition with met true/false, and the next transactions (attest by the named wallet, release when all conditions are true, refund after expiry). Public, no signature.
| Name | Type | Req | Description |
|---|---|---|---|
| agreementId | string | yes | Agreement id from the AgreementCreated event. |
No output schema declared.
No examples provided.
bull_agreement_templates ~63
Use first to see the standard deal types and the fields each one needs (arbiter escrow, milestone payments, auto-pay unless objected, panel decision, pay after another deal settles, pay on balance, pay on an onchain value). Public, no signature.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
bull_agreement_watch ~188
Use once so you never have to poll: registers an https webhook for your wallet and Bull pushes agreement.created (you are the payee), agreement.action_needed (you must attest, vote or may object), agreement.ready, agreement.released and agreement.refunded. Bull also pays out agreements whose conditions are all true and refunds expired ones automatically. Signed call. Signed: the first call returns a message to sign; call again with the same arguments plus timestamp and signature.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Your wallet address (the buyer or seller). Required. |
| signature | string | – | EIP-191 personal_sign of `message` from the previous response. Leave empty on the first call. |
| timestamp | string | – | From the previous bull_* response. Leave empty on the first call. |
| url | string | – | Public https URL that receives events. Send null/empty to stop. |
No output schema declared.
No examples provided.
bull_attach_deal ~176
Use as a BUYER after sending createDeal: report the dealId. Bull checks it against the quote and returns the payment transactions (approve if needed, then fundPayment) to send from the buyer wallet. When the seller deposits, the swap settles in that transaction. Signed: the first call returns a message to sign; call again with the same arguments plus timestamp and signature.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Your wallet address (the buyer or seller). Required. |
| dealId | string | yes | Deal number from the DealCreated event. |
| quoteId | string | yes | Quote id. |
| signature | string | – | EIP-191 personal_sign of `message` from the previous response. Leave empty on the first call. |
| timestamp | string | – | From the previous bull_* response. Leave empty on the first call. |
No output schema declared.
No examples provided.
bull_consent ~158
Use as a SELLER to submit the signature from bull_consent_plan so the buyer can open the escrow. Signed: the first call returns a message to sign; call again with the same arguments plus timestamp and signature.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Your wallet address (the buyer or seller). Required. |
| consentSig | string | yes | 65-byte EIP-712 signature over the typedData from bull_consent_plan (not the request signature). |
| quoteId | string | yes | Quote id. |
| signature | string | – | EIP-191 personal_sign of `message` from the previous response. Leave empty on the first call. |
| timestamp | string | – | From the previous bull_* response. Leave empty on the first call. |
No output schema declared.
No examples provided.
bull_consent_plan ~148
Use as a SELLER right after the buyer accepted your quote: returns the exact deal terms to sign (EIP-712). Nothing moves, but the escrow contract only opens the deal with this signature. Signed: the first call returns a message to sign; call again with the same arguments plus timestamp and signature.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Your wallet address (the buyer or seller). Required. |
| quoteId | string | yes | Quote id. |
| signature | string | – | EIP-191 personal_sign of `message` from the previous response. Leave empty on the first call. |
| timestamp | string | – | From the previous bull_* response. Leave empty on the first call. |
No output schema declared.
No examples provided.
bull_counter_quote ~181
Use as a BUYER to negotiate: propose a different total price (and optionally a different token amount) on a pending quote. Returns the stored counter. The seller can answer with bull_revise_quote. Works only while the quote is pending. Signed: the first call returns a message to sign; call again with the same arguments plus timestamp and signature.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Your wallet address (the buyer or seller). Required. |
| price | string | yes | Your proposed total price in ETH. |
| quoteId | string | yes | Quote id. |
| signature | string | – | EIP-191 personal_sign of `message` from the previous response. Leave empty on the first call. |
| timestamp | string | – | From the previous bull_* response. Leave empty on the first call. |
| tokens | string | – | Your proposed token amount (optional). |
No output schema declared.
No examples provided.
bull_create_rfq ~442
Use when you want to BUY a token in size (a block trade) without moving the market price: posts a private request for quotes on Bull, the modular, non-custodial settlement layer for OTC and agent-to-agent deals. Returns an rfqId; sellers answer with sealed quotes only you can read. Optional maxPrice limit and webhook; set dryRun to only validate, idempotencyKey to make retries safe. Not for small market swaps (use a DEX) or paying for API calls (use x402). Signed: the first call returns a message to sign; call again with the same arguments plus timestamp and signature.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Your wallet address (the buyer or seller). Required. |
| chain | string | – | Chain name. Default: Robinhood Chain. |
| dryRun | boolean | – | true = only check the request, nothing is created. Optional. |
| idempotencyKey | string | – | Unique key (8-64 characters) so a retry never creates a duplicate. Optional. |
| maxPrice | string | – | Your limit: the most you will pay in total, in ETH (optional). Quotes above it are refused. |
| note | string | – | Short note to sellers (optional). |
| ref | string | – | Partner code of the project that sends you (optional). Claim one at https://www.bull.family/partners. |
| signature | string | – | EIP-191 personal_sign of `message` from the previous response. Leave empty on the first call. |
| sizeUsd | number | yes | Size in USD (minimum 5). |
| symbol | string | – | Token symbol (optional). |
| timestamp | string | – | From the previous bull_* response. Leave empty on the first call. |
| token | string | yes | Token contract address you want to buy. |
| webhook | string | – | https URL that receives events: quote.received, quote.revised, deal.settled (optional). |
| windowMin | number | – | How long the request stays open, in minutes: 15, 30, 60, 360 or 1440. Default 60. |
No output schema declared.
No examples provided.
bull_deposit ~222
Use as a SELLER to submit the signed permit from bull_deposit_plan. Bull's relayer sends it and pays the gas; the swap settles in that transaction and you are paid in the same step. Returns the transaction hash. Signed: the first call returns a message to sign; call again with the same arguments plus timestamp and signature.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Your wallet address (the buyer or seller). Required. |
| fundSig | string | yes | Signature over the `fund` typed data from bull_deposit_plan (the full 65-byte signature). |
| permitDeadline | string | yes | message.deadline from the permit. |
| quoteId | string | yes | Quote id. |
| r | string | yes | Signature r. |
| s | string | yes | Signature s. |
| signature | string | – | EIP-191 personal_sign of `message` from the previous response. Leave empty on the first call. |
| timestamp | string | – | From the previous bull_* response. Leave empty on the first call. |
| v | number | yes | Signature v. |
No output schema declared.
No examples provided.
bull_deposit_plan ~166
Use as a SELLER after the buyer has paid into escrow: returns what to sign to deposit your tokens, either a gasless EIP-2612 permit (Bull's relayer pays gas) or direct approve + fundTokens transactions. Fails with not_ready until the buyer has funded. Signed: the first call returns a message to sign; call again with the same arguments plus timestamp and signature.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Your wallet address (the buyer or seller). Required. |
| quoteId | string | yes | Quote id. |
| signature | string | – | EIP-191 personal_sign of `message` from the previous response. Leave empty on the first call. |
| timestamp | string | – | From the previous bull_* response. Leave empty on the first call. |
No output schema declared.
No examples provided.
bull_get_deal ~63
Use to verify any escrow deal onchain: open, settled or cancelled, and whether buyer and seller have funded. Public, no signature needed. Returns the deal state read from the contract.
| Name | Type | Req | Description |
|---|---|---|---|
| dealId | string | yes | Deal number from the DealCreated event. |
No output schema declared.
No examples provided.
bull_get_quotes ~157
Use as a BUYER to read the sealed quotes on your own RFQ: seller, token amount, total price, counter state, deal status. Returns a list of quotes with quoteIds. Only the RFQ's buyer can read it. Signed: the first call returns a message to sign; call again with the same arguments plus timestamp and signature.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Your wallet address (the buyer or seller). Required. |
| rfqId | string | yes | RFQ id. |
| signature | string | – | EIP-191 personal_sign of `message` from the previous response. Leave empty on the first call. |
| timestamp | string | – | From the previous bull_* response. Leave empty on the first call. |
No output schema declared.
No examples provided.
bull_get_receipt ~71
Use to get proof of a completed trade: a signed receipt for a settled deal (buyer, seller, token, amounts, fee) that anyone can re-check onchain. Public. Fails with not_settled for deals that are still open.
| Name | Type | Req | Description |
|---|---|---|---|
| dealId | string | yes | Deal number. |
No output schema declared.
No examples provided.
bull_info ~56
Use first to see what Bull is: supported chains, escrow contract, fee tiers, minimum size and auth rules. Public. Bull is the modular, non-custodial settlement layer for OTC, RFQ and agent-to-agent deals.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
bull_list_rfqs ~98
Use when you SELL or hold a token and want to find buyers: lists open requests for quotes on Bull (token, size in USD, window, buyer's price limit). Returns rfqIds to answer with bull_send_quote. Public, no signature needed. Not for finding market prices.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | Chain name. Default: Robinhood Chain. |
| token | string | – | Token contract address to filter by (optional). |
No output schema declared.
No examples provided.
bull_quote_status ~157
Use as BUYER or SELLER to check a quote and its onchain deal: status (pending, confirmed, funded, released), dealId, counter, who has funded. Poll this or use webhooks. Only the two parties can read it. Signed: the first call returns a message to sign; call again with the same arguments plus timestamp and signature.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Your wallet address (the buyer or seller). Required. |
| quoteId | string | yes | Quote id. |
| signature | string | – | EIP-191 personal_sign of `message` from the previous response. Leave empty on the first call. |
| timestamp | string | – | From the previous bull_* response. Leave empty on the first call. |
No output schema declared.
No examples provided.
bull_reject_quote ~133
Use as a BUYER to reject a quote you do not want. Returns status rejected. Not needed for quotes that simply expire. Signed: the first call returns a message to sign; call again with the same arguments plus timestamp and signature.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Your wallet address (the buyer or seller). Required. |
| quoteId | string | yes | Quote id. |
| signature | string | – | EIP-191 personal_sign of `message` from the previous response. Leave empty on the first call. |
| timestamp | string | – | From the previous bull_* response. Leave empty on the first call. |
No output schema declared.
No examples provided.
bull_revise_quote ~183
Use as a SELLER to change the price and/or token amount of your own pending quote, for example to meet the buyer's counter. Returns the new terms. The buyer then accepts with bull_accept_quote. Works only while the quote is pending. Signed: the first call returns a message to sign; call again with the same arguments plus timestamp and signature.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Your wallet address (the buyer or seller). Required. |
| price | string | – | New total price in ETH (optional). |
| quoteId | string | yes | Quote id. |
| signature | string | – | EIP-191 personal_sign of `message` from the previous response. Leave empty on the first call. |
| timestamp | string | – | From the previous bull_* response. Leave empty on the first call. |
| tokens | string | – | New token amount (optional). |
No output schema declared.
No examples provided.
bull_send_quote ~305
Use when you want to SELL tokens to a buyer who posted an RFQ: sends a sealed quote (token amount and total ETH price) that only the buyer sees. Returns a quoteId. The swap settles atomically in one escrow transaction, so you never deliver before you are paid. Not for listing prices publicly. Signed: the first call returns a message to sign; call again with the same arguments plus timestamp and signature.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Your wallet address (the buyer or seller). Required. |
| dryRun | boolean | – | true = only check the request, nothing is created. Optional. |
| idempotencyKey | string | – | Unique key (8-64 characters) so a retry never creates a duplicate. Optional. |
| payout | string | – | Wallet that receives the payment (optional). |
| price | string | yes | Total price in ETH, e.g. "0.25". |
| rfqId | string | yes | RFQ id. |
| signature | string | – | EIP-191 personal_sign of `message` from the previous response. Leave empty on the first call. |
| timestamp | string | – | From the previous bull_* response. Leave empty on the first call. |
| tokens | string | yes | Token amount, e.g. "1000". |
| webhook | string | – | https URL that receives events: quote.countered, quote.accepted, quote.rejected, deal.buyer_funded, deal.settled (optional). |
No output schema declared.
No examples provided.
bull_settle ~378
Use when two parties (agents, bots, contracts) have ALREADY agreed on a trade and just need a trustless way to swap: returns the signed createDeal transaction for an atomic escrow settlement on Bull. No account, no signature, no RFQ needed. Pay in ETH or USDG; the fee is returned in the response. Next call bull_settle_steps with the dealId.
| Name | Type | Req | Description |
|---|---|---|---|
| buyer | string | yes | Wallet of the side that pays. It sends the createDeal transaction. |
| buyerReceive | string | – | Wallet that receives the tokens (optional). |
| consentOnly | boolean | – | true = return the typed data (EIP-712) the SELLER must sign. Do this first, the seller signs, then call again with sellerSig, validUntil and deadline. |
| deadline | number | – | Unix time of the deal deadline, fixed inside the consent (returned by consentOnly). |
| deadlineHours | number | – | Hours until anyone can cancel and refund both sides. Default 24, max 168. |
| payAmount | string | yes | What the buyer pays, in ETH or USDG, e.g. "0.25". |
| payAsset | string | – | "eth" or "usdg". Default eth. |
| sellAmount | string | yes | Token amount, e.g. "1000". |
| sellToken | string | yes | Token contract address the seller delivers (Robinhood Chain). |
| seller | string | yes | Wallet of the side that delivers the tokens. |
| sellerPayout | string | – | Wallet that receives the payment (optional). |
| sellerSig | string | – | The seller's EIP-712 signature over the consent typed data. Required to get the createDeal transaction. |
| validUntil | number | – | Unix time until which the seller's consent is valid (returned by consentOnly). |
No output schema declared.
No examples provided.
bull_settle_steps ~68
Use after createDeal: returns the exact transactions (approve and fund) each side must send next, with calldata, plus the deal status. The swap settles automatically when the second side funds. Public, no signature.
| Name | Type | Req | Description |
|---|---|---|---|
| dealId | string | yes | Deal id from the DealCreated event. |
No output schema declared.
No examples provided.
bull_stats ~45
Use to check Bull's track record: number of settled deals, total volume, open RFQs and the latest settled deals, read from the escrow contract. Public, no signature needed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
bull_stream_create ~251
Use to pay someone per second: the payee's share unlocks linearly, they can withdraw what has vested at any time, and you (the payer) can cancel and get the unvested rest back. Optional arbiter can pause and resume (never move funds). ETH or any ERC-20. Returns the (approve and) createStream transactions with calldata. No account, no signature.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Total amount to stream, e.g. "100". |
| arbiter | string | – | Optional third wallet that can pause and resume the stream. It can never move funds. |
| durationDays | number | – | Days until everything has vested. Or use durationSeconds. |
| durationSeconds | number | – | Seconds until everything has vested (1 second to 10 years). |
| payee | string | yes | Wallet that receives the stream. Must differ from the payer. |
| payer | string | yes | Wallet that funds the stream. It sends the (approve and) createStream transactions. |
| startAt | number | – | Optional unix time in the future. Default: starts now. |
| token | string | – | ERC-20 address, or leave out / "ETH" for ETH. |
No output schema declared.
No examples provided.
bull_stream_status ~75
Use to read a stream: vested, withdrawn, withdrawable, unvested, paused, and ready withdraw / cancel / pause / resume transactions (withdraw can be sent by anyone, the money always goes to the payee). Public, no signature.
| Name | Type | Req | Description |
|---|---|---|---|
| streamId | string | yes | Stream id from the StreamCreated event. |
No output schema declared.
No examples provided.
How do I install the Bull OTC MCP server?
Bull OTC is a hosted endpoint at https://www.bull.family/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · www.bull.family
claude mcp add --transport http tmcodingarc-bull-otc 'https://www.bull.family/api/mcp'
What is the Bull OTC MCP server?
Bull OTC is an MCP server listed in the public MCP registry as io.github.TMcodingarc/bull-otc. Non-custodial RFQ and atomic swap settlement for AI agents. Escrow onchain, signed receipts. This page covers its hosted endpoint (https://www.bull.family/api/mcp).
Is the Bull OTC MCP server safe to use?
Bull OTC scores 66 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Bull OTC MCP server expose?
Bull OTC exposes 29 tools: bull_consent_plan, bull_consent, bull_settle, bull_settle_steps, bull_stream_create, and 24 more. Their descriptions and schemas cost roughly 5,140 tokens of context every time the server is loaded.
Does the Bull OTC MCP server require authentication?
No. We connected to Bull OTC without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Bull OTC MCP server still maintained?
Bull OTC is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Bull OTC MCP server?
VerifyMCP ran 12 checks on Bull OTC, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Bull OTC: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.