Apiosk Connect

REMOTE · MCP.APIOSK.COM · 3 COMPONENTS · SCANNED AUG 3

Discover, pay for, execute, and publish APIs through Apiosk.

Available components

remote · mcp.apiosk.com 59 npm · @apiosk/mcp 35 pypi · apiosk-mcp 36

+6 this week 59 59 Trust /100

Trust breakdown (6 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 →

Endpoint Security57

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 (apiosk_execute). See how to fix → View diagnostics → Fail
HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
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 Usability36

0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
AI-judged instruction clarity (good).Pass
Context-footprint check failed: tool/resource definitions use about 2642 tokens (~220/item across 12 items; 11 tools + 1 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 Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage95

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
82% of tool parameters carry a description.Partial
Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Supports UI / widget rendering.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · mcp.apiosk.com

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http obcraft-apiosk-mcp https://mcp.apiosk.com/mcp

# ~/.codex/config.toml

[mcp_servers.obcraft-apiosk-mcp]
url = "https://mcp.apiosk.com/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "obcraft-apiosk-mcp": {
      "type": "remote",
      "url": "https://mcp.apiosk.com/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add obcraft-apiosk-mcp --url https://mcp.apiosk.com/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  obcraft-apiosk-mcp:
    url: "https://mcp.apiosk.com/mcp"

// mcp.json

{
  "mcpServers": {
    "obcraft-apiosk-mcp": {
      "type": "http",
      "url": "https://mcp.apiosk.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

3 Aug 26 +1

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

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
31 Jul 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 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
29 Jul 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.
28 Jul 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.
27 Jul 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
26 Jul 26 53

First indexed and scored.

Show 7 earlier entries Hide earlier entries

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 3 Aug 2026 · Probed https://mcp.apiosk.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=mcp.apiosk.com	CN=YE2,O=Let's Encrypt,C=US	7 Jun 2026	5 Sept 2026	ECDSA 256	ECDSA-SHA384	5cb67c9f9ad9030de3bbbcf803344959a82
SANs: mcp.apiosk.com
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

DNSSEC insecure

Validation of mcp.apiosk.com. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
com.	present	19718	13	Verified
apiosk.com.	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

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://mcp.apiosk.com/mcp	Verified	200
http (plaintext)	http://mcp.apiosk.com/mcp	HTTPS enforced	301	https://mcp.apiosk.com/mcp

MCP tools — 11 exposed · ~1,733 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.

Tool Tokens

apiosk_discover ~352

Find the best paid x402 API for a data capability across discovery sources (Apiosk catalog + federated external listings). Decompose the user's request into capability segments first, then call this once per capability. Returns a normalized, ranked list; each result's `executable_via` says whether to call apiosk_execute (Apiosk-settled) or apiosk_inspect_x402 + apiosk_fetch_paid (external). Use this instead of apiosk_search when the goal is 'get real paid data for X', not just browsing.

Input Output Examples

Name	Type	Req	Description
max_price_usdc	number	—	Optional per-call price ceiling in USDC. Results above this are dropped.
max_results	number	—	Maximum results to return (default 8, max 25).
probe_hosts	array	—	For the 'wellknown' source: explicit hostnames to probe for a /.well-known/x402 document (e.g. 'x402.example.com'). No speculative crawling — only hosts you name here are probed.
query	string	yes	The data capability to find, e.g. 'realtime USD exchange rate' or 'company registry lookup by domain'.
segments	array	—	Optional: the user's request pre-decomposed into distinct data capabilities. Each is searched and merged.
sources	array	—	Discovery sources to query. Default ['apiosk','bazaar']. Use ['all'] for every directly wired free REST source. Paid sources 'x402scan' and 'apify' are opt-in and return their payable endpoint for ap…