intel

mev_intel

Requires a ChainHelix API key as bearer token, or 2 cents per call paid over Binance b402 in USDT, USDC, USD1 or U on BNB Smart Chain, or over x402 in USDC on the Base network. MEV event rates per chain and type vs the trailing weekly pace. window in hours, default 24, max 168. Types overlap and must not be summed: a backrun transaction also emits an arbitrage row. NFT coverage is ERC-721 only, so nft_mev excludes all ERC-1155 activity. Chains covered: ethereum, bnb, avalanche, polygon.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`chain`	No
`window`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`meta`	No
`receipt`	No
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 1, 2026
- addedOutput schema / properties / results / items / properties / windowEnd
```
Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / results / items / properties / windowStart
```
Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
```
Changed4 schema fields changedSep 22, 2026
- changedOutput schema / properties / results / items / properties / count / type
```
Previous value: -"number"New value: +[
+  "number",
+  "null"
+]
```
- changedOutput schema / properties / results / items / properties / type / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- addedOutput schema / properties / results / items / properties / unavailable
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- changedOutput schema / properties / results / items / properties / weeklyPaceSameWindow / type
```
Previous value: -"number"New value: +[
+  "number",
+  "null"
+]
```

Changed1 schema field changedSep 21, 2026

changedInput schema / x-lexicon / bundleSha256

Previous value: -"a1c2e10fd3177d6b4d59ca78693e8fb36880165cf0f735f680dd86a510411178"New value: +"e5b4290024a229f2bdf97f8fc6a0079c3fe13b77267f41fdcffeb8b26aa1c41e"

Changed1 schema field changedSep 19, 2026

changedInput schema / x-lexicon / bundleSha256

Previous value: -"1eeb782ee15fe69fc80776948e0556fa6b795e210e6305935b2c97b73d955cda"New value: +"a1c2e10fd3177d6b4d59ca78693e8fb36880165cf0f735f680dd86a510411178"

Changed1 schema field changedSep 19, 2026

changedInput schema / x-lexicon / bundleSha256

Previous value: -"c014292cad7497ce9fd68c33345ac32cb42b672c8e77d6c749c26e162cc207e4"New value: +"1eeb782ee15fe69fc80776948e0556fa6b795e210e6305935b2c97b73d955cda"

Changed2 schema fields changedSep 19, 2026

addedInput schema / x-lexicon

Added value: +{
+  "bundleSha256": "c014292cad7497ce9fd68c33345ac32cb42b672c8e77d6c749c26e162cc207e4",
+  "name": "ChainHelix Agentic Lexicon",
+  "resolve": "lexicon_resolve",
+  "spec": "lexicon_spec",
+  "version": "0.1.0"
+}

addedInput schema / x-vocab

Added value: +{
+  "chain": "onchain.chain",
+  "window": "market.window"
+}

Changed1 schema field changedSep 6, 2026

changedInput schema / properties / chain / enum

Previous value: -[
-  "bitcoin",
-  "ethereum",
-  "bnb",
-  "solana",
-  "avalanche",
-  "xrp",
-  "tron",
-  "polygon",
-  "sui"
-]New value: +[
+  "ethereum",
+  "bnb",
+  "avalanche",
+  "polygon"
+]

Changed6 schema fields changedSep 5, 2026

addedOutput schema / properties / meta

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "contentHash": {
+      "type": "string"
+    },
+    "generated": {
+      "type": "number"
+    },
+    "priceUsd": {
+      "type": "number"
+    },
+    "validUntil": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

addedOutput schema / properties / receipt

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "bytes": {
+      "type": "number"
+    },
+    "covers": {
+      "type": "string"
+    },
+    "issuedAt": {
+      "type": "number"
+    },
+    "lookup": {
+      "type": "string"
+    },
+    "network": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "nonce": {
+      "type": "string"
+    },
+    "seq": {
+      "type": "number"
+    },
+    "settleTx": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "sha256": {
+      "type": "string"
+    },
+    "tool": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

addedOutput schema / properties / results / items / properties / calibration
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
addedOutput schema / properties / results / items / properties / latestBucket
```
Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
```

addedOutput schema / properties / results / items / properties / rule

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "changedInsideWindow": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "rule": {
+      "type": "string"
+    },
+    "since": {
+      "type": "string"
+    }
+  },
+  "type": [
+    "object",
+    "null"
+  ]
+}

addedOutput schema / properties / results / items / properties / source
```
Added value: +{
+  "type": "string"
+}
```

Changed1 schema field changedAug 5, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "results": {
+      "items": {
+        "properties": {
+          "chain": {
+            "type": "string"
+          },
+          "count": {
+            "type": "number"
+          },
+          "type": {
+            "type": "string"
+          },
+          "weeklyPaceSameWindow": {
+            "type": "number"
+          },
+          "windowHours": {
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "results"
+  ],
+  "type": "object"
+}

First observedAug 4, 2026

TDQS

B3.2/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the auth model (ChainHelix API key bearer token), the per-call cost and two payment rails (b402 on BSC, x402 on Base), the type-overlap caveat (backrun also emits an arbitrage row, must not be summed), and the ERC-721-only NFT coverage. These are exactly the non-obvious traits an agent needs before invoking.

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

Conciseness2/5

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

The critical purpose sentence is buried after a dense billing/payment preamble, so the agent must read past authentication plumbing to learn what the tool does. The caveat sentences are dense and earn their place, but front-loading is poor.

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

Completeness3/5

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

An output schema exists, so return-format explanation is unnecessary, and the description covers auth, cost, window bounds, type overlap, NFT scope, and chain coverage. What is missing is routing guidance against the numerous sibling MEV tools, leaving an agent unable to disambiguate similar-sounding endpoints.

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 0%, so the description must compensate. It adds real meaning for 'window' (hours, default 24, max 168), but for 'chain' it merely restates the enum values already present in the schema. Partial compensation yields a baseline 3.

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: 'MEV event rates per chain and type vs the trailing weekly pace', which is genuinely informative about what is returned. However, this core purpose is buried behind the payment/auth preamble, and it never distinguishes itself from neighbors like mev_pressure, mev_bots, or victim_flow.

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 defines window semantics (default 24, max 168) and enumerates supported chains, but gives no guidance on when to call this instead of the many sibling MEV tools (mev_pressure, mev_bots, victim_flow). No exclusions or routing conditions are offered.

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

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

Resources

Need Help?