Bull OTC MCP server
io.github.TMcodingarc/bull-otcTMcodingarcstreamable-httpv1.0.0Scanned
Non-custodial RFQ and atomic swap settlement for AI agents. Escrow onchain, signed receipts.
16 tools: 1 do something that can't be undone, 10 change things and 5 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 2
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here does something that can't be undone. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Bull OTC MCP server can do
The Bull OTC MCP server is published by the GitHub account TMcodingarc. It has 16 tools. It can do things that cannot be undone, such as sending, paying or publishing (bull_send_quote) and create or change data (10 tools: bull_create_rfq, bull_counter_quote, bull_revise_quote, bull_accept_quote and 6 more), but cannot delete data. 5 tools only read.
2 tools can send data out of your system (bull_create_rfq and bull_send_quote).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 11, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
16 tools
Can't be undone 1Claude Code: ask
bull_send_quoteUse 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.Can send data outNo findings
Why it is in this group
- The name "bull_send_quote" says "send": a word for sending, and what is sent cannot be taken back.
What it can reach
- outboundThe name "bull_send_quote" says "send": it sends or publishes something to other people.
- outboundThe input takes a URL (input.webhook): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it 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.
Changes things 10Claude Code: ask
bull_accept_quoteUse as a BUYER to accept a quote.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
bull_attach_dealUse as a BUYER after sending createDeal: report the dealId.No findings
Why it is in this group
- The name "bull_attach_deal" says "attach": a word for a change.
Description, as the server wrote it 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.
bull_counter_quoteUse as a BUYER to negotiate: propose a different total price (and optionally a different token amount) on a pending quote.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
bull_create_rfqUse 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, a non-custodial atomic OTC settlement layer.Can send data outNo findings
Why it is in this group
- The name "bull_create_rfq" says "create": a word for a change.
What it can reach
- outboundThe input takes a URL (input.webhook): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it 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, a non-custodial atomic OTC settlement layer. 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.
bull_depositUse as a SELLER to submit the signed permit from bull_deposit_plan.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
bull_deposit_planUse 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 + fu…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
bull_infoUse first to see what Bull is: supported chains, escrow contract, fee tiers, minimum size and auth rules.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Use first to see what Bull is: supported chains, escrow contract, fee tiers, minimum size and auth rules. Public. Bull is a non-custodial atomic OTC/RFQ settlement layer.
bull_reject_quoteUse as a BUYER to reject a quote you do not want.No findings
Why it is in this group
- The name "bull_reject_quote" says "reject": a word for a change.
Description, as the server wrote it 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.
bull_revise_quoteUse as a SELLER to change the price and/or token amount of your own pending quote, for example to meet the buyer's counter.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
bull_statsUse to check Bull's track record: number of settled deals, total volume, open RFQs and the latest settled deals, read from the escrow contract.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
Only reads 5Show 5 read-only tools
bull_get_dealUse to verify any escrow deal onchain: open, settled or cancelled, and whether buyer and seller have funded.No findings
Why it is in this group
- The name "bull_get_deal" says "get": a word for reading.
Description, as the server wrote it 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.
bull_get_quotesUse as a BUYER to read the sealed quotes on your own RFQ: seller, token amount, total price, counter state, deal status.No findings
Why it is in this group
- The name "bull_get_quotes" says "get": a word for reading.
Description, as the server wrote it 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.
bull_get_receiptUse 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.No findings
Why it is in this group
- The name "bull_get_receipt" says "get": a word for reading.
Description, as the server wrote it 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.
bull_list_rfqsUse 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).No findings
Why it is in this group
- The name "bull_list_rfqs" says "list": a word for reading.
Description, as the server wrote it 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.
bull_quote_statusUse as BUYER or SELLER to check a quote and its onchain deal: status (pending, confirmed, funded, released), dealId, counter, who has funded.No findings
Why it is in this group
- The name "bull_quote_status" says "status": a word for reading.
Description, as the server wrote it 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.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out2
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 19, 2026, 17:21 UTC, unchanged since Nov 19, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 21
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 21 tools that change things (2 irreversible, 19 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://www.bull.family/api/mcp: tools/list returned 29 tools to an anonymous client, including bull_stream_create (irreversible), bull_send_quote (irreversible), bull_consent_plan (write), bull_consent (write), bull_settle (write) and 16 more
Posture changes
- Nov 19, 2026
- Tools that change things, listed without credentials: 11 to 21
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Tools that change things, listed without credentials: 11 -> 21.View diff
- Tools that change things, listed without credentials: 11 to 21
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http bull-otc https://www.bull.family/api/mcpclaude mcp add --transport http bull-otc https://www.bull.family/api/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__bull-otc__bull_list_rfqs",
"mcp__bull-otc__bull_get_quotes",
"mcp__bull-otc__bull_quote_status",
"mcp__bull-otc__bull_get_deal",
"mcp__bull-otc__bull_get_receipt"
],
"ask": [
"mcp__bull-otc__bull_create_rfq",
"mcp__bull-otc__bull_send_quote",
"mcp__bull-otc__bull_counter_quote",
"mcp__bull-otc__bull_revise_quote",
"mcp__bull-otc__bull_accept_quote",
"mcp__bull-otc__bull_attach_deal",
"mcp__bull-otc__bull_deposit_plan",
"mcp__bull-otc__bull_deposit",
"mcp__bull-otc__bull_reject_quote",
"mcp__bull-otc__bull_stats",
"mcp__bull-otc__bull_info"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as bull-otc. Review it before you use it.
Capability tags behind 2 rules
- mcp__bull-otc__bull_create_rfq outbound
- mcp__bull-otc__bull_send_quote outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.TMcodingarc/bull-otc/verify?hash=3792f5d7733ecd2d72a997aafb4752c8883aae4e2ecd4cf47aeb7dc001661715" | jq -e '.changed == false'Pinned hash 3792f5d7733e, from Nov 11, 2026, 19:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.TMcodingarc/bull-otc/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.TMcodingarc/bull-otc)Source: MCP Registry · repository. Synced Nov 11, 2026, 19:17 UTC.
Bull OTC MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Bull OTC MCP server safe?
- No scan can promise that. What its definitions show: 16 tools, 11 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Bull OTC MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Bull OTC MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: bull_send_quote.
What tools does the Bull OTC MCP server have?
- 16 tools: 1 irreversible, 10 write, 5 read. bull_send_quote, bull_create_rfq, bull_counter_quote, bull_revise_quote, bull_accept_quote, bull_attach_deal, bull_deposit_plan, bull_deposit and 8 more.
Does the Bull OTC MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Bull OTC MCP server send data to outside services?
- 2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): bull_create_rfq and bull_send_quote.
Has the Bull OTC MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 11, 2026.