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.

O-Exchange Compute Futures

REMOTE · A959E52DB0499CEF3.APP.WORKBUDDY.HOST

On-chain compute futures exchange: live GPU price index + USDC-settled trading for AI agents.

−33 this week 0 Trust /100

Last scanned (34 days ago)

Scores higher than 0% of remote servers

Unreachable for 7 days in a row. Last reached 10 Oct 2026.

Category Crypto and Web3

Dead

Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.

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 Security57
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (5)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport

Checks we could not complete (6)

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 yet verified: we couldn't confirm whether this endpoint requires it.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

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 →

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.

  • 18 Oct 26 −7

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 17 Oct 26 −6
    • HSTS header: unverified → fail ▼ security
  • 16 Oct 26 −7

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 15 Oct 26 −6
    • HSTS header: fail → unverified ▼ security
  • 14 Oct 26 −7

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 12 Oct 26 0
    • Transport: pass → fail ▼ security
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
  • 1 Oct 26 33

    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 18 Oct 2026 · Probed https://a959e52db0499cef3.app.workbuddy.host/mcp

TLS valid

Negotiated TLS 1.2 with TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.workbuddy.host,O=Tencent Technology (Shenzhen) Company Limited,L=Shenzhen,ST=Guangdong Province,C=CN CN=DigiCert Secure Site OV G2 TLS CN RSA4096 SHA256 2022 CA1,O=DigiCert\, Inc.,C=US 10 Sept 2026 27 Mar 2027 RSA 2048 SHA256-RSA 42d0278b23e5092a1c8540bc7c33f21
SANs: *.workbuddy.host, workbuddy.host, *.app-staging.workbuddy.host, *.app-tencent.workbuddy.host, *.app.workbuddy.host, *.apps-staging.workbuddy.host, *.apps.workbuddy.host
CN=DigiCert Secure Site OV G2 TLS CN RSA4096 SHA256 2022 CA1,O=DigiCert\, Inc.,C=US (CA) CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US 15 Dec 2022 14 Dec 2032 RSA 4096 SHA256-RSA 4c1b960191fcabedcda9301a6cd78c3

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of a959e52db0499cef3.app.workbuddy.host. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
host. DS published 29155 13 Verified
workbuddy.host. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 504

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://a959e52db0499cef3.app.workbuddy.host/mcp Unreachable
http (plaintext) http://a959e52db0499cef3.app.workbuddy.host/mcp HTTPS enforced 302 HTTPS://a959e52db0499cef3.app.workbuddy.host/mcp
MCP tools

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 →

No tool schema has been captured from this endpoint yet.

Install

How do I install the O-Exchange Compute Futures MCP server?

O-Exchange Compute Futures is a hosted endpoint at https://a959e52db0499cef3.app.workbuddy.host/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 · a959e52db0499cef3.app.workbuddy.host

# add to Claude Code
claude mcp add --transport http host-workbuddy-app-a959e52db0499cef3-oexchange-c 'https://a959e52db0499cef3.app.workbuddy.host/mcp'
Common questions

What is the O-Exchange Compute Futures MCP server?

O-Exchange Compute Futures is an MCP server listed in the public MCP registry as host.workbuddy.app.a959e52db0499cef3/oexchange-compute-futu…. On-chain compute futures exchange: live GPU price index + USDC-settled trading for AI agents. This page covers its hosted endpoint (https://a959e52db0499cef3.app.workbuddy.host/mcp).

Is the O-Exchange Compute Futures MCP server safe to use?

O-Exchange Compute Futures scores 0 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.

Does the O-Exchange Compute Futures MCP server require authentication?

Its publisher declares no required credentials for O-Exchange Compute Futures. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the O-Exchange Compute Futures MCP server still maintained?

O-Exchange Compute Futures has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 10 October 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 O-Exchange Compute Futures MCP server?

VerifyMCP ran 5 checks on O-Exchange Compute Futures, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 1 more. 6 items could not be completed, a gap on our side rather than a finding about O-Exchange Compute Futures: Authorization, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. 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.