MCP tool reference

These 13 tools match the MCP runtime's canonical catalog. Parameter names must match the schema exactly.

ip

Look up IP geolocation and ASN data. Required: address.

dns

Query DNS records. Required: domain. Optional: type (A / AAAA / CNAME / MX / TXT / NS; default A).

http

Check HTTP/HTTPS availability and response time. Required: url. Optional: method (GET / HEAD / POST; default GET).

ping

Measure round-trip latency and packet loss. Required: target. Optional: count (default 3).

ssl

Inspect TLS certificates and expiry. Required: host.

whois

Query WHOIS data for a domain or IP. Required: query.

traceroute

Trace the network path to a target. Required: target. Optional: max_hops (default 30).

diagnose

Combine Ping, DNS, HTTP, and TLS diagnostics. Required: target.

icp

Look up China ICP filing data for a domain. Required: query.

list_nodes

List available probe nodes. No required parameters. Optional: country, tier (datacenter / residential / mobile / vps_small).

check_monitor

Read recent checks for a monitor in your account. Required: monitor_id. Optional: limit (default 10, maximum 100).

create_monitor

Create a monitor in your account (write operation). Required: name, type (http / tcp / ping / dns), target. Optional: interval_s, node_count (default 1), config.

generate_verdict

Create a Verdict report job (write operation). Required: template (sla / incident / compliance / legal), target, time_window_start, time_window_end (timestamps use RFC3339).

The MCP channel can only generate reports that Core prices as free. It never selects a payment channel, consumes report credits, or starts a paid order.

Probe tools do not accept a node list. The server selects a node and returns that node's result. Write operations run as the account that owns the MCP token.