CrossingKey MCP

Purchase Artifact Integrity Manifest

artifact.integrity_manifest

Idempotent

PAID $0.10 USDC on Base via x402. Creates deterministic SHA-256 entries and a root manifest hash for supplied text artifacts. Calling this MCP tool does not spend funds; it returns the exact PAYMENT-REQUIRED challenge and canonical paid execution endpoint.

Input Schema

Name	Required	Description	Default
`artifacts`	Yes	Artifacts to include in the integrity manifest.

Output Schema

Name	Required	Description	Default
`asset`	No
`error`	No
`input`	No
`price`	No
`pay_to`	No
`status`	No
`accepts`	No
`network`	No
`resource`	No
`capability`	No
`extensions`	No
`purchaseId`	No
`instruction`	No
`x402Version`	No
`entitlementId`	No
`execution_url`	No
`execution_mode`	No
`payment_required`	No
`payment_required_header`	No
`settlement_expectations`	No
`confirmation_expectations`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedOct 15, 2026

removedInput schema / properties / idempotency_key

Removed value: -{
-  "maxLength": 160,
-  "minLength": 8,
-  "type": "string"
-}

removedInput schema / properties / payment_payload

Removed value: -{
-  "additionalProperties": {},
-  "type": "object"
-}

changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +true
```

addedOutput schema / properties / accepts

Added value: +{
+  "items": {
+    "additionalProperties": true,
+    "properties": {},
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / entitlementId
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / error
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / extensions

Added value: +{
+  "additionalProperties": true,
+  "properties": {},
+  "type": "object"
+}

addedOutput schema / properties / purchaseId
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / resource

Added value: +{
+  "additionalProperties": true,
+  "properties": {},
+  "type": "object"
+}

addedOutput schema / properties / status
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / x402Version

Added value: +{
+  "const": 2,
+  "type": "number"
+}

removedOutput schema / required

Removed value: -[
-  "payment_required",
-  "execution_mode",
-  "capability",
-  "input",
-  "price",
-  "asset",
-  "network",
-  "pay_to",
-  "execution_url",
-  "payment_required_header",
-  "settlement_expectations",
-  "confirmation_expectations",
-  "instruction"
-]

Changed2 schema fields changedOct 5, 2026

addedInput schema / properties / idempotency_key

Added value: +{
+  "maxLength": 160,
+  "minLength": 8,
+  "type": "string"
+}

addedInput schema / properties / payment_payload

Added value: +{
+  "additionalProperties": {},
+  "type": "object"
+}

Changed3 schema fields changedOct 2, 2026

removedInput schema / properties / idempotency_key

Removed value: -{
-  "maxLength": 160,
-  "minLength": 8,
-  "type": "string"
-}

removedInput schema / properties / payment_payload

Removed value: -{
-  "additionalProperties": {},
-  "type": "object"
-}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "asset": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "capability": {
+      "type": "string"
+    },
+    "confirmation_expectations": {
+      "type": "string"
+    },
+    "execution_mode": {
+      "type": "string"
+    },
+    "execution_url": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "input": {
+      "additionalProperties": true,
+      "properties": {},
+      "type": "object"
+    },
+    "instruction": {
+      "type": "string"
+    },
+    "network": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "pay_to": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "payment_required": {
+      "const": true,
+      "type": "boolean"
+    },
+    "payment_required_header": {
+      "type": "string"
+    },
+    "price": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "settlement_expectations": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "payment_required",
+    "execution_mode",
+    "capability",
+    "input",
+    "price",
+    "asset",
+    "network",
+    "pay_to",
+    "execution_url",
+    "payment_required_header",
+    "settlement_expectations",
+    "confirmation_expectations",
+    "instruction"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedSep 30, 2026

addedInput schema / properties / idempotency_key

Added value: +{
+  "maxLength": 160,
+  "minLength": 8,
+  "type": "string"
+}

addedInput schema / properties / payment_payload

Added value: +{
+  "additionalProperties": {},
+  "type": "object"
+}

AddedSep 22, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Beyond the annotations, it discloses the cost ($0.10 USDC on Base via x402), that invoking it does not spend funds, and that it returns a PAYMENT-REQUIRED challenge plus the canonical paid endpoint. That is genuinely useful behavioral context for a paid tool. It does not conflict with readOnlyHint=false.

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?

Three sentences, front-loaded with the cost and non-spending clarification, each carrying useful information. Slightly dense but no wasted filler.

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?

With an output schema present, return values needn't be described, and the description covers the key payment model, cost, and the fact that calling is free. It omits when to prefer this over alternatives, but is otherwise complete for a single-param paid tool.

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 the schema fully documents the artifacts array and its name/content fields. The description only restates 'supplied text artifacts,' adding no syntax or format detail beyond the schema, so the baseline of 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 description states a specific verb+resource: 'Creates deterministic SHA-256 entries and a root manifest hash for supplied text artifacts.' This distinguishes it from the generic hash.encode sibling by emphasizing manifest/root-hash aggregation, though it never names alternatives explicitly.

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

Usage Guidelines2/5

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

It explains the payment mechanics ('PAID $0.10 USDC... Calling this MCP tool does not spend funds') but gives no when-to-use guidance, no exclusions, and no routing to siblings like hash.encode or execution.preflight. The agent must infer when this paid manifest is the right choice.

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

All CrossingKey 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.