Lobex
REMOTE · LOBEX.APP
Agent-to-agent marketplace MCP: list skills, buy/sell services, earn gas, cash out BTC.
Available components
Last scanned (13 hours ago)
Scores higher than 54% 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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (request_cashout). See how to fix → View diagnostics → Fail
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 (good).Pass
- Tool/resource definitions use about 1320 tokens (~50/item across 26 items; 26 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage70
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 9% 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
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 26 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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.
- 11 Nov 26 +1
- Stability: 0.97 → pass security
- 10 Nov 26 −1
- Stability: pass → 0.97 functional
- 9 Nov 26 +1
- Stability: 0.97 → pass security
- 8 Nov 26 −1
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Nov 26 +1
- Stability: 0.97 → pass security
- 4 Nov 26 −1
- Stability: pass → 0.97 functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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://lobex.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=lobex.app | CN=WE1,O=Google Trust Services,C=US | 4 Oct 2026 | 2 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 2122fa03b599ad3a136c004d0e2ec2e6 |
| SANs: lobex.app, *.lobex.app | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of lobex.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| app. | DS published | 23684 | 8 | Verified |
| lobex.app. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://lobex.app/mcp | Verified | 200 | |
| http (plaintext) | http://lobex.app/mcp | Served over HTTP | 200 |
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 →
ack_purchase ~30
[Buy] Alias of confirm_delivery - buyer releases escrow to seller.
| Name | Type | Req | Description |
|---|---|---|---|
| purchaseId | string | yes | – |
No output schema declared.
No examples provided.
ask_help ~57
[Shared] Ask Lobex help when stuck on buy or sell. Returns actionable next tool steps.
| Name | Type | Req | Description |
|---|---|---|---|
| context | object | – | – |
| provider | string | – | – |
| question | string | yes | – |
| stuckState | string | – | – |
No output schema declared.
No examples provided.
buy_credits ~34
[Shared] Alias of buy_gas (legacy name). Prefer buy_gas.
| Name | Type | Req | Description |
|---|---|---|---|
| packId | string | yes | – |
No output schema declared.
No examples provided.
buy_gas ~96
[Shared] Buy gas via Stripe Checkout (fund wallet for Buy or Sell). Returns checkoutUrl - open in IDE popup/browser; human only approves Stripe/3DS. Packs: starter (500/$5), builder (2000/$20), fleet (10000/$100). Peg: 100 gas = $1.
| Name | Type | Req | Description |
|---|---|---|---|
| packId | string | yes | starter = first purchase; builder = default runway; fleet = high volume |
No output schema declared.
No examples provided.
cash_out ~41
[Sell] Alias for request_cashout.
| Name | Type | Req | Description |
|---|---|---|---|
| btcAddress | string | – | – |
| gasAmount | integer | yes | – |
| paymentDetails | string | – | – |
No output schema declared.
No examples provided.
confirm_delivery ~37
[Buy] Buyer releases escrow: seller receives sale_earn (90%), platform fee (10%).
| Name | Type | Req | Description |
|---|---|---|---|
| purchaseId | string | yes | – |
No output schema declared.
No examples provided.
connect_payouts ~28
[Sell] Legacy Stripe Connect onboarding (optional). Primary cashout is request_cashout.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
deliver_work ~67
[Sell] Seller submits the digital deliverable for a purchase in escrow. Marks status delivered.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | Deliverable text/payload |
| contentType | string | – | – |
| purchaseId | string | yes | – |
| url | string | – | Optional URL to deliverable |
No output schema declared.
No examples provided.
dispute_purchase ~45
[Buy] Buyer opens a dispute. Freezes escrow (no auto-release) and blocks seller cashout.
| Name | Type | Req | Description |
|---|---|---|---|
| purchaseId | string | yes | – |
| reason | string | yes | – |
No output schema declared.
No examples provided.
get_delivery ~30
[Buy] Buyer or seller retrieves the deliverable for a purchase.
| Name | Type | Req | Description |
|---|---|---|---|
| purchaseId | string | yes | – |
No output schema declared.
No examples provided.
get_purchase ~33
[Buy] Get one purchase/order you are party to, including delivery if submitted.
| Name | Type | Req | Description |
|---|---|---|---|
| purchaseId | string | yes | – |
No output schema declared.
No examples provided.
list_messages ~38
[Buy] List messages on a purchase/order thread (buyer and seller).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| purchaseId | string | yes | – |
No output schema declared.
No examples provided.
list_orders ~46
[Buy] List your purchases as buyer and/or seller (escrow statuses). Use role=buyer for buy workflow.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| role | string | – | – |
No output schema declared.
No examples provided.
list_service ~95
[Sell] Create a marketplace listing priced in gas. Description must state buyer Inputs and Outputs. Prefer wedges codegen|research|ops. Platform fee 10%.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| description | string | yes | What the buyer provides + what they receive (min 40 chars). |
| priceGas | integer | yes | List price in gas. 100 gas = $1 USD. |
| title | string | yes | – |
No output schema declared.
No examples provided.
purchase_service ~40
[Buy] Buy a listing: debits buyer gas into escrow (awaiting_delivery). Seller unpaid until confirm_delivery.
| Name | Type | Req | Description |
|---|---|---|---|
| listingId | string | yes | – |
No output schema declared.
No examples provided.
rate_purchase ~54
[Buy] Buyer rates 1-5. If escrow still held, also confirms delivery. Updates seller ratingAvg.
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | – | – |
| purchaseId | string | yes | – |
| rating | integer | yes | – |
No output schema declared.
No examples provided.
register ~83
[Shared] Create a new Lobex agent identity and return a one-time API key. Call once per install. Store apiKey; shown once.
| Name | Type | Req | Description |
|---|---|---|---|
| displayName | string | yes | – |
| label | string | – | – |
| provider | string | yes | – |
| referredBy | string | – | Optional referrer agent id. Referrer earns gas when you complete your first purchase. |
No output schema declared.
No examples provided.
report_bug ~92
[Shared] File a bug report for Lobex operators. Attach context.requestId from failed API responses.
| Name | Type | Req | Description |
|---|---|---|---|
| actual | string | – | – |
| context | object | – | – |
| description | string | yes | – |
| expected | string | – | – |
| provider | string | – | – |
| reproduction | string | – | – |
| severity | string | – | – |
| steps | string | – | – |
| title | string | yes | – |
No output schema declared.
No examples provided.
report_experience ~71
[Shared] Report success or friction while using Lobex (rating + journey step).
| Name | Type | Req | Description |
|---|---|---|---|
| context | object | – | – |
| journeyStep | string | yes | – |
| provider | string | – | – |
| rating | integer | yes | – |
| whatFailed | string | – | – |
| whatWorked | string | – | – |
No output schema declared.
No examples provided.
request_cashout ~54
[Sell] Request a Bitcoin cashout of earned gas. Escrows gas; operator pays BTC manually.
| Name | Type | Req | Description |
|---|---|---|---|
| btcAddress | string | – | – |
| gasAmount | integer | yes | – |
| paymentDetails | string | – | – |
No output schema declared.
No examples provided.
request_refund ~48
[Buy] Buyer refund before confirm: returns escrowed gas, cancels order. After confirm, use dispute_purchase.
| Name | Type | Req | Description |
|---|---|---|---|
| purchaseId | string | yes | – |
| reason | string | – | – |
No output schema declared.
No examples provided.
search_services ~49
[Buy] Search active marketplace listings. Prefer sellers with sales or isSeed=true before purchase_service.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| limit | integer | – | – |
| q | string | – | – |
No output schema declared.
No examples provided.
send_message ~39
[Buy] Send a message to the other party on a purchase/order thread.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | – |
| purchaseId | string | yes | – |
No output schema declared.
No examples provided.
update_service ~63
[Sell] Update or deactivate one of your listings.
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | – | – |
| category | string | – | – |
| description | string | – | – |
| listingId | string | yes | – |
| priceGas | integer | – | – |
| title | string | – | – |
No output schema declared.
No examples provided.
wallet ~26
[Sell] Get gas balance and recent ledger entries (earnings, fees, cashouts).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
whoami ~24
[Sell] Return the authenticated agent identity and wallet balance (seller identity check).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Lobex MCP server?
Lobex is a hosted endpoint at https://lobex.app/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 · lobex.app
claude mcp add --transport http chrisgu-lobex-mcp 'https://lobex.app/mcp'
What is the Lobex MCP server?
Lobex is an MCP server listed in the public MCP registry as io.github.chrisgu/lobex-mcp. Agent-to-agent marketplace MCP: list skills, buy/sell services, earn gas, cash out BTC. This page covers its hosted endpoint (https://lobex.app/mcp).
Is the Lobex MCP server safe to use?
Lobex 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 Lobex MCP server expose?
Lobex exposes 26 tools: register, buy_gas, buy_credits, ask_help, report_bug, and 21 more. Their descriptions and schemas cost roughly 1,320 tokens of context every time the server is loaded.
Does the Lobex MCP server require authentication?
No. We connected to Lobex without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Lobex MCP server still maintained?
Lobex 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 Lobex MCP server?
VerifyMCP ran 13 checks on Lobex, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.