Skip to main content
Glama
Diogenes Web3, DeFi & HTTP 402 Security MCP

Diogenes Web3, DeFi & HTTP 402 Security MCP

http402_challenge_verifier

Verifies inbound HTTP 402 payment challenges (L402 BOLT11, x402 Solana, MPP Base) to detect overcharges and recipient spoofing.

Instructions

Verifies inbound HTTP 402 (L402 BOLT11, x402 Solana, MPP Base) payment challenges against overcharge and recipient spoofing.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "www_authenticate_header": "<www_authenticate_header>"
    },
    "name": "http402_challenge_verifier"
  }
}

Input Schema

NameRequiredDescriptionDefault
advertised_max_satsNo
www_authenticate_headerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the specific checks (overcharge and recipient spoofing), but it omits whether the tool is read-only, what a failed verification looks like, what the return value is, and any permission or rate-limit constraints.

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

Conciseness5/5

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

A single sentence front-loaded with the verb and the exact standards covered. It contains no filler and is appropriately sized for the stated purpose.

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

Completeness2/5

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

For a verification tool with no output schema, the description should explain the return shape or failure behavior. It also leaves both parameters undocumented and gives no when-to-use guidance, making it materially incomplete against the task complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for both parameters. The description's mention of 'overcharge' loosely relates to advertised_max_sats and 'HTTP 402 challenges' loosely relates to www_authenticate_header, but it gives no format, units, or interpretation; with zero schema documentation, it fails to compensate.

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?

States a specific verb ('Verifies') and resource ('inbound HTTP 402 payment challenges') plus named standards (L402 BOLT11, x402 Solana, MPP Base). It is clearly distinct from siblings like contract_audit or solana_risk, but it does not explicitly differentiate itself from any alternative tool.

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?

No when-to-use guidance, no alternatives, and no prerequisites are given. It does not say under what circumstances to call this tool versus handling a 402 challenge manually, so the agent must infer usage entirely.

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