Skip to main content
Glama

Antigravity x402 & MCP Gateway

audit_domain_security_posture

[0.005000 USDC via x402] Performs a 100% passive, non-intrusive security posture audit of any public domain across TLS 1.2/1.3 & X.509 hygiene (25 pts), OWASP HTTP headers (40 pts), DoH SPF/DMARC/CAA (30 pts), and RFC 9116 /.well-known/security.txt (5 pts), returning a 0-100 score, A+..F grade, and fixes.

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": {
      "domain": "<domain>"
    },
    "name": "audit_domain_security_posture"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesPublic domain or hostname to audit passively (e.g., 'cloudflare.com').
x402_payment_signatureNoOptional base64 x402 PAYMENT-SIGNATURE header token (0.005000 USDC on Base eip155:8453 or Polygon eip155:137). Omit to receive the live x402 quote.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses the passive/non-intrusive nature (i.e., no active exploitation, read-only), the exact audit dimensions and their scoring weights, the response shape, and the 0.005000 USDC x402 cost. It stops short of stating rate limits, latency/timeout behavior, or whether the score is comparable across runs.

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?

A single dense sentence that front-loads the price then the purpose, with the scoring breakdown kept compact via parenthetical weights. It borders on over-packed, but every clause (passive, dimension weights, return values) earns its place.

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?

No output schema exists, yet the description compensates by naming the three return values (score, grade, fixes), and the pricing is stated up front so the agent isn't surprised by a payment challenge. Completeness is only slightly undercut by the absence of any note on run duration, idempotency, or failure modes for unresolvable domains.

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 100%, and the schema already documents both 'domain' and the optional 'x402_payment_signature' including chains (Base eip155:8453, Polygon eip155:137) and the omit-to-get-quote behavior. The description adds only the price figure, so the baseline of 3 applies rather than a higher mark.

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 ('passive, non-intrusive security posture audit of any public domain') and enumerates exactly what is checked with point weights (TLS/X.509 25 pts, OWASP headers 40 pts, DoH SPF/DMARC/CAA 30 pts, RFC 9116 5 pts) plus the return shape (0-100 score, A+..F grade, fixes). An agent can immediately distinguish this from sibling tools such as recon_rdap_domain (registration data) or scan_agent_payload_security.

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 '100% passive, non-intrusive' qualifier implicitly tells the agent this is safe to run against any public domain without authorization concerns, which is real guidance. However, there is no explicit when-to-use vs. when-not, no named alternative (e.g., RDAP for registry data), and the paid-call flow is only gestured at via the price tag rather than explained as 'call once to get a quote, then resubmit with the signature'.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.