InferenceView MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EVM_PRIVATE_KEY | Yes | Your funded Base wallet private key. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| verify_transactionA | Before paying an unknown x402/MCP resource, return risk, recommendation, and evidence. The live x402 challenge controls the price. |
| factcheckA | Verify a factual claim before acting on it. Returns a verdict, confidence, primary sources, freshness, contradictions, and evidence. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools address entirely different verification domains: one assesses transaction risk for x402/MCP resources, while the other evaluates the veracity of factual claims. There is no overlap in inputs, operations, or outputs, making misselection impossible.
Both tool names use lowercase and avoid special characters, but verify_transaction follows a clear verb_noun pattern while factcheck is a single compound word. This minor stylistic mismatch is easy to read and does not hinder predictability.
With only two tools, the server feels somewhat thin. However, each tool covers a distinct, substantive verification use case, and the narrow focus justifies the small count, making it acceptable if not ideal.
The server's implied domain is pre-action verification, and the two tools cover the primary needs: verifying transactions and verifying facts. No critical gaps are apparent within this scope, though a broader verification suite might include other resource types.