Skavio USDC Payment Verification & Proof MCP

Web monitor

web_monitor

Idempotent

Measure a public HTTPS page's content hash, optionally comparing the previous SHA256 supplied by the caller. Use for detecting changes; choose web_fetch to retrieve the document or web_extract for just visible text. 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"
-            ]
-          }
-        ]
-      }
-    }
-  }
-]

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 / max_results

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

addedInput schema / properties / arguments / properties / previous_sha256 / description
```
Added value: +"Optional previous content SHA256 to compare for changes."
```

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"
+            ]
+          }
+        ]
+      }
+    }
+  }
+]

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 / max_results

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

removedInput schema / properties / arguments / properties / previous_sha256 / description
```
Removed value: -"Optional previous content SHA256 to compare for changes."
```

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: +{
+  "previous_sha256": {
+    "description": "Optional previous content SHA256 to compare for changes.",
+    "pattern": "^[0-9a-f]{64}$",
+    "type": "string"
+  },
+  "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.6/5.0

Behavior5/5

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

Goes well past the annotations: distinguishes admission from delivery, names the polling and retrieval siblings to use, warns to reuse the same idempotency_key rather than starting a new job, and explains how x402 (workload quote) differs from prepaid (shared credits). It also tells the caller to verify the returned SHA256, which the annotations cannot 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?

Purpose and sibling routing are front-loaded, then auth/payment, then the async workflow — a sensible order with little filler. It is dense to the point of run-on in the authentication sentence, which packs three separate admission requirements into one clause.

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 complex, authenticated, asynchronous job-creating tool with no output schema, the description covers authentication, payment modes, idempotent retry semantics, the poll-then-retrieve lifecycle, and result verification. Nothing an agent needs in order to call it correctly is missing.

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

Parameters3/5

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

Schema description coverage is 100%, so url, previous_sha256, payment_mode and idempotency_key are already documented in structured fields. The description restates their intent (comparison against a prior SHA256, same key on retry) without adding format, bounds, or edge-case detail beyond the schema, so baseline 3 applies.

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 (measure a public HTTPS page's content hash) plus an optional comparison against a caller-supplied SHA256, so the operation is unambiguous. It then explicitly contrasts itself with two named siblings, web_fetch and web_extract, so an agent can pick it without opening a 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 the positive trigger (detecting changes) and the alternatives with their selection conditions (web_fetch to retrieve the document, web_extract for visible text). It also states preconditions — valid Bearer key, enabled backend operation, accepted payment mode — and the no-anonymous-execution constraint.

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 monitor

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources