Apiosk Connect
REMOTE · MCP.APIOSK.COM · 3 COMPONENTS
Discover, pay for, execute, and publish APIs through Apiosk.
Available components
Last scanned (3 hours ago)
Scores higher than 19% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Developer Tools
Recent critical change
Authorization (20 Aug 2026). See the changelog before you install this server.
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 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. Claim this server and supply a read-only token to verify it and lift the score.
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.
- 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
- 25 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
- 9 Sept 26 0
- Endpoint reachability: reachable → behind authorisation ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Stability: fail → unverified ▼ security
- Authorization: partial → pass ▲ security
- First check of Authorization: partial security
- Capabilities: pass → unverified ▼ functional
- Schema quality: 0 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 8 Sept 26 0
- Tool “apiosk_approval_status” was removed ▼ security
- Tool “apiosk” was removed ▼ security
- Tool “apiosk_cancel_job” was removed ▼ security
- Tool “apiosk_compare” was removed ▼ security
- Tool “apiosk_connect” was removed ▼ security
- Tool “apiosk_execute_plan” was removed ▼ security
- Tool “apiosk_job_status” was removed ▼ security
- Tool “apiosk_plan” was removed ▼ security
- Tool “apiosk_resolve_job” was removed ▼ security
- Authorization: fail → partial ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “apiosk_discover” rewrote its description, which is the text the model reads security
- Tool “apiosk_execute” rewrote its description, which is the text the model reads security
- Tool “apiosk_execute” no longer declares itself destructive security
- Schema quality: 36% → 0% ▼ functional
- Tool coverage: 100% → 5% ▼ functional
- Schema quality: 237 → 262 ▼ functional
- “apiosk_discover” added a required parameter “question”, so existing callers break ▼ functional
- “apiosk_discover” dropped the required parameter “query” ▼ functional
- “apiosk_execute” dropped the required parameter “max_price_usdc” ▼ functional
- “apiosk_execute” dropped the required parameter “offer_token” ▼ functional
- “apiosk_execute” dropped the required parameter “prompt” ▼ functional
- Prompt “apiosk” was removed ▼ functional
- Prompt “cheapest_that_meets_my_bar” was removed ▼ functional
- Prompt “compare_providers” was removed ▼ functional
- Prompt “find_and_choose_an_api” was removed ▼ functional
- Resource “Apiosk connection card” was removed ▼ functional
- Resource “Apiosk offer approval card” was removed ▼ functional
- Resource “Apiosk offer picker” was removed ▼ functional
- Resource “Apiosk paid result canvas” was removed ▼ functional
- Resource “Apiosk plan approval card” was removed ▼ functional
- Resource “SKILL.md” was removed ▼ functional
- Resource “agents/openai.yaml” was removed ▼ functional
- Schema quality: excellent → fair functional
- New resource “Apiosk Gateway v2 interactive card” functional
- New resource “Apiosk Gateway v2 interactive card (compatible)” functional
- New resource “Apiosk v2 chatbot instructions” functional
- Server version: 1.8.1788699473 → 1.8.1788822441-gateway-v2 functional
- New tool “apiosk_sources” functional
- “apiosk_discover” added an optional parameter “context_delta” cosmetic
- “apiosk_discover” added an optional parameter “request_id” cosmetic
- “apiosk_discover” added an optional parameter “state” cosmetic
- “apiosk_execute” added an optional parameter “action_id” cosmetic
- “apiosk_execute” added an optional parameter “authorization_ref” cosmetic
- “apiosk_execute” added an optional parameter “idempotency_key” cosmetic
- “apiosk_execute” added an optional parameter “quote_ref” cosmetic
- “apiosk_execute” added an optional parameter “recover_task_ref” cosmetic
- “apiosk_execute” added an optional parameter “request_id” cosmetic
- “apiosk_execute” added an optional parameter “state” cosmetic
- “apiosk_execute” reworded the description of “input” cosmetic
- “apiosk_discover” dropped the optional parameter “choose” cosmetic
- “apiosk_discover” dropped the optional parameter “max_price_usdc” cosmetic
- “apiosk_discover” dropped the optional parameter “max_results” cosmetic
- “apiosk_discover” dropped the optional parameter “optimize_for” cosmetic
- “apiosk_discover” dropped the optional parameter “segments” cosmetic
- “apiosk_execute” dropped the optional parameter “approval_id” cosmetic
- “apiosk_execute” dropped the optional parameter “input_parts” cosmetic
- “apiosk_execute” dropped the optional parameter “operation” cosmetic
- “apiosk_execute” dropped the optional parameter “path_params” cosmetic
- “apiosk_execute” dropped the optional parameter “query” cosmetic
- Tool “apiosk_discover” changed its title: Apiosk discover → Plan a data request cosmetic
- Tool “apiosk_execute” changed its title: Apiosk run → Continue an Apiosk task cosmetic
- 7 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 1.8.1788643967 → 1.8.1788699473 functional
- 6 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- New tool “apiosk_execute_plan”, which the server declares destructive security
- New tool “apiosk_cancel_job”, which the server declares destructive security
- Tool “apiosk_compare” rewrote its description, which is the text the model reads security
- Schema quality: 50% → 36% ▼ functional
- Schema quality: 2546 → 4252 ▼ functional
- New resource “Apiosk plan approval card” functional
- New resource “SKILL.md” functional
- New resource “agents/openai.yaml” functional
- Server version: 1.7.1788550507 → 1.8.1788643967 functional
- New tool “apiosk_plan” functional
- New tool “apiosk_resolve_job” functional
- New tool “apiosk_job_status” functional
- 5 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 67% → 50% ▼ functional
- Schema quality: 287 → 254 ▲ functional
- New resource “Apiosk offer picker” functional
- New resource “Apiosk connection card” functional
- Server version: 1.7.1788272287 → 1.7.1788550507 functional
- “apiosk_discover” added an optional parameter “choose” cosmetic
- “apiosk” reworded the description of “max_results” cosmetic
- Tool “apiosk_execute” changed its title: Run the chosen API call → Apiosk run cosmetic
- Tool “apiosk_discover” changed its title: Find APIs that can do a job → Apiosk discover cosmetic
- Tool “apiosk_connect” changed its title: Check the Apiosk connection → Apiosk connect cosmetic
- Tool “apiosk_compare” changed its title: Compare the candidates on price and measured performance → Apiosk compare cosmetic
- Tool “apiosk_approval_status” changed its title: Check a purchase waiting for approval → Apiosk approval cosmetic
- Tool “apiosk” changed its title: Find the top provider for one question → Apiosk top pick cosmetic
- 2 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “apiosk_compare” rewrote its description, which is the text the model reads security
- Tool “apiosk_approval_status” rewrote its description, which is the text the model reads security
- Schema quality: 75% → 67% ▼ functional
- “apiosk_execute” made “prompt” required, so existing callers break ▼ functional
- “apiosk_execute” made “max_price_usdc” required, so existing callers break ▼ functional
- “apiosk_execute” made “offer_token” required, so existing callers break ▼ functional
- Schema quality: 342 → 287 ▲ functional
- Schema quality: good → excellent functional
- New prompt “apiosk” functional
- New resource “Apiosk offer approval card” functional
- Server version: 1.7.1788168147 → 1.7.1788272287 functional
- New tool “apiosk” functional
- “apiosk_execute” added an optional parameter “input_parts” cosmetic
- “apiosk_execute” added an optional parameter “approval_id” cosmetic
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 5 Nov 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 | 5 Oct 2026 | 3 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6477805050c031de43bc262173a06174f09 |
| 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 |
Background: What to check on a remote MCP endpoint →
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 Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer error="invalid_token", scope="mcp:tools", resource_metadata="https://mcp.apiosk.com/.well-known/oauth-protected-resource/mcp"
Bearer error="invalid_token", scope="mcp:tools", resource_metadata="https://mcp.apiosk.com/.well-known/oauth-protected-resource/mcp"| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
| www-authenticate | Bearer error="invalid_token", scope="mcp:tools", resource_metadata="https://mcp.apiosk.com/.well-known/oauth-protected-resource/mcp" |
Protected resource metadata
| Document | https://mcp.apiosk.com/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.apiosk.com/mcp |
| Authorisation server | https://mcp.apiosk.com/ |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.apiosk.com/mcp | Auth required | 401 | |
| http (plaintext) | http://mcp.apiosk.com/mcp | HTTPS enforced | 301 | https://mcp.apiosk.com/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 →
apiosk_discover Plan a data request ~82
Start a NEW data question; preserve source, entity and period requirements. Returns one plan, total price ceiling or required clarification. No provider purchase. Continue the SAME question through apiosk_execute with returned next_actions.
| Name | Type | Req | Description |
|---|---|---|---|
| context_delta | object | – | – |
| question | string | yes | – |
| request_id | string | – | – |
| state | object | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| billing | – | – | – |
| context_view | object | – | – |
| error_code | string | – | – |
| errors | array | – | – |
| idempotency_key | string | – | – |
| intent_ref | string|null | – | – |
| message | string | – | – |
| next_actions | array | – | – |
| proposal | – | – | – |
| protocol_version | string | – | – |
| recover_task_ref | string | – | – |
| request_id | string | – | – |
| result | – | – | – |
| retry_after_ms | integer | – | – |
| state | – | – | – |
| status | string | – | – |
No examples provided.
apiosk_execute Continue an Apiosk task ~148
Use a returned next_action to execute, supply input, select an entity, poll, cancel or read a result. Paid steps require saved App consent and the current quote_ref. For lost state, pass ONLY recover_task_ref. Never invent action IDs or change payment identity on retry.
| Name | Type | Req | Description |
|---|---|---|---|
| action_id | string | – | – |
| authorization_ref | string|null | – | – |
| idempotency_key | string | – | – |
| input | – | – | – |
| quote_ref | string|null | – | – |
| recover_task_ref | string | – | Recover state using a previously gateway-issued task reference. Reads only; does not execute or parse. |
| request_id | string | – | – |
| state | object | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| billing | – | – | – |
| context_view | object | – | – |
| error_code | string | – | – |
| errors | array | – | – |
| idempotency_key | string | – | – |
| intent_ref | string|null | – | – |
| message | string | – | – |
| next_actions | array | – | – |
| proposal | – | – | – |
| protocol_version | string | – | – |
| recover_task_ref | string | – | – |
| request_id | string | – | – |
| result | – | – | – |
| retry_after_ms | integer | – | – |
| state | – | – | – |
| status | string | – | – |
No examples provided.
apiosk_sources Browse Apiosk sources ~105
Find published data sources by name, category, sector, tag or capability. Browsing is free and paginated. Recommend sources that match the person's need. Keep replies concise and never expose protocol fields or describe catalog endpoints as chatbot tools.
| Name | Type | Req | Description |
|---|---|---|---|
| capability | string | – | – |
| category | string | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
| search | string | – | – |
| sector | string | – | – |
| tag | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| capabilities | array | – | – |
| categories | array | – | – |
| error_code | string | – | – |
| idempotency_key | string | – | – |
| message | string | – | – |
| next_offset | integer|null | – | – |
| notice | string | – | – |
| offset | integer | – | – |
| protocol_version | string | – | – |
| recover_task_ref | string | – | – |
| request_id | string | – | – |
| sectors | array | – | – |
| sources | array | – | – |
| tags | array | – | – |
| total | integer | – | – |
No examples provided.
How do I install the Apiosk Connect MCP server?
Apiosk Connect is a hosted endpoint at https://mcp.apiosk.com/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 · mcp.apiosk.com
claude mcp add --transport http obcraft-apiosk-mcp 'https://mcp.apiosk.com/mcp'
What is the Apiosk Connect MCP server?
Apiosk Connect is an MCP server listed in the public MCP registry as io.github.obcraft/apiosk-mcp. Discover, pay for, execute, and publish APIs through Apiosk. This page covers its hosted endpoint (https://mcp.apiosk.com/mcp).
Is the Apiosk Connect MCP server safe to use?
Apiosk Connect scores 36 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 Apiosk Connect MCP server expose?
Apiosk Connect exposes 3 tools: apiosk_sources, apiosk_discover, apiosk_execute. Their descriptions and schemas cost roughly 335 tokens of context every time the server is loaded.
Does the Apiosk Connect MCP server require authentication?
Yes. Apiosk Connect asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Apiosk Connect MCP server still maintained?
Apiosk Connect is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.