SiteCheck Web Intel

Reports whether Shodan's pre-collected passive scan data

security_ntp_monlist_audit

Read-only

Reports whether Shodan's pre-collected passive scan data shows NTP (port 123) seen open on an IPv4 address. Passive and possibly old; the monlist amplification check itself is not run, so this cannot say whether monlist is enabled. Related tools on this server, for a different need: security_ssh_banner_audit when you need From Shodan's pre-collected passive scan data: whether TCP; security_bimi_record_audit when you need to read a domain's BIMI record: whether it is published. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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": {
      "ip": "<ip>"
    },
    "name": "security_ntp_monlist_audit"
  }
}

Input Schema

Name	Required	Description	Default
`ip`	Yes	IPv4 address such as 129.6.15.28 (required)

Output Schema

Name	Required	Description	Default
`ip`	No
`known`	No
`source`	No
`checkedAt`	No
`monlistTested`	No
`ntpPortSeenOpen`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Adds substantial context beyond readOnlyHint/openWorldHint: passive, possibly stale data; explicit limitation that monlist status is not checked; cost per successful call and no charge for failures. No contradiction with annotations.

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

Conciseness3/5

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

The core purpose and limitation are front-loaded and easy to scan. However, the related-tools sentence is malformed and includes an unrelated BIMI audit, which weakens structure and wastes space.

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?

Complete for a one-parameter passive lookup: it explains the data source, its staleness, the monlist limitation, and pricing, while the output schema carries return details. Nothing critical for correct invocation is missing.

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 coverage is 100% and the single ip parameter is already documented with an IPv4 example. The description reinforces that the target is an IPv4 address and that NTP/123 is the probe, but adds no format or validation detail beyond the schema.

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: reports whether Shodan's pre-collected passive data shows NTP/port 123 open for an IPv4 address. It also names the monlist limitation and distinguishes adjacent SSH/BIMI audits, so an agent can select it 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?

Explains the key usage caveat: the data is passive and possibly old, and the monlist check itself is not run, so it cannot determine whether monlist is enabled. It points to related tools for different needs, though those references are grammatically garbled.

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

All SiteCheck Web Intel 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?