ScorpTech x402 Tools

Cipher Suite Info

cipher_suite_info

Read-onlyIdempotent

Look up TLS cipher suites by IANA name, OpenSSL name, GnuTLS name or hex code (0x13,0x01 / 0xC02F) — one or a whole list from a scanner, server config or ClientHello — and get key exchange, authentication, cipher, MAC / PRF hash, AEAD and forward-secrecy flags, minimum protocol, the IANA Recommended flag (Y / N / Discouraged) and a security rating (recommended, secure, weak, insecure) with reasons: no forward secrecy, CBC, SHA-1, RC4, 3DES, EXPORT, NULL or anonymous. Lists get a summary and their worst suite. Without a suite, browse the 356-entry IANA registry filtered by protocol or rating. Offline data: IANA registry, OpenSSL 3.6 and GnuTLS names. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/cipher-suite-info

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cipher_suite_info"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`suite`	No	One or more suites (names or hex), separated by spaces, colons, commas or newlines
`rating`	No	Browse filter	any
`protocol`	No	Browse filter	any

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare read-only, idempotent and open-world, and the description adds genuinely non-obvious traits: offline data sources (IANA, OpenSSL 3.6, GnuTLS), a per-call price of $0.001 USDC via x402 on Solana, and an equivalent HTTPS endpoint. The payment requirement is critical invocation context that nothing else conveys.

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?

Front-loaded with the lookup action and result fields before covering browse mode, pricing and the alternate endpoint. It is a dense ~130-word single sentence chain — every clause earns its place, but the density slightly hurts scannability.

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

Completeness5/5

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

No output schema exists, so the description carries the full return-value burden and does: key exchange, auth, cipher, MAC/PRF hash, AEAD and forward-secrecy flags, minimum protocol, IANA Recommended flag, and a security rating with named reasons, plus list summaries reporting the worst suite.

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

Parameters4/5

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

Schema coverage is 75% and the schema defines the rating/protocol enums, but the description adds concrete hex syntax examples ('0x13,0x01 / 0xC02F'), the accepted delimiters, and the registry size (356 entries) that contextualizes the browse filters. Only `limit` goes unmentioned, which is minor.

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 ('Look up TLS cipher suites') and enumerates accepted identifier forms (IANA, OpenSSL, GnuTLS, hex) plus its two modes: lookup by suite or browse the registry. An agent knows exactly what it gets back without opening the schema.

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

Usage Guidelines4/5

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

Explicitly covers both invocation modes: pass one or a list 'from a scanner, server config or ClientHello', or omit suite to browse the registry filtered by protocol or rating. It doesn't name any alternative tool, but no close sibling exists for this task, so the guidance is effectively complete.

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

All ScorpTech x402 Tools 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?