Skavio USDC Payment Verification & Proof MCP

Web extract

web_extract

Idempotent

Extract human-visible text from one public HTTPS page under robots and size limits. Use for readable page text, not raw document fetching (web_fetch) or SHA256 change detection (web_monitor). This is a separately authenticated company Agent Tools relay; requires a valid Bearer API key, an enabled backend operation and an accepted payment mode. x402 returns a workload-specific quote and prepaid consumes shared company credits. Retry with the SAME idempotency_key and inputs to recover, not a new job. Admission is not delivery: poll skavio_agent_job_status, retrieve through skavio_agent_job_result, and verify SHA256. No anonymous execution.

Input Schema

Name	Required	Description	Default
`arguments`	Yes	Tool-specific structured input object. Supply the required named fields described by its JSON Schema; source bytes must respect encoded size limits. Never include wallet private keys, passwords or API tokens.
`payment_mode`	No	x402 returns a workload-specific quote; prepaid spends your existing shared company credits. No anonymous execution.	x402
`idempotency_key`	Yes	Stable job key; retry exactly the same inputs and payment mode with this key to recover safely.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 27, 2026

addedInput schema / properties / arguments / description

Added value: +"Tool-specific structured input object. Supply the required named fields described by its JSON Schema; source bytes must respect encoded size limits. Never include wallet private keys, passwords or API tokens."

Changed9 schema fields changedOct 20, 2026

removedInput schema / properties / arguments / allOf

Removed value: -[
-  {
-    "if": {
-      "required": [
-        "url"
-      ]
-    },
-    "then": {
-      "not": {
-        "anyOf": [
-          {
-            "required": [
-              "max_results"
-            ]
-          },
-          {
-            "required": [
-              "fetch_top"
-            ]
-          }
-        ]
-      }
-    }
-  }
-]

removedInput schema / properties / arguments / not

Removed value: -{
-  "required": [
-    "url",
-    "query"
-  ]
-}

removedInput schema / properties / arguments / oneOf

Removed value: -[
-  {
-    "required": [
-      "url"
-    ]
-  },
-  {
-    "required": [
-      "query"
-    ]
-  }
-]

removedInput schema / properties / arguments / properties / diagnose

Removed value: -{
-  "default": false,
-  "description": "Optional DeepSeek interpretation, priced separately; a provider failure never loses the primary result.",
-  "type": "boolean"
-}

removedInput schema / properties / arguments / properties / fetch_top

Removed value: -{
-  "default": 3,
-  "description": "In query mode, how many top real source URLs to fetch and extract.",
-  "maximum": 5,
-  "minimum": 1,
-  "type": "integer"
-}

removedInput schema / properties / arguments / properties / max_results

Removed value: -{
-  "default": 5,
-  "description": "Search results to return in query mode.",
-  "maximum": 10,
-  "minimum": 1,
-  "type": "integer"
-}

removedInput schema / properties / arguments / properties / query

Removed value: -{
-  "description": "Google query answered by Serper; returns real source URLs, never synthesised links. Mutually exclusive with url.",
-  "maxLength": 256,
-  "minLength": 1,
-  "type": "string"
-}

changedInput schema / properties / arguments / properties / url / description

Previous value: -"Public HTTPS page to process. Mutually exclusive with query."New value: +"Public HTTPS page URL. Robots, public address and bounded response checks apply."

addedInput schema / properties / arguments / required
```
Added value: +[
+  "url"
+]
```

Changed9 schema fields changedOct 18, 2026

addedInput schema / properties / arguments / allOf

Added value: +[
+  {
+    "if": {
+      "required": [
+        "url"
+      ]
+    },
+    "then": {
+      "not": {
+        "anyOf": [
+          {
+            "required": [
+              "max_results"
+            ]
+          },
+          {
+            "required": [
+              "fetch_top"
+            ]
+          }
+        ]
+      }
+    }
+  }
+]

addedInput schema / properties / arguments / not

Added value: +{
+  "required": [
+    "url",
+    "query"
+  ]
+}

addedInput schema / properties / arguments / oneOf

Added value: +[
+  {
+    "required": [
+      "url"
+    ]
+  },
+  {
+    "required": [
+      "query"
+    ]
+  }
+]

addedInput schema / properties / arguments / properties / diagnose

Added value: +{
+  "default": false,
+  "description": "Optional DeepSeek interpretation, priced separately; a provider failure never loses the primary result.",
+  "type": "boolean"
+}

addedInput schema / properties / arguments / properties / fetch_top

Added value: +{
+  "default": 3,
+  "description": "In query mode, how many top real source URLs to fetch and extract.",
+  "maximum": 5,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / arguments / properties / max_results

Added value: +{
+  "default": 5,
+  "description": "Search results to return in query mode.",
+  "maximum": 10,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / arguments / properties / query

Added value: +{
+  "description": "Google query answered by Serper; returns real source URLs, never synthesised links. Mutually exclusive with url.",
+  "maxLength": 256,
+  "minLength": 1,
+  "type": "string"
+}

changedInput schema / properties / arguments / properties / url / description

Previous value: -"Public HTTPS page URL. Robots, public address and bounded response checks apply."New value: +"Public HTTPS page to process. Mutually exclusive with query."

removedInput schema / properties / arguments / required
```
Removed value: -[
-  "url"
-]
```

Changed9 schema fields changedOct 17, 2026

changedInput schema / properties / arguments / additionalProperties
```
Previous value: -trueNew value: +false
```

addedInput schema / properties / arguments / properties

Added value: +{
+  "url": {
+    "description": "Public HTTPS page URL. Robots, public address and bounded response checks apply.",
+    "maxLength": 2048,
+    "type": "string"
+  }
+}

addedInput schema / properties / arguments / required
```
Added value: +[
+  "url"
+]
```
removedInput schema / properties / arguments / title
```
Removed value: -"Arguments"
```

addedInput schema / properties / idempotency_key / description

Added value: +"Stable job key; retry exactly the same inputs and payment mode with this key to recover safely."

addedInput schema / properties / idempotency_key / maxLength
```
Added value: +128
```
addedInput schema / properties / idempotency_key / minLength
```
Added value: +8
```
addedInput schema / properties / idempotency_key / pattern
```
Added value: +"^[A-Za-z0-9_.:-]{8,128}$"
```

addedInput schema / properties / payment_mode / description

Added value: +"x402 returns a workload-specific quote; prepaid spends your existing shared company credits. No anonymous execution."

AddedOct 14, 2026

TDQS

A4.8/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well beyond the annotations: discloses the relay authentication model, that x402 issues a workload-specific quote while prepaid consumes shared company credits, and the retry contract ('retry with the SAME idempotency_key and inputs to recover, not a new job'). It also discloses the critical asynchronous semantic 'Admission is not delivery', telling the agent to poll status, retrieve via result, and verify SHA256 — none of which the readOnlyHint/openWorldHint/idempotentHint annotations convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose then differentiation, followed by auth/payment/retry/job-flow blocks; every sentence carries operational weight with no filler. It is dense and near the upper bound of useful length for a single-page extractor, with a couple of clauses that could be tightened.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutating, authenticated, asynchronous, paid tool with no output schema, the description covers everything an agent needs: access prerequisites, cost model, idempotent retry behavior, the admission-vs-completion distinction, the exact follow-up tools (skavio_agent_job_status, skavio_agent_job_result), and output verification via SHA256.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description adds meaning by pairing idempotency_key with retry recovery and contrasting x402 quoting against prepaid credit spend. It does not explain the nested `arguments` object or the URL constraints beyond what the schema already states, so it is above baseline but not exhaustive.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Extract human-visible text from one public HTTPS page') plus the operating envelope (robots and size limits). It then explicitly names the two sibling it is NOT — web_fetch for raw document fetching and web_monitor for SHA256 change detection — so an agent can route correctly without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit positive condition ('readable page text') and explicit exclusions mapped to named alternatives (web_fetch, web_monitor). It also states prerequisites ('requires a valid Bearer API key, an enabled backend operation and an accepted payment mode') and 'No anonymous execution', which prevents a whole class of mis-invocation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Skavio USDC Payment Verification & Proof MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Web extract

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources