CrossingKey MCP

Purchase SHA-256 Text Hash

hash.encode

Idempotent

PAID $0.01 USDC on Base via x402. Computes a SHA-256 digest and UTF-8 byte count for supplied text. Calling this MCP tool returns a payment challenge and does not autonomously spend funds.

Input Schema

Name	Required	Description	Default
`text`	Yes	Input text, maximum 65536 UTF-8 bytes.

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.

Changed10 schema fields changedOct 15, 2026

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

AddedOct 10, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations only signal readOnly=false, openWorld=true, idempotent=true, destructive=false. The description adds substantial behavioral context beyond that: the exact cost ($0.01 USDC), the chain (Base), the protocol (x402), and critically that calling returns a payment challenge and does not autonomously spend funds. It stops short of describing the post-payment flow, but the safety profile is well covered.

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 compact sentences with zero filler, front-loaded with the payment terms and followed by purpose then the no-autonomous-spend guarantee. Efficient, though leading with the payment model before the function slightly delays the core verb+resource.

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 tool with an output schema (so return values need no explanation) and full schema coverage, the description supplies the essential payment and safety context. It is close to complete, with the only gap being how a challenge is fulfilled, which the x402 sibling tools can cover.

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?

With one parameter at 100% schema description coverage, the schema already carries the constraint (maxLength 65536 UTF-8 bytes). The description alludes to 'supplied text' and the UTF-8 byte count but adds no format, encoding, or edge-case detail beyond what the schema states.

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: 'Computes a SHA-256 digest and UTF-8 byte count for supplied text.' No sibling in the list performs hashing, so the operation is unambiguous and immediately distinguishable from the x402/audit siblings that merely inspect payment paths.

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

Usage Guidelines3/5

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

The description discloses that the call is paid and returns a payment challenge rather than spending funds, which is important context for deciding to invoke it, but it gives no explicit when-to-use or when-not guidance and names no alternative for obtaining a hash or handling x402 payment.

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.