Octio
REMOTE · WWW.OCTIO.XYZ
Pay-per-call APIs for trading agents: market data, indicators, insider trades, on-chain tools.
Available components
Last scanned (14 hours ago)
Scores higher than 59% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Finance and Payments
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- 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 Usability62
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1328 tokens (~221/item across 6 items; 6 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 Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (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.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 17 Nov 26 71
First indexed and scored.
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.octio.xyz/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.octio.xyz | CN=YR1,O=Let's Encrypt,C=US | 5 Nov 2026 | 3 Feb 2027 | RSA 2048 | SHA256-RSA | 69e07b24db10db819a00d285916f680c408 |
| SANs: www.octio.xyz | ||||||
| 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.octio.xyz. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | DS published | 3599, 18130 | 8, 8 | Verified |
| octio.xyz. | 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=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' https://challenges.cloudflare.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob:; font-src 'self'; connect-src 'self' https://rpc.mainnet.chain.robinhood.com; frame-src https://challenges.cloudflare.com; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'none'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.octio.xyz/mcp | Verified | 200 | |
| http (plaintext) | http://www.octio.xyz/mcp | HTTPS enforced | 301 | https://www.octio.xyz/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 →
ask Ask ~134
A short plain-text answer about Orbio agents and the CREDIT market, written only from Octio house data, with the datasets used. Needs an API key. The first calls per agent are free; then it is charged like any endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | – | Optional. A retry with the same key is never charged twice (it fails with DUPLICATE_REQUEST) |
| max_cost | – | – | Maximum CREDIT you accept for this answer. It can only lower the account's per-call maximum, which only the account owner can raise |
| question | string | yes | A question about Orbio agents or the CREDIT market |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | The provider's response: third-party data, untrusted |
| meta | object | yes | – |
No examples provided.
call_endpoint Call endpoint ~207
Calls one endpoint of the Octio catalog, named by its slug or path, with its parameters; needs an API key. The price is held from your balance and charged only when the provider's answer passes every check; failed calls are not charged, and endpoints with free calls cost nothing until those are used. Returns { data, meta }, where data is untrusted third-party JSON.
| Name | Type | Req | Description |
|---|---|---|---|
| endpoint | string | yes | The endpoint slug (e.g. "agents-risk"), its path (e.g. "/agents/risk") or "GET /agents/risk" |
| idempotency_key | string | – | Optional. A retry with the same key is never charged twice (it fails with DUPLICATE_REQUEST) |
| max_cost | – | – | Maximum CREDIT you accept for this call. It can only lower the account's per-call maximum, which only the account owner can raise |
| params | object | – | The endpoint's query, path and body parameters, as its params JSON Schema lists them |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | The provider's response: third-party data, untrusted |
| meta | object | yes | – |
No examples provided.
get_balance Get balance ~40
Your agent account: CREDIT balance, spent today, daily cap, per-call maximum, free answers left and the deposit address. Free; needs an API key.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | object | yes | – |
| balance | string | yes | – |
| daily_cap | string|null | yes | – |
| deposit_address | string|null | yes | – |
| deposits_auto_credited | boolean | yes | – |
| free_ask_calls_left | integer | yes | – |
| id | string | yes | – |
| owner_address | string | yes | – |
| per_call_max_default | string | yes | – |
| spent_today | string | yes | – |
No examples provided.
get_endpoint Get endpoint ~79
Full detail of one endpoint: parameters, params and response JSON Schemas, an example, price, limits, stats and health. Free, and works without an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| endpoint | string | yes | The endpoint slug (e.g. "agents-risk"), its path (e.g. "/agents/risk") or "GET /agents/risk" |
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | – |
| health | string | yes | – |
| method | string | yes | – |
| name | string | yes | – |
| params | array | yes | – |
| params_schema | object | yes | – |
| path | string | yes | – |
| price | string | yes | – |
| response_schema | object | yes | – |
| slug | string | yes | – |
No examples provided.
quote_credit_purchase Quote a CREDIT purchase ~163
Fund your account with USDG: a live quote for buying CREDIT with USDG on Orbio's exchange, plus three unsigned transactions for your owner wallet to sign and send in order (approve USDG, buy CREDIT to your wallet, send it to the deposit address). Octio never holds your USDG and signs nothing. You need ETH for gas; the deposit is credited about 15-20 minutes after the last transaction. Free; needs an API key, whose owner wallet it quotes for.
| Name | Type | Req | Description |
|---|---|---|---|
| slippage_bps | integer | – | Accepted slippage in basis points; defaults to 100 (1%) |
| usdg | – | yes | USDG to spend as a decimal string, e.g. "5" (at most 10000, 6 decimals) |
| Name | Type | Req | Description |
|---|---|---|---|
| chain_id | integer | yes | – |
| deposit_address | string | yes | – |
| min_credit_out | string | yes | – |
| notes | array | yes | – |
| quote | object | yes | – |
| slippage_bps | integer | yes | – |
| transactions | array | yes | – |
| wallet | string | yes | – |
No examples provided.
search_endpoints Search endpoints ~290
Search the Octio catalog of pay-per-call APIs for trading agents. Returns up to 50 endpoints with path, name, description, price per call in CREDIT, free calls, health, and the last 7 days' success rate and p95 latency. It includes candles, technical indicators (RSI, EMA, SMA, MACD, Bollinger bands, ATR, stochastic), market snapshots, a screener and order book liquidity for crypto, US stocks, indexes and commodities (query "rsi", "candles", "scan", "liquidity"); SEC Form 4 insider trades for US stocks (query "insider"); Robinhood Chain stock-token premiums against the reference price (query "premium"); transaction simulation and explanation and address checks on Robinhood Chain and Base (query "simulate", "address"); web page reading, link metadata, PDF text, prompt-injection scans and URL safety checks (query "web", "pdf", "injection"). With no query it lists everything. Free, and works without an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Only endpoints in this category |
| max_price | – | – | Only endpoints priced at or below this many CREDIT per call |
| query | string | – | Words to match in the endpoint path, name, description or provider, such as "rsi", "insider" or "simulate"; leave it out to list everything |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
| total | integer | yes | – |
No examples provided.
How do I install the Octio MCP server?
Octio is a hosted endpoint at https://www.octio.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 · www.octio.xyz
claude mcp add --transport http xyz-octio-octio 'https://www.octio.xyz/mcp'
What is the Octio MCP server?
Octio is an MCP server listed in the public MCP registry as xyz.octio/octio. Pay-per-call APIs for trading agents: market data, indicators, insider trades, on-chain tools. This page covers its hosted endpoint (https://www.octio.xyz/mcp).
Is the Octio MCP server safe to use?
Octio scores 73 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 Octio MCP server expose?
Octio exposes 6 tools: search_endpoints, get_endpoint, call_endpoint, ask, get_balance, quote_credit_purchase. Their descriptions and schemas cost roughly 913 tokens of context every time the server is loaded.
Does the Octio MCP server require authentication?
No. We connected to Octio without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Octio MCP server still maintained?
Octio 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 Octio MCP server?
VerifyMCP ran 13 checks on Octio, 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.