Synthex Forge — x402 Paid Agent Services

Verify Mcp Uptime

verify_mcp_uptime

Read-onlyIdempotent

Independent uptime confirmation tied to a settled receipt. use it rather than verify_c2pa_provenance for mcp uptime, not c2pa provenance; an object with 37 fields including algorithm, canonicalSha256. $0.25 USDC.

Input Schema

Name	Required	Description
`checks`	No	Which checks to run. Omit for the default set.
`service_url`	No	The service url this operation operates on. See the schema for its type and whether it is required.
`last_confirmed_settlement_tx`	No	The last confirmed settlement tx this operation operates on. See the schema for its type and whether it is required.

Output Schema

Name	Required	Description
`ok`	Yes	Whether the operation succeeded.
`up`	No	The `up` field of the response.
`kind`	No	The `kind` field of the response.
`name`	No	The `name` field of the response.
`note`	No	A note on how the answer was produced.
`checks`	No	The individual checks that were run.
`detail`	Yes	Human-readable explanation of the verdict.
`sha256`	No	The `sha256` field of the response.
`framing`	No	The `framing` field of the response.
`metrics`	No	The `metrics` field of the response.
`verdict`	Yes	The decision this tool returned.
`coverage`	No	How much of the underlying corpus the answer is based on.
`probedAt`	No	The `probedAt` field of the response.
`signedBy`	No	The `signedBy` field of the response.
`algorithm`	No	The `algorithm` field of the response.
`checks_ok`	No	The `checks_ok` field of the response.
`latencyMs`	No	The `latencyMs` field of the response.
`ed25519Sig`	No	The `ed25519Sig` field of the response.
`serviceUrl`	No	The `serviceUrl` field of the response.
`url_present`	No	The `url_present` field of the response.
`evidenceCore`	No	The `evidenceCore` field of the response.
`observations`	No	The `observations` field of the response.
`publicKeyHex`	No	The `publicKeyHex` field of the response.
`verdictLevel`	No	The `verdictLevel` field of the response.
`checks_failed`	No	The `checks_failed` field of the response.
`checks_usable`	No	The `checks_usable` field of the response.
`checks_skipped`	No	The `checks_skipped` field of the response.
`evidenceDigest`	No	The `evidenceDigest` field of the response.
`canonicalSha256`	No	The `canonicalSha256` field of the response.
`checks_supplied`	No	The `checks_supplied` field of the response.
`latency_samples`	No	The `latency_samples` field of the response.
`reproducibility`	No	The `reproducibility` field of the response.
`verificationHint`	No	The `verificationHint` field of the response.
`settlementLatencyP95`	No	The `settlementLatencyP95` field of the response.
`lastConfirmedSettlementTx`	No	The `lastConfirmedSettlementTx` field of the response.
`settlement_latency_p95_ms`	No	The `settlement_latency_p95_ms` field of the response.
`settlement_anchor_supplied`	No	The `settlement_anchor_supplied` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed39 schema fields changedOct 31, 2026

addedOutput schema / properties / algorithm

Added value: +{
+  "description": "The `algorithm` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / canonicalSha256

Added value: +{
+  "description": "The `canonicalSha256` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / checks

Added value: +{
+  "description": "The individual checks that were run.",
+  "items": {
+    "description": "One record.",
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / checks_failed

Added value: +{
+  "description": "The `checks_failed` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / checks_ok

Added value: +{
+  "description": "The `checks_ok` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / checks_skipped

Added value: +{
+  "description": "The `checks_skipped` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / checks_supplied

Added value: +{
+  "description": "The `checks_supplied` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / checks_usable

Added value: +{
+  "description": "The `checks_usable` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / coverage

Added value: +{
+  "description": "How much of the underlying corpus the answer is based on.",
+  "type": "object"
+}

addedOutput schema / properties / detail

Added value: +{
+  "description": "Human-readable explanation of the verdict.",
+  "type": "string"
+}

addedOutput schema / properties / ed25519Sig

Added value: +{
+  "description": "The `ed25519Sig` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / evidenceCore

Added value: +{
+  "description": "The `evidenceCore` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / evidenceDigest

Added value: +{
+  "description": "The `evidenceDigest` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / framing

Added value: +{
+  "description": "The `framing` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / kind

Added value: +{
+  "description": "The `kind` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / lastConfirmedSettlementTx

Added value: +{
+  "description": "The `lastConfirmedSettlementTx` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / latencyMs

Added value: +{
+  "description": "The `latencyMs` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / latency_samples

Added value: +{
+  "description": "The `latency_samples` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / metrics

Added value: +{
+  "description": "The `metrics` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / name

Added value: +{
+  "description": "The `name` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / note

Added value: +{
+  "description": "A note on how the answer was produced.",
+  "type": "string"
+}

addedOutput schema / properties / observations

Added value: +{
+  "description": "The `observations` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / ok

Added value: +{
+  "description": "Whether the operation succeeded.",
+  "type": "boolean"
+}

addedOutput schema / properties / probedAt

Added value: +{
+  "description": "The `probedAt` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / publicKeyHex

Added value: +{
+  "description": "The `publicKeyHex` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / reproducibility

Added value: +{
+  "description": "The `reproducibility` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / serviceUrl

Added value: +{
+  "description": "The `serviceUrl` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / settlementLatencyP95

Added value: +{
+  "description": "The `settlementLatencyP95` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / settlement_anchor_supplied

Added value: +{
+  "description": "The `settlement_anchor_supplied` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / settlement_latency_p95_ms

Added value: +{
+  "description": "The `settlement_latency_p95_ms` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / sha256

Added value: +{
+  "description": "The `sha256` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / signedBy

Added value: +{
+  "description": "The `signedBy` field of the response.",
+  "type": "object"
+}

removedOutput schema / properties / status

Removed value: -{
-  "type": "string"
-}

addedOutput schema / properties / up

Added value: +{
+  "description": "The `up` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / url_present

Added value: +{
+  "description": "The `url_present` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / verdict

Added value: +{
+  "description": "The decision this tool returned.",
+  "type": "string"
+}

addedOutput schema / properties / verdictLevel

Added value: +{
+  "description": "The `verdictLevel` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / verificationHint

Added value: +{
+  "description": "The `verificationHint` field of the response.",
+  "type": "object"
+}

addedOutput schema / required

Added value: +[
+  "detail",
+  "ok",
+  "verdict"
+]

AddedOct 31, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description still adds two genuinely new facts: a prerequisite ('tied to a settled receipt') and a price ('$0.25 USDC'), the latter being critical since this is a paid call. It does not explain what happens on payment failure or how the 37-field object is shaped beyond two field names.

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

Conciseness3/5

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

Short and front-loaded with the purpose and the sibling exclusion, which is good. But it reads as stitched fragments — the semicolon-separated 'an object with 37 fields…' clause and the bare '$0.25 USDC.' sentence sit awkwardly and partly duplicate what the output schema already provides.

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

Completeness4/5

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

For a paid, read-only, 3-param verification call with an output schema, most of what an agent needs is present: what it verifies, the sibling to avoid, the settlement prerequisite, and the cost. Remaining gaps (check catalogue, behavior when the receipt is unsettled) are minor.

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 `checks`, `service_url` and `last_confirmed_settlement_tx` are already documented in the schema. The description adds nothing about any of them — notably it never says what 'checks' options exist or that omitting them yields the default set. Baseline 3 applies.

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

Purpose4/5

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

The first clause names a specific verb and resource ('Independent uptime confirmation') bound to a precondition ('tied to a settled receipt'), and it explicitly contrasts with the sibling `verify_c2pa_provenance`. The trailing fragment about 'an object with 37 fields including algorithm, canonicalSha256' is return-value noise that dilutes rather than clarifies the purpose.

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

Usage Guidelines4/5

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

It directly routes the agent away from the confusable sibling: 'use it rather than `verify_c2pa_provenance` for mcp uptime, not c2pa provenance.' What's missing is any statement of when NOT to use this tool at all, or what to do if no settled receipt exists yet.

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

All Synthex Forge — x402 Paid Agent Services 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.