Skip to main content
Glama
Sign In

Cian Endpoint Audit

by io.github.cian-spider
OverviewDiscussionsAdmin

HTTP endpoint audit

endpoint_audit
Read-only

Audit one public HTTP endpoint: final status and redirect chain, TLS, security headers, and the DNS records behind it. Returns the same JSON as GET https://cian-x402.netlify.app/v1/audit. Paid per call: 0.05 USDC on Base (eip155:8453) via x402. An unpaid tools/call returns HTTP 402 with the payment terms; pay and retry the identical call.

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": {
      "url": "<url>"
    },
    "name": "endpoint_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesAbsolute http(s) URL to audit, e.g. https://example.com

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only cover safety and openness; the description adds the economically decisive facts: cost of 0.05 USDC on Base (eip155:8453) via x402, that an unpaid call returns HTTP 402 with payment terms, and that the caller must retry the identical call after paying. That is auth/payment and error-path disclosure an agent cannot get from the structured fields.

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?

Three tight sentences: capability first, return shape second, payment mechanics third. Every sentence carries information an agent needs, with no filler or repetition of the title.

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?

The tool has an output schema, so return values need not be explained, and the description instead equates the output to a known public GET endpoint. Combined with the payment and retry flow, nothing required to invoke it successfully is missing.

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?

With a single required parameter and 100% schema description coverage, the schema already defines the URL format. The description only marginally adds meaning by qualifying the target as "public", which hints that internal addresses may be rejected.

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?

The description opens with a specific verb and resource ("Audit one public HTTP endpoint") and enumerates exactly what is inspected: final status and redirect chain, TLS, security headers, and DNS records. An agent knows precisely what the tool produces 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?

Scope is bounded clearly by "one" and "public", which implicitly rules out bulk auditing and internal/non-routable hosts. There are no sibling tools to route against, but the description stops short of explicitly stating those exclusions or prerequisites for the target URL.

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

All Cian Endpoint Audit toolsInspect
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