Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

OwlGate

REMOTE · API.OWLGATE.XYZ

TapeOut rigs: fair prices, below-fair BNB deals, unsigned buy tx, X Layer voucher orders.

Available components

70 Trust /100

Last scanned (45 minutes ago)

Scores higher than 55% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

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 Security74
Transport & Reachability100
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 761 tokens (~152/item across 5 items; 5 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 Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 93% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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
Changelog

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.

  • 5 Nov 26 −1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool coverage: 100% → 93% ▼ functional
    • Schema quality: pass → fail ▼ functional
    • New tool “buy” functional
    • New tool “deals” functional
    • New tool “xl_build_order” functional
    • New tool “xl_market” functional
  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 31 Oct 26 69

    First indexed and scored.

Diagnostics

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 5 Nov 2026 · Probed https://api.owlgate.xyz/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=owlgate.xyz CN=YE2,O=Let's Encrypt,C=US 26 Oct 2026 24 Jan 2027 ECDSA 256 ECDSA-SHA384 60e603d30d9aaecfa1c8cf83b6521bf222c
SANs: *.owlgate.xyz, owlgate.xyz
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.owlgate.xyz. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
xyz. present 3599, 18130 8, 8 Verified
owlgate.xyz. absent 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
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.owlgate.xyz/mcp Verified 200
http (plaintext) http://api.owlgate.xyz/mcp HTTPS enforced 301 https://api.owlgate.xyz/mcp
MCP tools · 5 exposed · ~686 tokens

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 →

Tool Tokens
buy ~119

Unsigned transaction to buy one TapeOut rig listed on BNB Chain through the OwlGate router (price + 0.75% OwlGate fee), dry-run from `from`. Use cp + tid from a deals or fair_price item. Returns steps for the buyer to sign and send with their own wallet; OwlGate never signs or holds funds.

NameTypeReqDescription
cpstringyesCPU contract address of the rig (0x…)
fromstringyesBuyer wallet address (0x…)
tidstringyesRig token id

No output schema declared.

No examples provided.

deals ~182

TapeOut mining rigs on BNB Chain listed now below their fair price (median BNB price of recent sales of the same CPU and mining power), only where the fair price rests on at least 3 sales (raise minSales for stricter results; every item shows its sales count). Each item: price, fair, sales, hours, underFairPct and a buy link on owlgate.xyz (the buyer signs in their own wallet; OwlGate adds a 0.75% fee). Deepest discount first. Estimate, not advice; listings can sell at any time.

NameTypeReqDescription
limitnumber–Max items (default 10, max 50)
minDiscountPctnumber–Minimum % below fair (default 5)
minSalesnumber–Minimum sales behind the fair price (default 3, lowest allowed 3)

No output schema declared.

No examples provided.

fair_price ~157

Fair price of TapeOut rigs on BNB Chain: median BNB price of recent sales of the same CPU and mining power (12 h, else 24 h, 48 h, 7 d). With cp + vw/uw returns one quote; with no arguments returns rigs listed now with their fair price and discount vs fair, deepest discount first, each with a buy link on owlgate.xyz. Estimate, not advice.

NameTypeReqDescription
cpstring–CPU contract address (0x…), optional
limitnumber–Max listings when no cp is given (default 20, max 100)
uwnumber–U mining power, optional
vwnumber–V mining power, optional

No output schema declared.

No examples provided.

xl_build_order ~175

Unsigned steps to place an order on the X Layer voucher market (Seaport): kind list (sell one voucher you hold, price in OKB), offer (bid on one voucher, paid in WOKB) or coll (bid on any voucher). The seller pays a 0.75% OwlGate fee on fill. Steps: approve/wrap if needed, sign typed data (free), POST to /bids. The wallet signs itself; OwlGate never holds funds.

NameTypeReqDescription
daysnumber–Order lifetime in days (default 1)
fromstringyesWallet address (0x…)
kindstringyes–
pricestringyesPrice in OKB, 0.01 to 500
vstring–Voucher id (not needed for coll)

No output schema declared.

No examples provided.

xl_market ~53

TapeOut Rig Bridge vouchers on X Layer (chain 196): each voucher with mining power, BEM/day, holder, open asks and offers (OKB), plus the best voucher by BEM/day. Read-only.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the OwlGate MCP server?

OwlGate is a hosted endpoint at https://api.owlgate.xyz/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 · api.owlgate.xyz

# add to Claude Code
claude mcp add --transport http xyz-owlgate-fair-price 'https://api.owlgate.xyz/mcp'
Common questions

What is the OwlGate MCP server?

OwlGate is an MCP server listed in the public MCP registry as xyz.owlgate/fair-price. TapeOut rigs: fair prices, below-fair BNB deals, unsigned buy tx, X Layer voucher orders. This page covers its hosted endpoint (https://api.owlgate.xyz/mcp).

Is the OwlGate MCP server safe to use?

OwlGate scores 70 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 OwlGate MCP server expose?

OwlGate exposes 5 tools: fair_price, deals, buy, xl_market, xl_build_order. Their descriptions and schemas cost roughly 686 tokens of context every time the server is loaded.

Does the OwlGate MCP server require authentication?

No. We connected to OwlGate without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the OwlGate MCP server still maintained?

OwlGate is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.