# Apiosk Connect (remote · mcp.apiosk.com)

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

- Trust score: 59/100 (low)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.apiosk.com`: 59/100 (this document), [markdown](https://verifymcp.io/servers/obcraft-apiosk-mcp/mcp.md), [page](https://verifymcp.io/servers/obcraft-apiosk-mcp/mcp)
- npm · `@apiosk/mcp`: 35/100, [markdown](https://verifymcp.io/servers/obcraft-apiosk-mcp/apiosk-mcp.md), [page](https://verifymcp.io/servers/obcraft-apiosk-mcp/apiosk-mcp)
- pypi · `apiosk-mcp`: 36/100, [markdown](https://verifymcp.io/servers/obcraft-apiosk-mcp/apiosk-mcp-2.md), [page](https://verifymcp.io/servers/obcraft-apiosk-mcp/apiosk-mcp-2)

## Channel facts

- Endpoint: `https://mcp.apiosk.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.7.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (apiosk_execute).
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 36/100
  - 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 95/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 82% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### Claude

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

### Codex

```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
    }
  }
}
```

### OpenClaw

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

### Hermes

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

### Other

```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 recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 59, +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.

### 2026-08-01 (score 58, +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.

### 2026-07-31 (score 57, +2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 55, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 55, +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.

### 2026-07-28 (score 54, +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.

### 2026-07-27 (score 53, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 53)

First indexed and scored.

## MCP tools (11)

### `apiosk_help` (~96 tokens)

Explain what Apiosk MCP is, how to connect it, how auth and USDC/x402 payments work, and the recommended workflow for discovery, wallets, and publishing.

Input parameters:

- `topic` (string): Optional help topic. Defaults to overview. Use 'discovery' to learn which live sources apiosk_discover searches (Apiosk catalog + Coinbase Bazaar + well-known); use 'rails' for how USDC/x402 settleme…

### `apiosk_discover` (~352 tokens)

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 parameters:

- `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, required): 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…

### `apiosk_explore` (~79 tokens)

Browse Apiosk listing groups and explore one group at a time before narrowing with search.

Input parameters:

- `limit` (number)
- `listing_type` (string)
- `offset` (number)
- `order` (string)
- `search` (string): Optional free-text search when listing_type is set.
- `sort` (string)

### `apiosk_inspect_x402` (~148 tokens)

Read an arbitrary URL's x402 payment terms (price, asset, network, payTo) WITHOUT paying. Use this on an external result's `url` from apiosk_discover before paying: it makes one unauthenticated request, parses the 402 offer, and returns the exact amount so you can confirm the price with the user. Read-only; never spends. apiosk_execute (for Apiosk catalog listings) does not need this.

Input parameters:

- `method` (string): HTTP method the resource charges on. Defaults to GET.
- `url` (string, required): The https:// URL of the x402 resource to inspect (e.g. a federated listing's resource URL).

### `apiosk_execute` (~103 tokens)

Execute any Apiosk API by slug through the uniform /execute contract.

Input parameters:

- `input` (object): Raw JSON body for the default operation, or the envelope input field when operation is provided.
- `operation` (string): Optional explicit operation id or path.
- `path_params` (object): Optional path parameter override when using the execute envelope.
- `query` (object): Optional query override when using the execute envelope.
- `slug` (string, required): Apiosk API slug.

### `apiosk_fetch_paid` (~322 tokens)

Pay an EXTERNAL x402 endpoint (one Apiosk does not host) from the connected wallet and return its data. Use this only for external results from apiosk_discover (executable_via='apiosk_fetch_paid'); for Apiosk catalog listings use apiosk_execute. REQUIRED: call apiosk_inspect_x402 on the url first, tell the user the exact price, and pass that amount as confirmed_price_usdc — the gateway refuses if the live price is higher. The gateway enforces the wallet's per-tx/daily spend limits. Base + USDC only.

Input parameters:

- `body` (object): Optional JSON request body for POST/PUT/PATCH.
- `confirmed_price_usdc` (number, required): The price you read via apiosk_inspect_x402 and confirmed with the user. The gateway refuses if the live price exceeds this.
- `headers` (object): Optional extra request headers (allowlisted server-side; secrets are never accepted here).
- `idempotency_key` (string): Optional. Reuse the same key to safely retry without paying twice; a fresh one is generated if omitted.
- `max_price_usdc` (number): Optional additional per-call ceiling. The gateway also enforces the wallet's per-tx and daily limits.
- `method` (string): HTTP method for the provider request. Defaults to GET.
- `query` (object): Optional query parameters to send to the provider.
- `url` (string, required): The external x402 resource URL to pay and fetch (from a discovery result's `url`).

### `apiosk_get_api` (~44 tokens)

Fetch full listing detail and agent metadata for a specific Apiosk API slug.

Input parameters:

- `slug` (string, required): Apiosk API slug, for example 'agent-json-diff'.

### `apiosk_search` (~137 tokens)

Search and browse the Apiosk catalog by capability, price, or category. For browsing/filtering the catalog. When the goal is to fulfil a user request with real paid data ('get me the live X'), prefer apiosk_discover, which decomposes the need and ranks the best endpoints across sources.

Input parameters:

- `category` (string): Optional category filter.
- `limit` (number): Maximum number of APIs to return.
- `offset` (number): Pagination offset.
- `order` (string): Sort direction.
- `search` (string): Free-text search over API names and descriptions.
- `sort` (string): Sort order for results.

### `apiosk_payment_guide` (~115 tokens)

Explain how to pay through the Apiosk gateway. Returns a buyer guide (how an agent settles a paid API call over USDC/x402, tailored to the current auth) and a provider guide (how to publish an API and get paid). Pass slug to scope buyer guidance to one listing, or role to pick a side.

Input parameters:

- `role` (string): Which side to explain. Defaults to both.
- `slug` (string): Optional API slug to scope buyer guidance (price, payment steps) to one listing.

### `apiosk_list_wallets` (~36 tokens)

List the signed-in user's managed Apiosk wallets. Requires an Apiosk dashboard session from local env auth or hosted MCP authorization.

### `publish_x402_route` (~301 tokens)

Publish a paid x402 route

Publish an API endpoint as a paid x402 route on the Apiosk gateway. The route gets a paid URL that returns 402 Payment Required until the caller pays in USDC, then forwards to your upstream API. New routes enter Apiosk's review queue (status pending_review) and go live on approval. Requires an Apiosk provider token (Authorization: Bearer sk_live_…).

Input parameters:

- `currency` (string): Only USDC is supported.
- `description` (string)
- `input_schema` (object)
- `method` (string): Defaults to GET.
- `name` (string, required): Human-readable API name, e.g. 'Weather API'.
- `network` (string): Settlement network. Defaults to base.
- `output_schema` (object)
- `path` (string): Public path under the route's gateway slug, e.g. /weather. Defaults to the last segment of upstream_url.
- `price` (string|number, required): Price per call in USDC, e.g. "0.01".
- `settlement_address` (string, required): Wallet that receives 98% of each payment (Apiosk keeps a 2% platform fee).
- `slug` (string): Optional gateway slug override (lowercase letters, numbers, hyphens). Defaults to a slug derived from name.
- `tags` (array)
- `upstream_url` (string, required): Full HTTPS URL of your existing endpoint the gateway forwards paid requests to.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/obcraft-apiosk-mcp/mcp#diagnostics

## Score history

- 2026-08-03: 59
- 2026-08-02: 58
- 2026-08-01: 58
- 2026-07-31: 57
- 2026-07-30: 55
- 2026-07-29: 55
- 2026-07-28: 54
- 2026-07-27: 53
- 2026-07-26: 53

## Links

- Remote endpoint: https://mcp.apiosk.com/mcp
- Repository: https://github.com/obcraft/apiosk-mcp
- Website: https://apiosk.com/
- Changelog RSS feed: https://verifymcp.io/servers/obcraft-apiosk-mcp/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/obcraft-apiosk-mcp/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/obcraft-apiosk-mcp/mcp