A
licenseNot graded
qualityA
maintenanceFree SSL/TLS scanning and Let's Encrypt certificate issuance (private key stays local), plus certificate-expiry monitoring via one MCP server. Public scan and cert tools need no account.
MIT
Uptimeify
by io.uptimeify
Server Details
Free anonymous website, DNS, email and TLS checks, plus monitor read and opt-in write access.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
TDQS
A4.3/5.0
Scored across 20 tools
Disambiguation5/5
Descriptions are exceptionally explicit, with each tool naming its siblings and stating exactly what it does and does not cover (e.g. website_status vs response_time vs http_headers vs redirect_check; asn_lookup vs ip_geolocation vs reverse_dns). Overlapping candidates like whois/domain_expiry are distinguished by scope (full registration vs expiry with computed days). An agent can reliably pick the right tool.
Naming Consistency3/5
The set mixes a 'check_' prefix (check_dns, check_ssl) with a '_check' suffix (dkim_check, dmarc_check, spf_check, dnsbl_check, hsts_check) for the same verb, plus assorted forms like asn_lookup, reverse_dns, ping_test, response_time, website_status and a bare whois. Still readable, but the inconsistency in expressing the same action is real.
Tool Count4/5
20 tools sits at the heavy end, but the server spans genuinely distinct subdomains (DNS, TLS, email auth, blacklists, WHOIS, HTTP behavior, latency, ports), so each tool earns its place. Slightly over what a single agent comfortably juggles, but well-scoped rather than redundant.
Completeness4/5
Coverage is broad: DNS resolution and propagation, SSL, SPF/DKIM/DMARC, blacklists, WHOIS/expiry, headers, redirects, timing, ports, ping, reverse DNS, ASN and geolocation, plus HSTS. Minor gaps remain (no traceroute, no multi-vantage or historical uptime despite the 'Uptimeify' name, no UDP), but core diagnostic workflows have no dead ends.
Available Tools
20 toolsasn_lookupARead-onlyInspect
Resolve a public IP address, or a domain, to the autonomous system that announces it: AS number and name, the announced prefix, country code, registry and allocation date. Answers who operates the network an address sits on, which tells a hosting provider from a CDN from a corporate network. It does not identify the site owner, and private or reserved addresses have no announcing AS. ip_geolocation returns the same AS data plus country and PTR. Anonymous and rate-limited per IP.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Public IP address or domain name |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| cc | No | |
| ip | No | |
| ok | No | |
| asns | No | |
| found | No | |
| query | No | |
| prefix | No | |
| registry | No |
TDQS
A4.4/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations only declare readOnlyHint, so the description carries real weight here and delivers: 'Anonymous and rate-limited per IP' discloses the absence of auth plus a throttling constraint, and 'private or reserved addresses have no announcing AS' pre-empts a whole class of empty results. It also enumerates the returned fields, which goes beyond the safety profile.
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 verb and resource, then constraints, then the sibling comparison, then the operational caveat — a sensible ordering. Three sentences with almost no waste, though the 'which tells a hosting provider from a CDN' clause is interpretive framing rather than call-critical detail.
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?
An output schema exists, so return values need not be explained, and the description still covers the input contract, failure modes, rate limiting, and the adjacent tool. For a one-parameter, read-only lookup, nothing an agent needs in order to call it correctly 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% for the single 'query' parameter, so the schema already defines it as a public IP or domain name, making 3 the baseline. The description adds only the boundary condition that private/reserved inputs yield nothing; it does not add format, IPv6, or CIDR guidance 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?
Uses a specific verb ('Resolve') on a specific resource ('public IP address, or a domain') and names exactly what comes back: AS number and name, announced prefix, country code, registry, allocation date. It explicitly differentiates itself from the sibling ip_geolocation, so an agent can route without opening either 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?
It states the selecting condition against the alternative: 'ip_geolocation returns the same AS data plus country and PTR,' which tells the agent when the sibling is the better pick. It also frames the use case ('who operates the network... hosting provider from a CDN from a corporate network'). What's missing is an explicit rule such as 'prefer this when you only need AS data,' so usage is strongly implied rather than spelled out.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
check_dnsARead-onlyInspect
Resolve a domain's DNS records in one call (A, AAAA, CNAME, MX, TXT, NS, SOA and more), returning each record type with its values and a per-type error where a lookup failed. Answers come from the resolver Uptimeify uses, so this is one vantage point: to see whether the answer is already the same everywhere, use dns_propagation. It reads records only and never connects to the host. Anonymous and rate-limited per IP.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Domain name, e.g. deinkunde.com |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| ok | No | |
| found | No | |
| domain | No | |
| records | No | |
| warnings | No |
TDQS
A4.7/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations only declare readOnlyHint=true, but the description adds several traits beyond that: answers come from a single resolver vantage point, the tool reads records only and never connects to the host, and it is anonymous with per-IP rate limiting. These are exactly the operational constraints an agent needs before calling.
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 sentences, each load-bearing: what it returns, which vantage point it represents plus the alternative, and the safety/rate-limit profile. No repetition of the title or schema, and the core capability is front-loaded.
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?
Even though an output schema exists, the description still summarizes the return shape (each record type with values and per-type errors) and covers the single parameter, the alternative tool, and access constraints. Nothing an agent needs to invoke this correctly 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?
There is only one parameter and schema coverage is 100%, with the schema itself supplying an example domain. The description adds no syntax, validation, or format detail beyond what the schema already provides, so this sits at the documented baseline.
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 ('Resolve a domain's DNS records') and enumerates the record types covered, so the agent knows exactly what comes back. It also distinguishes itself from the overlapping sibling mx_lookup/dns_propagation family by naming dns_propagation as the multi-vantage alternative.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly routes the agent: use dns_propagation 'to see whether the answer is already the same everywhere,' implying this tool is the single-vantage-point default. Combined with the scoping note that this is one resolver's answer, the when-to-use vs when-to-use-the-alternative decision is fully covered.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
check_sslARead-onlyInspect
Fetch and evaluate a host's TLS/SSL certificate over a live handshake: subject and issuer, validity window, days until expiry, hostname match, chain trust, self-signed and expired flags, SANs, serial and SHA-256 fingerprint. Takes a hostname, not an IP address, plus an optional port (default 443). This is a single sample taken now: it does not watch the certificate over time, says nothing about the HTTP response behind it (website_status) and nothing about the transport policy the site advertises (hsts_check). Anonymous and rate-limited per IP; hosts that resolve to private or reserved address space are refused.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| host | Yes | Domain name (not an IP), e.g. deinkunde.com | |
| port | No | TLS port, default 443 |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| ip | No | |
| ok | No | |
| san | No | |
| host | No | |
| port | No | |
| found | No | |
| expired | No | |
| issuerO | No | |
| trusted | No | |
| validTo | No | |
| issuerCN | No | |
| subjectCN | No | |
| validFrom | No | |
| selfSigned | No | |
| notYetValid | No | |
| serialNumber | No | |
| hostnameMatch | No | |
| fingerprint256 | No | |
| daysUntilExpiry | No | |
| authorizationError | No |
TDQS
A4.6/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the readOnlyHint annotation, the description discloses rate limiting per IP, anonymity, refusal of private/reserved address space, and that the result is a single point-in-time sample with no historical tracking. These are operational behaviors an agent needs and none are inferable from the annotation or schema.
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 core purpose and scope limits, and every clause is informative. The long enumeration of returned fields is somewhat redundant given an output schema exists, which is the only reason it falls short of 5.
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?
Covers input form, defaults, scope boundaries versus siblings, sampling semantics, access constraints, and network restrictions — everything needed to call the tool correctly and interpret its limits, with the output schema covering return values.
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%, so both parameters are already documented, and the description largely repeats the schema's constraint that a hostname (not an IP) is required and that the port defaults to 443. No additional syntax, validation, or edge-case detail is added, so the baseline of 3 applies.
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 ('fetch and evaluate a host's TLS/SSL certificate over a live handshake') and enumerates what is evaluated: subject/issuer, validity window, expiry, hostname match, chain trust, self-signed/expired flags, SANs, serial, fingerprint. It explicitly distinguishes itself from the sibling tools website_status and hsts_check by naming what it does not cover.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives explicit routing conditions: it is a point-in-time sample, not continuous monitoring, and it says nothing about the HTTP response (website_status) or transport policy (hsts_check). It also states the input precondition (hostname, not IP) and the access constraint (anonymous, rate-limited per IP, private/reserved addresses refused).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
dkim_checkARead-onlyInspect
Fetch and validate the DKIM public key published at a given selector (._domainkey.) and report the parsed tags, key type, key size in bits, and warnings such as a revoked or malformed key. The selector is required and cannot be derived from the domain: read it from a message's DKIM-Signature header, or try the provider's usual value (google, selector1, default, k1). An unused selector returns found=false rather than an error. Anonymous and rate-limited per IP.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Domain name, e.g. deinkunde.com | |
| selector | Yes | DKIM selector, e.g. google or default |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| ok | No | |
| bits | No | |
| tags | No | |
| error | No | |
| found | No | |
| domain | No | |
| hasKey | No | |
| record | No | |
| keyType | No | |
| selector | No | |
| warnings | No |
TDQS
A4.7/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Goes well beyond readOnlyHint=true by disclosing anonymous, per-IP rate-limited access, the non-error found=false outcome for unused selectors, and the warning behaviours (revoked or malformed key). These are operational traits an agent cannot infer from annotations or schema.
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 dense sentences: what it does first, then the non-obvious selector requirement with fallbacks, then the error/rate-limit semantics. No filler and the critical selector guidance is front-loaded where it matters.
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?
An output schema exists, yet the description still sketches the returned fields and the found=false case; combined with the selector acquisition guidance and rate-limit disclosure, an agent has everything needed to invoke and interpret the call.
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 already 100%, so baseline is 3, but the description adds real meaning: that selector cannot be derived from domain, where to find it, and representative values to try. Domain semantics (e.g. deinkunde.com) are left to 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 pair (fetch and validate) plus the exact resource (the DKIM public key at <selector>._domainkey.<domain>) and enumerates what is reported: parsed tags, key type, key size, and warnings. This clearly separates it from sibling email-auth checks like spf_check and dmarc_check without needing the schemas.
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 how to obtain the required selector — read it from a DKIM-Signature header or try common provider values (google, selector1, default, k1) — and clarifies that an unused selector yields found=false rather than an error. It stops short of explicitly routing to sibling tools (spf_check/dmarc_check) or stating when this check is unnecessary.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
dmarc_checkARead-onlyInspect
Fetch a domain's DMARC record from _dmarc. and evaluate it: the raw record, every parsed tag, the policy and subdomain policy, the percentage the policy applies to, and warnings for records that parse but do not protect (p=none, missing rua, syntax receivers ignore). Reports the published policy, not whether real mail passes it. Pair it with spf_check and dkim_check, the mechanisms DMARC aligns against. Anonymous and rate-limited per IP.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Domain name, e.g. deinkunde.com |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| ok | No | |
| pct | No | |
| tags | No | |
| error | No | |
| found | No | |
| domain | No | |
| policy | No | |
| record | No | |
| warnings | No | |
| subPolicy | No |
TDQS
A4.4/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations only declare readOnlyHint=true, so the description carries most of the load. It adds genuinely useful behavioral context: anonymous access, per-IP rate limiting, the resolution path (_dmarc.<domain>), and that warnings are emitted for records that parse but do not protect. It stops short of describing failure modes such as what happens when no record exists or how rate limiting manifests.
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?
Two dense sentences with the core action front-loaded and no filler; the enumeration of returned fields is the most valuable content and arrives early. It is slightly run-on, packing the lookup, the return shape, the caveat, and the rate-limit note into one long sentence, which costs a little readability.
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?
For a single-param read tool with an output schema, the description supplies everything an agent needs: the lookup mechanism, what is returned, the p=none/missing-rua warning behavior, the alignment caveat, related tools, and the anonymous/rate-limited access model. Nothing material is left for the agent to infer before calling it.
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 100% schema description coverage the baseline is 3, but the description goes slightly beyond the schema by explaining that the domain feeds a DNS lookup against the reserved _dmarc.<domain> name, which clarifies what the parameter is actually resolved against. That is meaningful added context, though format rules (IDN, trailing dot, subdomain handling) are not addressed.
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 (fetch) and resource (a domain's DMARC record from _dmarc.<domain>) plus what is done with it (evaluate tags, policy, subdomain policy, percentage, warnings). It also names the sibling tools it complements, spf_check and dkim_check, so an agent can place it among the 19 siblings without opening a 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?
Gives clear context for use, including the boundary 'Reports the published policy, not whether real mail passes it', which tells the agent when this tool is the wrong choice for a deliverability question. It also recommends pairing with spf_check and dkim_check. It does not name an explicit alternative tool to use instead for the excluded case, so it falls short of a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
dnsbl_checkARead-onlyInspect
Query a public IP address against common DNS blacklists and return, per list, whether it is listed, the reason code the list gave and its delisting URL, plus totals and a clean flag. Takes an IP address, not a domain: resolve the sending host first with mx_lookup or check_dns. Slow blocklists are dropped instead of waited for, so partial=true means zonesQueried is below total and a clean verdict is provisional for the lists that never answered. A listing usually appears between checks, so one call proves only this moment. Anonymous and rate-limited per IP, and this is the strictest limit of the anonymous tools.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ip | Yes | Public IPv4 or IPv6 address |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| ip | No | |
| ok | No | |
| clean | No | |
| total | No | |
| partial | No | |
| results | No | |
| listedCount | No | |
| zonesQueried | No |
TDQS
A4.9/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, but the description goes far beyond that: it explains partial=true when slow blocklists are dropped, notes that a clean verdict is provisional for unanswered lists, warns that listings are transient, and states the rate-limiting and anonymity constraints. This is rich behavioral context that an agent would otherwise lack.
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?
The description is front-loaded with the tool's purpose and return shape, then proceeds to caveats in a logical order. Every sentence carries distinct, necessary information (input type, partial behavior, transience, rate limits) without redundant phrasing.
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?
Given the existence of an output schema, the description is not required to re-explain return values, yet it complements them by clarifying the meaning of partial results and the provisional nature of a clean verdict. It also covers input expectations, operational constraints, and the need to resolve the host first, making the definition complete for an agent to call it correctly.
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?
The schema fully documents the single 'ip' parameter as a public IPv4 or IPv6 address (100% coverage). The description adds valuable meaning by emphasizing that it takes an IP address, not a domain, and directing the agent to resolve the sending host first, which clarifies intended input beyond the schema text.
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 states a specific verb and resource: query a public IP against DNS blacklists and return per-list results plus totals and a clean flag. It distinguishes itself from siblings by explicitly noting it takes an IP, not a domain, and names mx_lookup and check_dns as alternative tools for resolving the host.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
It gives explicit when-to-use guidance: resolve the sending host first with mx_lookup or check_dns, then use this tool. It also discloses operational limits (anonymous, rate-limited per IP, strictest anonymous limit) and explains that a single call proves only the current moment, which directly affects when the result is meaningful.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
dns_propagationARead-onlyInspect
Query the same domain against several public resolvers and compare the answers, so a recent record change can be told apart from a stale cache. Returns each resolver with the values it gave, plus a consistent flag that stays false while the answers still differ. Use it after changing DNS; for a single reading of all record types, check_dns is the cheaper call. Anonymous and rate-limited per IP.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Domain name, e.g. deinkunde.com |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| ok | No | |
| type | No | |
| domain | No | |
| results | No | |
| consistent | No |
TDQS
A4.5/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds meaningful behavior beyond annotations: it is anonymous, rate-limited per IP, and returns per-resolver values with a consistency flag that stays false while answers differ. The rate-limit detail is useful, though not quantified.
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?
The description is four compact sentences, front-loaded with the purpose and followed by return behavior, usage guidance, and operational constraints. Every sentence earns its place.
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?
An output schema exists, so return values need not be fully explained. The description still covers purpose, alternative routing, output interpretation, and rate-limit/auth context, leaving nothing essential missing for correct invocation.
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 single domain parameter is fully documented in the schema. The description does not add format, syntax, or validation detail beyond the schema, so the baseline of 3 is appropriate.
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 states a specific verb and resource: query the same domain against several public resolvers and compare answers. It also explicitly distinguishes the tool from check_dns by naming the cheaper alternative for a single reading of all record types.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
It gives an explicit usage trigger ('Use it after changing DNS') and names the sibling alternative with the condition that selects it ('for a single reading of all record types, check_dns is the cheaper call'). No inference is required.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
domain_expiryARead-onlyInspect
Report a domain's registration expiry from WHOIS together with daysUntilExpiry, plus registrar, creation and update dates and the EPP status codes that reveal a domain already in redemption or pending delete. This is the registration, not the certificate: an expiring TLS certificate is check_ssl. tldSupported=false means the TLD has no WHOIS server Uptimeify can query, which is not the same as an unregistered domain. Anonymous and rate-limited per IP.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Domain name, e.g. deinkunde.com |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| ok | No | |
| tld | No | |
| error | No | |
| found | No | |
| domain | No | |
| statuses | No | |
| createdAt | No | |
| expiresAt | No | |
| registrar | No | |
| updatedAt | No | |
| tldSupported | No | |
| daysUntilExpiry | No |
TDQS
A4.1/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the readOnlyHint annotation, it discloses that access is anonymous and rate-limited per IP (affecting call pacing), and explains the tldSupported=false semantics ('not the same as an unregistered domain'), a real edge case that prevents misinterpretation of results.
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-loads the core purpose, then layers the sibling disambiguation, the tldSupported caveat, and the rate-limit note. Dense and largely waste-free, though the enumeration of return fields drifts toward duplicating the output schema.
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?
An output schema exists so return values need not be re-explained, and the readOnlyHint annotation covers the safety profile. Rate limits, anonymous access, and the tldSupported edge case fill the remaining gaps an agent would need before calling it.
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% for the single required 'domain' param, so the schema already documents it fully. The description adds no syntax, format, or constraint detail beyond what the schema provides, which is the expected baseline when the schema does the heavy lifting.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('Report a domain's registration expiry from WHOIS') and enumerates the returned fields (daysUntilExpiry, registrar, creation/update dates, EPP status codes). It explicitly distinguishes itself from check_ssl, but does not differentiate from the sibling 'whois' tool, which covers overlapping ground.
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?
Clearly routes the certificate-vs-registration case to check_ssl ('an expiring TLS certificate is check_ssl'), giving the agent a real alternative. However it offers no guidance on when to prefer this over the sibling 'whois' tool or any exclusion beyond the cert case.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
hsts_checkARead-onlyInspect
Check a domain's HTTP Strict Transport Security configuration: whether the header is present, its raw value, max-age in seconds, the includeSubDomains and preload flags, whether plain HTTP redirects to HTTPS, whether the configuration would qualify for the browser preload list, and warnings for values that make the header ineffective. Reports the policy the site advertises, not the certificate behind it (check_ssl) and not the full redirect chain (redirect_check). Anonymous and rate-limited per IP; private and reserved address space is refused.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Domain name, e.g. deinkunde.com |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| ok | No | |
| raw | No | |
| domain | No | |
| maxAge | No | |
| preload | No | |
| present | No | |
| warnings | No | |
| preloadReady | No | |
| httpsRedirect | No | |
| includeSubDomains | No |
TDQS
A4.6/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the readOnlyHint annotation, the description discloses authentication ('Anonymous'), rate limiting ('rate-limited per IP'), refusal behavior ('private and reserved address space is refused'), and that warnings are produced for ineffective header values. These are meaningful operational traits an agent needs before invoking the tool, and they do not contradict the readOnly annotation.
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?
The description is front-loaded with purpose and packed with useful distinctions, but the first sentence is a long, sprawling enumeration of return fields. Given that an output schema exists, that list is denser than strictly necessary, though the remaining sentences about alternatives and operational constraints clearly earn their place.
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?
For a single-parameter read tool with an output schema, the description covers purpose, alternatives, safety/operational behavior, and refusal conditions. Since return-value details are already handled by the output schema, nothing essential is missing for an agent to select and invoke it correctly.
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?
There is only one parameter and schema description coverage is 100%, so the schema already fully documents the domain argument. The description adds no syntax, format, or validation details beyond what the schema provides, making the baseline score of 3 appropriate.
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 gives a specific verb and resource ('Check a domain's HTTP Strict Transport Security configuration') and then enumerates exactly which HSTS properties are evaluated. It explicitly distinguishes itself from the sibling tools check_ssl and redirect_check, so an agent can tell what it does and does not cover without opening any schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
It names the alternatives directly and states the boundary: 'Reports the policy the site advertises, not the certificate behind it (check_ssl) and not the full redirect chain (redirect_check).' This is an explicit when-to-use/when-not-to-use statement that routes the agent to the correct sibling for certificate and redirect questions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
http_headersARead-onlyInspect
Fetch a URL and return its HTTP response headers verbatim as a name/value map, with the status line and every redirect hop taken to get there. Use it to inspect caching, security and server headers as they are actually sent; the response body is never returned, so this says nothing about page content. For a plain up/down verdict use website_status, for the redirect chain alone redirect_check. Anonymous and rate-limited per IP; hosts resolving to private or reserved address space are refused.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Full URL, e.g. https://deinkunde.com |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| ok | No | |
| url | No | |
| status | No | |
| headers | No | |
| redirects | No | |
| statusText | No |
TDQS
A4.7/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the readOnlyHint annotation, it discloses that access is anonymous and rate-limited per IP, that private/reserved address ranges are refused, and that the body is never returned. These are non-obvious operational constraints an agent needs before calling.
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?
Front-loads the core behavior, then exclusions, then routing to alternatives, then operational caveats, in three tight sentences with no filler.
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 return shape is described (name/value map plus status line and redirect hops) and an output schema exists, so nothing further about returns is needed. Safety, routing, and access constraints are all covered for a simple one-parameter read tool.
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 url parameter already has a format example, so the description adds no parameter-level syntax or constraints. Baseline 3 applies when the schema carries the parameter burden.
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 (fetch a URL, return its HTTP response headers) plus exact scope: status line and every redirect hop, body never returned. It explicitly distinguishes itself from siblings website_status and redirect_check, so an agent can route without opening a schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives an explicit use case ('inspect caching, security and server headers as they are actually sent') and names the two alternatives with their selecting conditions: website_status for a plain up/down verdict, redirect_check for the redirect chain alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
ip_geolocationARead-onlyInspect
Locate a public IP address, or a domain resolved to one, at network level: country code, allocating registry, announced prefix, PTR hostname and the autonomous systems the address belongs to. It is registry-based, so it names the network operator's country, which for hosted or CDN-fronted addresses is not where the visitor or the business sits -- never read it as a street address. Private and reserved addresses have no answer. For the AS and its owner alone use asn_lookup, for the PTR alone reverse_dns. Anonymous and rate-limited per IP.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Public IP address or domain name |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| cc | No | |
| ip | No | |
| ok | No | |
| ptr | No | |
| asns | No | |
| found | No | |
| query | No | |
| prefix | No | |
| registry | No | |
| resolvedFromDomain | No |
TDQS
A4.9/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations cover only readOnlyHint, so the description carries the rest and does so well: it discloses the registry-based semantics, warns that the country reflects the network operator not the visitor/business, states the private/reserved no-answer behavior, and notes anonymous, per-IP rate limiting.
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?
A single dense paragraph with zero filler; scope and return contents are front-loaded, then caveats, then alternative tools. Every sentence carries actionable information.
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?
An output schema exists so return-value documentation is not required, yet the description still previews the fields. Combined with the coverage of limitations, rate limits, and sibling routing, nothing an agent needs to invoke it correctly 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?
Schema coverage is 100% for the single 'query' parameter, so the baseline is 3. The description adds real meaning beyond the schema by clarifying that a domain input is resolved to an IP first ('or a domain resolved to one'), which tells the agent how the domain form is actually handled.
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?
Names a specific verb ('Locate') and resource ('public IP address, or a domain resolved to one') and enumerates exactly what comes back: country code, registry, announced prefix, PTR hostname, and the autonomous systems. It also distinguishes itself from siblings by scope, so an agent can route correctly without opening a schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly routes alternatives: 'For the AS and its owner alone use asn_lookup, for the PTR alone reverse_dns.' It also states the failure boundary ('Private and reserved addresses have no answer'), so an agent knows both when to pick this tool and when it will return nothing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
mx_lookupARead-onlyInspect
Look up a domain's MX records and resolve each mail exchanger to its IPv4 and IPv6 addresses, ordered by priority and flagged when a host resolves into private address space. Tells you where mail for the domain is delivered; it does not connect to those servers, does not test SMTP, and says nothing about whether the domain is authorised to send (spf_check, dkim_check, dmarc_check). Anonymous and rate-limited per IP.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Domain name, e.g. deinkunde.com |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| ok | No | |
| found | No | |
| domain | No | |
| servers | No |
TDQS
A4.7/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations only declare readOnlyHint=true; the description adds substantive traits beyond that: anonymous access, per-IP rate limiting, no connection to the discovered hosts, and result characteristics (priority ordering, private-address-space flagging). These are exactly the operational constraints an agent needs before calling.
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?
Two densely packed sentences with zero filler; the positive capability is front-loaded and the exclusions follow immediately. Every clause carries routing or behavioural information.
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?
With an output schema present, return values need not be described; the description instead covers the things the schema cannot — access model, rate limits, and non-capabilities. Nothing needed to call this tool correctly 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?
The single 'domain' parameter is fully documented in the schema (100% coverage) and the description only implies it via 'a domain's MX records'. No additional syntax, format or validation meaning is added, so the baseline 3 for high schema coverage applies.
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?
Specific verb (look up) plus resource (a domain's MX records), with explicit scope: resolves each exchanger to IPv4/IPv6, ordered by priority, flags private address space. It also demarcates itself from siblings by naming spf_check, dkim_check and dmarc_check as the tools that answer sending-authorisation questions.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives both when-to-use (finding where mail for a domain is delivered) and when-not: it does not connect to servers, does not test SMTP, and says nothing about sending authorisation. The alternatives for that latter need are named explicitly, so an agent can route correctly without inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
ping_testARead-onlyInspect
Measure reachability and round-trip time by opening repeated TCP connections to a host, reporting every attempt plus the count sent and received, packet loss percentage and min/avg/max milliseconds. This is a TCP handshake against a port (default 443), not an ICMP echo: a host that drops ICMP still answers here, and a host that answers ICMP with the port closed does not. For a one-shot verdict on a website rather than a latency series, use website_status. Anonymous and rate-limited per IP; private and reserved address space is refused.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| host | Yes | Domain name or host | |
| port | No | Port, default 443 |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| ip | No | |
| ok | No | |
| host | No | |
| port | No | |
| sent | No | |
| avgMs | No | |
| maxMs | No | |
| minMs | No | |
| lossPct | No | |
| attempts | No | |
| received | No |
TDQS
A4.7/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations only declare readOnlyHint=true; the description adds genuinely new behavioral context: repeated connections rather than a single probe, the full metric set returned (count sent/received, loss %, min/avg/max ms), anonymous rate limiting per IP, and refusal of private/reserved ranges. The ICMP-vs-TCP contrast also predicts surprising results (ICMP-dropping hosts still reply; ICMP-replying hosts with a closed port do not).
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 tightly packed sentences with no filler: the first defines the operation and its outputs, the second handles the ICMP misconception, the third handles routing and constraints. Front-loaded and every clause carries information.
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?
For a two-parameter, read-only probe with an output schema, the description covers everything an agent needs: what is measured, what comes back, the default port, access limits, address-space restrictions, and the sibling alternative. Nothing material is delegated to guesswork.
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%, so both parameters (host, port) are already documented and the 443 default is stated in the schema itself. The description restates the port default and the handshake context but adds no syntax, format, or validation detail beyond what the schema provides, so the baseline of 3 applies.
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?
Specific verb and resource: 'Measure reachability and round-trip time by opening repeated TCP connections to a host,' with the exact reported metrics enumerated. It goes further and disambiguates from the most confusable sibling and from ICMP ping semantics, so an agent can select it without opening any schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly routes the agent: 'For a one-shot verdict on a website rather than a latency series, use website_status.' It also states the default port (443), the anonymous/rate-limited access model, and the exclusion of private and reserved address space, giving both when-to-use and when-not-to-use.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
port_checkARead-onlyInspect
Open a TCP connection to one or more ports on a host and report each as open, closed or filtered with the time the attempt took. Pass a single port or a list of up to 10; a single-port call also gets its answer flat, exactly as before the list form existed. partial=true means not every requested port was answered inside the time budget. TCP only -- there is no UDP check -- and filtered means no answer arrived, not that the port is certainly closed. Anonymous and rate-limited per IP; the host is resolved first and private or reserved addresses are refused, including a host whose DNS answer points into them.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| host | Yes | Domain name or host | |
| port | Yes | TCP port, or a list of up to 10 ports, e.g. 443 or [80, 443, 25] |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| ip | No | |
| ok | No | |
| host | No | |
| port | No | |
| state | No | |
| timeMs | No | |
| partial | No | |
| results | No | |
| portsRequested | No |
TDQS
A4.2/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With annotations providing only readOnlyHint, the description carries the rest and delivers real operational context: anonymous, rate-limited per IP, host resolved first, private/reserved addresses refused including DNS answers pointing into them, and a time budget that can yield partial results. It stops short of quantifying the rate limit or time budget, so it is strong but not exhaustive.
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?
Purpose and scope are front-loaded, and every sentence conveys a distinct constraint (result taxonomy, list limit, partial flag, TCP-only, rate limits, SSRF refusal). Slightly dense and the backward-compatibility clause ('exactly as before the list form existed') costs words for limited agent value.
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?
An output schema exists, so return structure need not be explained, yet the description still covers the ambiguous output cases (filtered semantics, partial=true) and the security/resolution preconditions. Nothing an agent needs to invoke this correctly against a 2-parameter schema 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?
Schema description coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema by explaining the single-item vs list response shape ('a single-port call also gets its answer flat') and tying partial=true to the input list, which clarifies what the port argument actually produces.
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 concrete verb and resource ('Open a TCP connection to one or more ports on a host') plus the exact result taxonomy (open/closed/filtered). This clearly distinguishes it from siblings like ping_test or check_dns, which probe different layers.
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 description bounds scope ('TCP only -- there is no UDP check') and interprets 'filtered' as no answer rather than certainly closed, which helps an agent read results. However, it never names an alternative sibling or states when to prefer this over ping_test/website_status, so selection guidance is only implied.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
redirect_checkARead-onlyInspect
Follow a URL's HTTP redirect chain hop by hop and return every step with its status code, source and target, the final URL and status, the hop count, and warnings for chains that loop, drop from HTTPS to HTTP, or run longer than they should. Answers where a URL ends up and how many round trips that costs; it returns neither the body nor the headers of the destination (http_headers). Anonymous and rate-limited per IP; private and reserved address space is refused.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Full URL, e.g. https://deinkunde.com |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| ok | No | |
| hops | No | |
| start | No | |
| finalUrl | No | |
| warnings | No | |
| totalHops | No | |
| finalStatus | No | |
| finalStatusText | No |
TDQS
A4.4/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations only carry readOnlyHint, but the description adds substantial behavioral context: anonymous access, per-IP rate limiting, refusal of private/reserved address space, and warnings emitted for loops, HTTPS-to-HTTP downgrades, and over-long chains. It also discloses what is not returned (destination body/headers), which no annotation 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 core action and return contents, then the exclusions and constraints. The opening sentence is dense with a long list of returned fields, but every clause conveys distinct, useful information rather than repeating structured data.
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?
For a single-parameter read tool with an output schema, the description covers the remaining gaps an agent needs: access model (anonymous, rate-limited), safety constraints (private/reserved space refused), diagnostic warnings, and explicit boundaries versus http_headers. Nothing material 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% with a single 'url' parameter already documented with an example, so the schema carries the load. The description adds no format or syntax detail beyond what the schema provides, making the baseline 3 appropriate.
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 ('Follow a URL's HTTP redirect chain hop by hop') and enumerates exactly what it returns, so an agent knows this is a redirect-tracing tool distinct from one-shot checks. It explicitly contrasts itself with the http_headers sibling, stating it returns neither body nor headers of the destination.
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?
It clearly frames the question the tool answers ('where a URL ends up and how many round trips that costs') and routes header/body needs to http_headers, which is the natural alternative. However it does not explicitly state when redirect_check should be preferred over, say, website_status, leaving some sibling selection to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
response_timeARead-onlyInspect
Measure how fast a URL answers by taking several samples and returning each one plus min, average and max milliseconds, the HTTP status and an up flag. partial=true means fewer samples came back than were requested, so the average rests on a smaller base. This measures the response, not the rendered page: no browser runs, so nothing here reflects JavaScript, assets or Core Web Vitals. One call is a snapshot, not a trend. Anonymous and rate-limited per IP; private and reserved address space is refused.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Full URL, e.g. https://deinkunde.com |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| ok | No | |
| up | No | |
| avg | No | |
| max | No | |
| min | No | |
| url | No | |
| status | No | |
| partial | No | |
| samples | No | |
| samplesRequested | No |
TDQS
A4.4/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations only supply readOnlyHint=true, so the description carries real weight here and delivers: anonymous access, per-IP rate limiting, refusal of private/reserved address space, the meaning of partial=true and its effect on the average, and the no-browser execution model. These are operational traits an agent cannot infer from the annotation or schema.
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?
Five dense sentences, each carrying distinct information: purpose and outputs first, then partial semantics, then the rendering caveat, then snapshot limitation and access constraints. Slightly list-like toward the end, but every clause earns its place with no filler.
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?
Even though an output schema exists and would cover return values, the description still frames what comes back and, more importantly, covers the execution model, access model and interpretation limits that structured fields cannot express. Nothing an agent needs to call this correctly and interpret the result 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?
There is a single parameter (url) with 100% schema description coverage, so the schema already documents the input. The description adds no syntax, format or constraint detail about the URL beyond the schema's example; its parameter-adjacent note about partial=true refers to an output field, not an input. Baseline 3 is appropriate when the schema does the work.
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 ('Measure how fast a URL answers') plus the exact output shape (samples, min/avg/max ms, HTTP status, up flag). It actively distinguishes itself from render-based siblings by declaring 'no browser runs, so nothing here reflects JavaScript, assets or Core Web Vitals,' which separates it from page-rendering tools and clarifies it is not ping_test or a full website_status check.
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?
Gives clear usage context ('one call is a snapshot, not a trend') and the boundary condition for when this is the right instrument ('measures the response, not the rendered page'). It stops short of naming a specific sibling to use instead for rendered-page measurement or trend tracking, so routing is implied rather than explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
reverse_dnsARead-onlyInspect
Resolve a public IP address to the PTR hostnames published for it, returning every name the pointer record carries, or the resolver's error where there is none. A PTR is set by whoever controls the address block, so it names the host rather than necessarily the site running on it, and a missing PTR is common and not a fault. It is not the inverse of check_dns: a forward record and a PTR need not agree, and this call does not verify that they do. Anonymous and rate-limited per IP.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ip | Yes | Public IPv4 or IPv6 address |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| ip | No | |
| ok | No | |
| error | No | |
| hostnames | No |
TDQS
A4.5/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the readOnlyHint annotation, it discloses the auth profile (anonymous), a rate limit scoped per IP, the failure mode (returns the resolver's error where there is none), and an important interpretive caveat (a PTR names the host, not necessarily the site). This is unusually rich behavioral context for a read-only call.
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 sentences with no filler: the operation leads, the interpretive caveat and the sibling disambiguation follow, and operational constraints close. Every sentence carries distinct information.
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?
Output schema covers return values, so the description correctly omits them and instead covers the two things the schema cannot: the rate limit and the fact that a null/error result is expected rather than a failure. Nothing needed to call this correctly 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 description coverage is 100% and the single 'ip' parameter is already documented as a public IPv4 or IPv6 address. The description restates 'public IP address' without adding format, validation, or edge-case detail, so the baseline 3 applies.
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 (Resolve) and resource (public IP address to PTR hostnames), and explicitly distinguishes itself from the sibling check_dns by noting it is not its inverse. An agent can pick it apart from check_dns and dns_propagation without opening any 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?
Gives clear context for when results are meaningful ('a missing PTR is common and not a fault') and rules out the check_dns inverse assumption. It does not name an explicit alternative to use instead when reverse DNS is inappropriate, so it stops short of full when/when-not routing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
spf_checkARead-onlyInspect
Fetch a domain's SPF record and evaluate the policy: the raw record, every parsed term with its qualifier, the number of DNS lookups it costs against the RFC 7208 limit of ten, the final all qualifier, and warnings for the failure modes that silently break sending. Covers the sending policy only -- alignment and reporting are DMARC (dmarc_check), the signing key is DKIM (dkim_check). A domain without a record returns found=false, which is an answer, not an error. Anonymous and rate-limited per IP.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Domain name, e.g. deinkunde.com |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| ok | No | |
| all | No | |
| error | No | |
| found | No | |
| terms | No | |
| domain | No | |
| record | No | |
| lookups | No | |
| warnings | No |
TDQS
A4.7/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations only supply readOnlyHint, so the description carries the rest and does so well: it discloses the rate limit ('Anonymous and rate-limited per IP'), the RFC 7208 lookup budget of ten, and critically that a missing record yields found=false rather than an error -- behavior an agent could otherwise mishandle.
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?
Front-loads what is fetched and evaluated, then scope, then the error semantics and operational constraints. Dense but every clause carries information with no filler.
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?
An output schema exists, so return values need not be explained, yet the description still signals the notable return shape (found=false on absence). With scope, alternatives, rate limits, and error semantics all covered, an agent has everything needed to call it correctly.
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?
Only one parameter, domain, and schema coverage is 100% with a clear example ('deinkunde.com'). The description adds no meaning beyond the schema, so the baseline 3 for a fully-documented single parameter is appropriate.
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 (Fetch... and evaluate) plus a precise resource (a domain's SPF record/policy) and enumerates exactly what the policy evaluation yields. It explicitly carves out its scope against two named siblings (dmarc_check, dkim_check), so it is distinguishable without opening any schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly bounds its own scope ('Covers the sending policy only') and names the alternatives for adjacent concerns -- alignment/reporting to dmarc_check, the signing key to dkim_check. The condition that separates it from siblings is stated rather than inferred.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
website_statusARead-onlyInspect
Is a website up right now? Start here for any is-the-site-down question: up/down verdict, HTTP status and status text, response time in milliseconds, the server header and the number of redirects followed, in one call. This is a single sample from one location taken now -- it is not uptime, and a site that fails here may be reachable from elsewhere. For the timing breakdown use response_time, for the headers themselves http_headers, for the redirect chain redirect_check. Anonymous and rate-limited per IP; private and reserved address space is refused.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Full URL, e.g. https://deinkunde.com |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| ok | No | |
| up | No | |
| url | No | |
| server | No | |
| status | No | |
| redirects | No | |
| statusText | No | |
| responseTimeMs | No |
TDQS
A4.7/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations only declare readOnlyHint=true, so the description carries the real disclosure burden and delivers: anonymous access, per-IP rate limiting, refusal of private/reserved address space, single-location/single-sample semantics, and the explicit caveat that a failure is not proof of downtime.
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?
Front-loaded with the core question and verdict, then progressively adds scope, limitations, sibling routing, and access constraints. Dense but every sentence earns its place with no filler.
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?
An output schema exists so return values need no explanation. The description still supplies the sampling caveat, sibling alternatives, and access/rate-limit constraints — everything an agent needs to call this correctly and interpret results.
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?
Single required 'url' parameter is fully documented in the schema (100% coverage) with an example. The description adds no syntax beyond the schema, so the baseline of 3 applies — the schema does the heavy lifting here.
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?
Opens with a specific verb+resource framed as a question ('Is a website up right now?') and enumerates exactly what the call returns (up/down verdict, HTTP status/text, response time in ms, server header, redirect count). It clearly distinguishes itself from siblings by naming what it consolidates in one call.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly states when to use it ('Start here for any is-the-site-down question') and routes to alternatives by condition: response_time for timing breakdown, http_headers for headers, redirect_check for the chain. It also warns that a failure here is a single-sample result, not uptime.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
whoisARead-onlyInspect
Retrieve WHOIS registration data for a domain: registrar, creation, update and expiry dates, EPP status codes, nameservers and the contact roles the registry still publishes. Registries redact personal data since GDPR, so contacts are usually roles without names. Not every TLD has a WHOIS server Uptimeify can query -- tldSupported=false means it could not ask, which is different from a domain that is not registered (found=false). For the expiry date alone, domain_expiry returns it with the remaining days already computed. Anonymous and rate-limited per IP.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Domain name, e.g. deinkunde.com |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| ok | No | |
| tld | No | |
| error | No | |
| found | No | |
| domain | No | |
| contacts | No | |
| statuses | No | |
| createdAt | No | |
| expiresAt | No | |
| registrar | No | |
| updatedAt | No | |
| nameservers | No | |
| tldSupported | No |
TDQS
A4.7/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations only cover readOnlyHint=true, so the description carries the behavioral burden and does so well: it discloses GDPR-driven contact redaction, rate-limiting per IP, anonymous access, and the semantic distinction between 'could not query' and 'not registered'. This is substantial context beyond what the annotations provide.
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?
Front-loaded with the core purpose, then layered with the caveats that matter (GDPR redaction, tldSupported vs found, the domain_expiry alternative, rate limits). Despite its length, every sentence carries distinct, decision-relevant information with no filler.
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?
With an output schema present, the description need not explain return values, and it still covers the error/edge semantics (tldSupported, found), contact redaction, and rate limiting. An agent has everything needed to call and interpret this tool correctly.
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?
There is a single required parameter (domain) with 100% schema description coverage including an example, so the schema does the work. The description adds no syntax, format, or TLD-level constraints on the parameter itself, making the baseline 3 appropriate.
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 ('Retrieve WHOIS registration data for a domain') and enumerates the concrete fields returned (registrar, creation/update/expiry dates, EPP status codes, nameservers, contact roles). It also differentiates itself from the sibling domain_expiry by scoping that one to expiry date alone.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly routes the agent: 'For the expiry date alone, domain_expiry returns it with the remaining days already computed.' It further clarifies the disambiguation between tldSupported=false (no WHOIS server available) and found=false (domain not registered), which is precisely the usage decision an agent must make.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
20 tool updates
- Changed
asn_lookup15 fields changed- changed
Output schema / properties / asns / anyOfPrevious value: -[ - { - "items": { - "additionalProperties": {}, - "properties": { - "allocated": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - }, - "asn": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - }, - "cc": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - }, - "name": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - }, - "registry": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - } - }, - "type": "object" - }, - "type": "array" - }, - { - "type": "null" - } -]New value: +[ + { + "items": { + "additionalProperties": {}, + "properties": { + "allocated": { + "type": [ + "string", + "null" + ] + }, + "asn": { + "type": [ + "string", + "null" + ] + }, + "cc": { + "type": [ + "string", + "null" + ] + }, + "name": { + "type": [ + "string", + "null" + ] + }, + "registry": { + "type": [ + "string", + "null" + ] + } + }, + "type": "object" + }, + "type": "array" + }, + { + "type": "null" + } +] - removed
Output schema / properties / cc / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / cc / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / found / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / found / typeAdded value: +[ + "boolean", + "null" +] - removed
Output schema / properties / ip / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / ip / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / ok / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / ok / typeAdded value: +[ + "boolean", + "null" +] - removed
Output schema / properties / prefix / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / prefix / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / query / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / query / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / registry / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / registry / typeAdded value: +[ + "string", + "null" +]
- Changed
check_dns7 fields changed- removed
Output schema / properties / domain / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / domain / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / found / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / found / typeAdded value: +[ + "boolean", + "null" +] - removed
Output schema / properties / ok / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / ok / typeAdded value: +[ + "boolean", + "null" +] - changed
Output schema / properties / records / anyOfPrevious value: -[ - { - "items": { - "additionalProperties": {}, - "properties": { - "error": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - }, - "type": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - }, - "values": { - "anyOf": [ - { - "items": { - "type": "string" - }, - "type": "array" - }, - { - "type": "null" - } - ] - } - }, - "type": "object" - }, - "type": "array" - }, - { - "type": "null" - } -]New value: +[ + { + "items": { + "additionalProperties": {}, + "properties": { + "error": { + "type": [ + "string", + "null" + ] + }, + "type": { + "type": [ + "string", + "null" + ] + }, + "values": { + "anyOf": [ + { + "items": { + "type": "string" + }, + "type": "array" + }, + { + "type": "null" + } + ] + } + }, + "type": "object" + }, + "type": "array" + }, + { + "type": "null" + } +]
- Changed
check_ssl38 fields changed- removed
Output schema / properties / authorizationError / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / authorizationError / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / daysUntilExpiry / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / daysUntilExpiry / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / expired / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / expired / typeAdded value: +[ + "boolean", + "null" +] - removed
Output schema / properties / fingerprint256 / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / fingerprint256 / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / found / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / found / typeAdded value: +[ + "boolean", + "null" +] - removed
Output schema / properties / host / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / host / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / hostnameMatch / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / hostnameMatch / typeAdded value: +[ + "boolean", + "null" +] - removed
Output schema / properties / ip / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / ip / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / issuerCN / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / issuerCN / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / issuerO / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / issuerO / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / notYetValid / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / notYetValid / typeAdded value: +[ + "boolean", + "null" +] - removed
Output schema / properties / ok / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / ok / typeAdded value: +[ + "boolean", + "null" +] - removed
Output schema / properties / port / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / port / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / selfSigned / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / selfSigned / typeAdded value: +[ + "boolean", + "null" +] - removed
Output schema / properties / serialNumber / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / serialNumber / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / subjectCN / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / subjectCN / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / trusted / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / trusted / typeAdded value: +[ + "boolean", + "null" +] - removed
Output schema / properties / validFrom / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / validFrom / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / validTo / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / validTo / typeAdded value: +[ + "string", + "null" +]
- Changed
dkim_check19 fields changed- removed
Output schema / properties / bits / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / bits / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / domain / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / domain / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / error / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / error / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / found / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / found / typeAdded value: +[ + "boolean", + "null" +] - removed
Output schema / properties / hasKey / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / hasKey / typeAdded value: +[ + "boolean", + "null" +] - removed
Output schema / properties / keyType / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / keyType / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / ok / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / ok / typeAdded value: +[ + "boolean", + "null" +] - removed
Output schema / properties / record / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / record / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / selector / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / selector / typeAdded value: +[ + "string", + "null" +] - changed
Output schema / properties / tags / anyOfPrevious value: -[ - { - "items": { - "additionalProperties": {}, - "properties": { - "tag": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - }, - "value": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - } - }, - "type": "object" - }, - "type": "array" - }, - { - "type": "null" - } -]New value: +[ + { + "items": { + "additionalProperties": {}, + "properties": { + "tag": { + "type": [ + "string", + "null" + ] + }, + "value": { + "type": [ + "string", + "null" + ] + } + }, + "type": "object" + }, + "type": "array" + }, + { + "type": "null" + } +]
- Changed
dmarc_check17 fields changed- removed
Output schema / properties / domain / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / domain / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / error / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / error / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / found / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / found / typeAdded value: +[ + "boolean", + "null" +] - removed
Output schema / properties / ok / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / ok / typeAdded value: +[ + "boolean", + "null" +] - removed
Output schema / properties / pct / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / pct / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / policy / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / policy / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / record / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / record / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / subPolicy / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / subPolicy / typeAdded value: +[ + "string", + "null" +] - changed
Output schema / properties / tags / anyOfPrevious value: -[ - { - "items": { - "additionalProperties": {}, - "properties": { - "tag": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - }, - "value": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - } - }, - "type": "object" - }, - "type": "array" - }, - { - "type": "null" - } -]New value: +[ + { + "items": { + "additionalProperties": {}, + "properties": { + "tag": { + "type": [ + "string", + "null" + ] + }, + "value": { + "type": [ + "string", + "null" + ] + } + }, + "type": "object" + }, + "type": "array" + }, + { + "type": "null" + } +]
- Changed
dns_propagation9 fields changed- removed
Output schema / properties / consistent / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / consistent / typeAdded value: +[ + "boolean", + "null" +] - removed
Output schema / properties / domain / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / domain / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / ok / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / ok / typeAdded value: +[ + "boolean", + "null" +] - changed
Output schema / properties / results / anyOfPrevious value: -[ - { - "items": { - "additionalProperties": {}, - "properties": { - "error": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - }, - "resolver": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - }, - "server": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - }, - "values": { - "anyOf": [ - { - "items": { - "type": "string" - }, - "type": "array" - }, - { - "type": "null" - } - ] - } - }, - "type": "object" - }, - "type": "array" - }, - { - "type": "null" - } -]New value: +[ + { + "items": { + "additionalProperties": {}, + "properties": { + "error": { + "type": [ + "string", + "null" + ] + }, + "resolver": { + "type": [ + "string", + "null" + ] + }, + "server": { + "type": [ + "string", + "null" + ] + }, + "values": { + "anyOf": [ + { + "items": { + "type": "string" + }, + "type": "array" + }, + { + "type": "null" + } + ] + } + }, + "type": "object" + }, + "type": "array" + }, + { + "type": "null" + } +] - removed
Output schema / properties / type / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / type / typeAdded value: +[ + "string", + "null" +]
- Changed
dnsbl_check15 fields changed- removed
Output schema / properties / clean / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / clean / typeAdded value: +[ + "boolean", + "null" +] - removed
Output schema / properties / ip / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / ip / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / listedCount / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / listedCount / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / ok / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / ok / typeAdded value: +[ + "boolean", + "null" +] - removed
Output schema / properties / partial / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / partial / typeAdded value: +[ + "boolean", + "null" +] - changed
Output schema / properties / results / anyOfPrevious value: -[ - { - "items": { - "additionalProperties": {}, - "properties": { - "code": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - }, - "delistUrl": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - }, - "error": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - }, - "listKey": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - }, - "listed": { - "anyOf": [ - { - "type": "boolean" - }, - { - "type": "null" - } - ] - }, - "name": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - }, - "reason": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - } - }, - "type": "object" - }, - "type": "array" - }, - { - "type": "null" - } -]New value: +[ + { + "items": { + "additionalProperties": {}, + "properties": { + "code": { + "type": [ + "string", + "null" + ] + }, + "delistUrl": { + "type": [ + "string", + "null" + ] + }, + "error": { + "type": [ + "string", + "null" + ] + }, + "listKey": { + "type": [ + "string", + "null" + ] + }, + "listed": { + "type": [ + "boolean", + "null" + ] + }, + "name": { + "type": [ + "string", + "null" + ] + }, + "reason": { + "type": [ + "string", + "null" + ] + } + }, + "type": "object" + }, + "type": "array" + }, + { + "type": "null" + } +] - removed
Output schema / properties / total / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / total / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / zonesQueried / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / zonesQueried / typeAdded value: +[ + "number", + "null" +]
- Changed
domain_expiry22 fields changed- removed
Output schema / properties / createdAt / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / createdAt / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / daysUntilExpiry / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / daysUntilExpiry / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / domain / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / domain / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / error / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / error / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / expiresAt / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / expiresAt / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / found / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / found / typeAdded value: +[ + "boolean", + "null" +] - removed
Output schema / properties / ok / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / ok / typeAdded value: +[ + "boolean", + "null" +] - removed
Output schema / properties / registrar / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / registrar / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / tld / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / tld / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / tldSupported / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / tldSupported / typeAdded value: +[ + "boolean", + "null" +] - removed
Output schema / properties / updatedAt / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / updatedAt / typeAdded value: +[ + "string", + "null" +]
- Changed
hsts_check18 fields changed- removed
Output schema / properties / domain / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / domain / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / httpsRedirect / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / httpsRedirect / typeAdded value: +[ + "boolean", + "null" +] - removed
Output schema / properties / includeSubDomains / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / includeSubDomains / typeAdded value: +[ + "boolean", + "null" +] - removed
Output schema / properties / maxAge / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / maxAge / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / ok / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / ok / typeAdded value: +[ + "boolean", + "null" +] - removed
Output schema / properties / preload / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / preload / typeAdded value: +[ + "boolean", + "null" +] - removed
Output schema / properties / preloadReady / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / preloadReady / typeAdded value: +[ + "boolean", + "null" +] - removed
Output schema / properties / present / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / present / typeAdded value: +[ + "boolean", + "null" +] - removed
Output schema / properties / raw / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / raw / typeAdded value: +[ + "string", + "null" +]
- Changed
http_headers9 fields changed- removed
Output schema / properties / ok / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / ok / typeAdded value: +[ + "boolean", + "null" +] - changed
Output schema / properties / redirects / anyOfPrevious value: -[ - { - "items": { - "additionalProperties": {}, - "properties": { - "from": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - }, - "status": { - "anyOf": [ - { - "type": "number" - }, - { - "type": "null" - } - ] - }, - "to": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - } - }, - "type": "object" - }, - "type": "array" - }, - { - "type": "null" - } -]New value: +[ + { + "items": { + "additionalProperties": {}, + "properties": { + "from": { + "type": [ + "string", + "null" + ] + }, + "status": { + "type": [ + "number", + "null" + ] + }, + "to": { + "type": [ + "string", + "null" + ] + } + }, + "type": "object" + }, + "type": "array" + }, + { + "type": "null" + } +] - removed
Output schema / properties / status / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / status / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / statusText / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / statusText / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / url / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / url / typeAdded value: +[ + "string", + "null" +]
- Changed
ip_geolocation19 fields changed- changed
Output schema / properties / asns / anyOfPrevious value: -[ - { - "items": { - "additionalProperties": {}, - "properties": { - "allocated": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - }, - "asn": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - }, - "cc": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - }, - "name": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - }, - "registry": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - } - }, - "type": "object" - }, - "type": "array" - }, - { - "type": "null" - } -]New value: +[ + { + "items": { + "additionalProperties": {}, + "properties": { + "allocated": { + "type": [ + "string", + "null" + ] + }, + "asn": { + "type": [ + "string", + "null" + ] + }, + "cc": { + "type": [ + "string", + "null" + ] + }, + "name": { + "type": [ + "string", + "null" + ] + }, + "registry": { + "type": [ + "string", + "null" + ] + } + }, + "type": "object" + }, + "type": "array" + }, + { + "type": "null" + } +] - removed
Output schema / properties / cc / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / cc / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / found / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / found / typeAdded value: +[ + "boolean", + "null" +] - removed
Output schema / properties / ip / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / ip / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / ok / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / ok / typeAdded value: +[ + "boolean", + "null" +] - removed
Output schema / properties / prefix / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / prefix / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / ptr / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / ptr / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / query / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / query / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / registry / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / registry / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / resolvedFromDomain / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / resolvedFromDomain / typeAdded value: +[ + "boolean", + "null" +]
- Changed
mx_lookup7 fields changed- removed
Output schema / properties / domain / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / domain / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / found / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / found / typeAdded value: +[ + "boolean", + "null" +] - removed
Output schema / properties / ok / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / ok / typeAdded value: +[ + "boolean", + "null" +] - changed
Output schema / properties / servers / anyOfPrevious value: -[ - { - "items": { - "additionalProperties": {}, - "properties": { - "exchange": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - }, - "ipv4": { - "anyOf": [ - { - "items": { - "type": "string" - }, - "type": "array" - }, - { - "type": "null" - } - ] - }, - "ipv6": { - "anyOf": [ - { - "items": { - "type": "string" - }, - "type": "array" - }, - { - "type": "null" - } - ] - }, - "priority": { - "anyOf": [ - { - "type": "number" - }, - { - "type": "null" - } - ] - }, - "private": { - "anyOf": [ - { - "type": "boolean" - }, - { - "type": "null" - } - ] - } - }, - "type": "object" - }, - "type": "array" - }, - { - "type": "null" - } -]New value: +[ + { + "items": { + "additionalProperties": {}, + "properties": { + "exchange": { + "type": [ + "string", + "null" + ] + }, + "ipv4": { + "anyOf": [ + { + "items": { + "type": "string" + }, + "type": "array" + }, + { + "type": "null" + } + ] + }, + "ipv6": { + "anyOf": [ + { + "items": { + "type": "string" + }, + "type": "array" + }, + { + "type": "null" + } + ] + }, + "priority": { + "type": [ + "number", + "null" + ] + }, + "private": { + "type": [ + "boolean", + "null" + ] + } + }, + "type": "object" + }, + "type": "array" + }, + { + "type": "null" + } +]
- Changed
ping_test21 fields changed- changed
Output schema / properties / attempts / anyOfPrevious value: -[ - { - "items": { - "additionalProperties": {}, - "properties": { - "seq": { - "anyOf": [ - { - "type": "number" - }, - { - "type": "null" - } - ] - }, - "timeMs": { - "anyOf": [ - { - "type": "number" - }, - { - "type": "null" - } - ] - } - }, - "type": "object" - }, - "type": "array" - }, - { - "type": "null" - } -]New value: +[ + { + "items": { + "additionalProperties": {}, + "properties": { + "seq": { + "type": [ + "number", + "null" + ] + }, + "timeMs": { + "type": [ + "number", + "null" + ] + } + }, + "type": "object" + }, + "type": "array" + }, + { + "type": "null" + } +] - removed
Output schema / properties / avgMs / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / avgMs / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / host / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / host / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / ip / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / ip / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / lossPct / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / lossPct / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / maxMs / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / maxMs / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / minMs / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / minMs / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / ok / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / ok / typeAdded value: +[ + "boolean", + "null" +] - removed
Output schema / properties / port / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / port / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / received / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / received / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / sent / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / sent / typeAdded value: +[ + "number", + "null" +]
- Changed
port_check17 fields changed- removed
Output schema / properties / host / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / host / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / ip / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / ip / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / ok / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / ok / typeAdded value: +[ + "boolean", + "null" +] - removed
Output schema / properties / partial / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / partial / typeAdded value: +[ + "boolean", + "null" +] - removed
Output schema / properties / port / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / port / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / portsRequested / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / portsRequested / typeAdded value: +[ + "number", + "null" +] - changed
Output schema / properties / results / anyOfPrevious value: -[ - { - "items": { - "additionalProperties": {}, - "properties": { - "error": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - }, - "ip": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - }, - "port": { - "anyOf": [ - { - "type": "number" - }, - { - "type": "null" - } - ] - }, - "state": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - }, - "timeMs": { - "anyOf": [ - { - "type": "number" - }, - { - "type": "null" - } - ] - } - }, - "type": "object" - }, - "type": "array" - }, - { - "type": "null" - } -]New value: +[ + { + "items": { + "additionalProperties": {}, + "properties": { + "error": { + "type": [ + "string", + "null" + ] + }, + "ip": { + "type": [ + "string", + "null" + ] + }, + "port": { + "type": [ + "number", + "null" + ] + }, + "state": { + "type": [ + "string", + "null" + ] + }, + "timeMs": { + "type": [ + "number", + "null" + ] + } + }, + "type": "object" + }, + "type": "array" + }, + { + "type": "null" + } +] - removed
Output schema / properties / state / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / state / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / timeMs / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / timeMs / typeAdded value: +[ + "number", + "null" +]
- Changed
redirect_check13 fields changed- removed
Output schema / properties / finalStatus / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / finalStatus / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / finalStatusText / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / finalStatusText / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / finalUrl / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / finalUrl / typeAdded value: +[ + "string", + "null" +] - changed
Output schema / properties / hops / anyOfPrevious value: -[ - { - "items": { - "additionalProperties": {}, - "properties": { - "from": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - }, - "status": { - "anyOf": [ - { - "type": "number" - }, - { - "type": "null" - } - ] - }, - "to": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - } - }, - "type": "object" - }, - "type": "array" - }, - { - "type": "null" - } -]New value: +[ + { + "items": { + "additionalProperties": {}, + "properties": { + "from": { + "type": [ + "string", + "null" + ] + }, + "status": { + "type": [ + "number", + "null" + ] + }, + "to": { + "type": [ + "string", + "null" + ] + } + }, + "type": "object" + }, + "type": "array" + }, + { + "type": "null" + } +] - removed
Output schema / properties / ok / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / ok / typeAdded value: +[ + "boolean", + "null" +] - removed
Output schema / properties / start / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / start / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / totalHops / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / totalHops / typeAdded value: +[ + "number", + "null" +]
- Changed
response_time18 fields changed- removed
Output schema / properties / avg / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / avg / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / max / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / max / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / min / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / min / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / ok / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / ok / typeAdded value: +[ + "boolean", + "null" +] - removed
Output schema / properties / partial / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / partial / typeAdded value: +[ + "boolean", + "null" +] - removed
Output schema / properties / samplesRequested / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / samplesRequested / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / status / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / status / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / up / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / up / typeAdded value: +[ + "boolean", + "null" +] - removed
Output schema / properties / url / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / url / typeAdded value: +[ + "string", + "null" +]
- Changed
reverse_dns6 fields changed- removed
Output schema / properties / error / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / error / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / ip / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / ip / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / ok / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / ok / typeAdded value: +[ + "boolean", + "null" +]
- Changed
spf_check15 fields changed- removed
Output schema / properties / all / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / all / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / domain / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / domain / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / error / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / error / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / found / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / found / typeAdded value: +[ + "boolean", + "null" +] - removed
Output schema / properties / lookups / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / lookups / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / ok / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / ok / typeAdded value: +[ + "boolean", + "null" +] - removed
Output schema / properties / record / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / record / typeAdded value: +[ + "string", + "null" +] - changed
Output schema / properties / terms / anyOfPrevious value: -[ - { - "items": { - "additionalProperties": {}, - "properties": { - "qualifier": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - }, - "term": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - }, - "type": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - } - }, - "type": "object" - }, - "type": "array" - }, - { - "type": "null" - } -]New value: +[ + { + "items": { + "additionalProperties": {}, + "properties": { + "qualifier": { + "type": [ + "string", + "null" + ] + }, + "term": { + "type": [ + "string", + "null" + ] + }, + "type": { + "type": [ + "string", + "null" + ] + } + }, + "type": "object" + }, + "type": "array" + }, + { + "type": "null" + } +]
- Changed
website_status16 fields changed- removed
Output schema / properties / ok / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / ok / typeAdded value: +[ + "boolean", + "null" +] - removed
Output schema / properties / redirects / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / redirects / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / responseTimeMs / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / responseTimeMs / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / server / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / server / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / status / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / status / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / statusText / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / statusText / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / up / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / up / typeAdded value: +[ + "boolean", + "null" +] - removed
Output schema / properties / url / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / url / typeAdded value: +[ + "string", + "null" +]
- Changed
whois21 fields changed- changed
Output schema / properties / contacts / anyOfPrevious value: -[ - { - "items": { - "additionalProperties": {}, - "properties": { - "name": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - }, - "role": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - } - }, - "type": "object" - }, - "type": "array" - }, - { - "type": "null" - } -]New value: +[ + { + "items": { + "additionalProperties": {}, + "properties": { + "name": { + "type": [ + "string", + "null" + ] + }, + "role": { + "type": [ + "string", + "null" + ] + } + }, + "type": "object" + }, + "type": "array" + }, + { + "type": "null" + } +] - removed
Output schema / properties / createdAt / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / createdAt / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / domain / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / domain / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / error / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / error / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / expiresAt / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / expiresAt / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / found / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / found / typeAdded value: +[ + "boolean", + "null" +] - removed
Output schema / properties / ok / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / ok / typeAdded value: +[ + "boolean", + "null" +] - removed
Output schema / properties / registrar / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / registrar / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / tld / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / tld / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / tldSupported / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / tldSupported / typeAdded value: +[ + "boolean", + "null" +] - removed
Output schema / properties / updatedAt / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / updatedAt / typeAdded value: +[ + "string", + "null" +]
13 tool updates
- Removed
alert_history - Removed
billing_summary - Removed
check_history - Removed
get_organization - Removed
list_alert_channels - Removed
list_customers - Removed
list_incidents - Removed
list_maintenance_windows - Removed
list_monitors - Removed
list_status_pages - Removed
list_users - Removed
monitor_status - Removed
uptime_summary
8 tool updates
- Added
alert_history - Added
billing_summary - Added
get_organization - Added
list_alert_channels - Added
list_customers - Added
list_maintenance_windows - Added
list_status_pages - Added
list_users
3 tool updates
- Changed
check_history2 fields changed- added
Input schema / properties / kindAdded value: +{ + "description": "Monitor family. Omit to cover all eight. One of: website, dns, icmp, tcp, ftp, smtp, ssh, imap_pop", + "enum": [ + "website", + "dns", + "icmp", + "tcp", + "ftp", + "smtp", + "ssh", + "imap_pop" + ], + "type": "string" +} - changed
Input schema / properties / monitor_id / descriptionPrevious value: -"The monitor/website id"New value: +"The monitor id"
- Changed
list_monitors5 fields changed- added
Input schema / properties / kindAdded value: +{ + "description": "Monitor family. Omit to cover all eight. One of: website, dns, icmp, tcp, ftp, smtp, ssh, imap_pop", + "enum": [ + "website", + "dns", + "icmp", + "tcp", + "ftp", + "smtp", + "ssh", + "imap_pop" + ], + "type": "string" +} - changed
Output schema / properties / items / anyOfPrevious value: -[ - { - "items": { - "additionalProperties": {}, - "properties": { - "avgResponseDay": { - "anyOf": [ - { - "type": "number" - }, - { - "type": "null" - } - ] - }, - "avgResponseMonth": { - "anyOf": [ - { - "type": "number" - }, - { - "type": "null" - } - ] - }, - "avgResponseYear": { - "anyOf": [ - { - "type": "number" - }, - { - "type": "null" - } - ] - }, - "hasCritical": { - "anyOf": [ - { - "type": "boolean" - }, - { - "type": "null" - } - ] - }, - "hasWarning": { - "anyOf": [ - { - "type": "boolean" - }, - { - "type": "null" - } - ] - }, - "id": { - "anyOf": [ - { - "type": "number" - }, - { - "type": "null" - } - ] - }, - "isDown": { - "anyOf": [ - { - "type": "boolean" - }, - { - "type": "null" - } - ] - }, - "isRecovering": { - "anyOf": [ - { - "type": "boolean" - }, - { - "type": "null" - } - ] - }, - "monitoringType": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - }, - "name": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - }, - "publicId": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - }, - "upSinceAt": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - }, - "uptimeDay": { - "anyOf": [ - { - "anyOf": [ - { - "type": "number" - }, - { - "type": "string" - } - ] - }, - { - "type": "null" - } - ] - }, - "uptimeMonth": { - "anyOf": [ - { - "anyOf": [ - { - "type": "number" - }, - { - "type": "string" - } - ] - }, - { - "type": "null" - } - ] - }, - "uptimeYear": { - "anyOf": [ - { - "anyOf": [ - { - "type": "number" - }, - { - "type": "string" - } - ] - }, - { - "type": "null" - } - ] - }, - "url": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ] - } - }, - "type": "object" - }, - "type": "array" - }, - { - "type": "null" - } -]New value: +[ + { + "items": { + "additionalProperties": {}, + "properties": { + "avgResponseDay": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "avgResponseMonth": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "avgResponseYear": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "hasCritical": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "hasWarning": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "id": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "isDown": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "isRecovering": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "kind": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "monitoringType": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "name": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "publicId": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "upSinceAt": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "uptimeDay": { + "anyOf": [ + { + "anyOf": [ + { + "type": "number" + }, + { + "type": "string" + } + ] + }, + { + "type": "null" + } + ] + }, + "uptimeMonth": { + "anyOf": [ + { + "anyOf": [ + { + "type": "number" + }, + { + "type": "string" + } + ] + }, + { + "type": "null" + } + ] + }, + "uptimeYear": { + "anyOf": [ + { + "anyOf": [ + { + "type": "number" + }, + { + "type": "string" + } + ] + }, + { + "type": "null" + } + ] + }, + "url": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + } + }, + "type": "object" + }, + "type": "array" + }, + { + "type": "null" + } +] - removed
Output schema / properties / pageRemoved value: -{ - "anyOf": [ - { - "type": "number" - }, - { - "type": "null" - } - ] -} - added
Output schema / properties / partialFailuresAdded value: +{ + "anyOf": [ + { + "items": { + "type": "string" + }, + "type": "array" + }, + { + "type": "null" + } + ] +} - removed
Output schema / properties / perPageRemoved value: -{ - "anyOf": [ - { - "type": "number" - }, - { - "type": "null" - } - ] -}
- Changed
monitor_status2 fields changed- added
Input schema / properties / kindAdded value: +{ + "description": "Monitor family. Omit to cover all eight. One of: website, dns, icmp, tcp, ftp, smtp, ssh, imap_pop", + "enum": [ + "website", + "dns", + "icmp", + "tcp", + "ftp", + "smtp", + "ssh", + "imap_pop" + ], + "type": "string" +} - added
Output schema / properties / kindAdded value: +{ + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] +}
3 tool updates
- Changed
dnsbl_check2 fields changed- added
Output schema / properties / partialAdded value: +{ + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] +} - added
Output schema / properties / zonesQueriedAdded value: +{ + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] +}
- Changed
port_check8 fields changed- added
Input schema / properties / port / anyOfAdded value: +[ + { + "maximum": 65535, + "minimum": 1, + "type": "integer" + }, + { + "items": { + "maximum": 65535, + "minimum": 1, + "type": "integer" + }, + "maxItems": 10, + "minItems": 1, + "type": "array" + } +] - changed
Input schema / properties / port / descriptionPrevious value: -"TCP port to test"New value: +"TCP port, or a list of up to 10 ports, e.g. 443 or [80, 443, 25]" - removed
Input schema / properties / port / maximumRemoved value: -65535 - removed
Input schema / properties / port / minimumRemoved value: -1 - removed
Input schema / properties / port / typeRemoved value: -"integer" - added
Output schema / properties / partialAdded value: +{ + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] +} - added
Output schema / properties / portsRequestedAdded value: +{ + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] +} - added
Output schema / properties / resultsAdded value: +{ + "anyOf": [ + { + "items": { + "additionalProperties": {}, + "properties": { + "error": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "ip": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "port": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "state": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "timeMs": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + } + }, + "type": "object" + }, + "type": "array" + }, + { + "type": "null" + } + ] +}
- Changed
response_time2 fields changed- added
Output schema / properties / partialAdded value: +{ + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] +} - added
Output schema / properties / samplesRequestedAdded value: +{ + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] +}
25 tool updates
- Changed
asn_lookup1 field changed- changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": {}, + "properties": { + "asns": { + "anyOf": [ + { + "items": { + "additionalProperties": {}, + "properties": { + "allocated": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "asn": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "cc": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "name": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "registry": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + } + }, + "type": "object" + }, + "type": "array" + }, + { + "type": "null" + } + ] + }, + "cc": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "found": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "ip": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "ok": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "prefix": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "query": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "registry": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + } + }, + "type": "object" +}
- Changed
check_dns1 field changed- changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": {}, + "properties": { + "domain": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "found": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "ok": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "records": { + "anyOf": [ + { + "items": { + "additionalProperties": {}, + "properties": { + "error": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "type": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "values": { + "anyOf": [ + { + "items": { + "type": "string" + }, + "type": "array" + }, + { + "type": "null" + } + ] + } + }, + "type": "object" + }, + "type": "array" + }, + { + "type": "null" + } + ] + }, + "warnings": { + "anyOf": [ + { + "items": { + "type": "string" + }, + "type": "array" + }, + { + "type": "null" + } + ] + } + }, + "type": "object" +}
- Changed
check_history1 field changed- changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": {}, + "properties": { + "data": { + "anyOf": [ + { + "items": { + "additionalProperties": {}, + "properties": { + "checkedAt": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "errorMessage": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "id": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "location": { + "anyOf": [ + { + "additionalProperties": {}, + "properties": { + "code": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "name": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + } + }, + "type": "object" + }, + { + "type": "null" + } + ] + }, + "responseTimeMs": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "status": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "success": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + } + }, + "type": "object" + }, + "type": "array" + }, + { + "type": "null" + } + ] + }, + "page": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "pageCount": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "total": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + } + }, + "type": "object" +}
- Changed
check_ssl1 field changed- changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": {}, + "properties": { + "authorizationError": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "daysUntilExpiry": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "expired": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "fingerprint256": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "found": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "host": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "hostnameMatch": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "ip": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "issuerCN": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "issuerO": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "notYetValid": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "ok": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "port": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "san": { + "anyOf": [ + { + "items": { + "type": "string" + }, + "type": "array" + }, + { + "type": "null" + } + ] + }, + "selfSigned": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "serialNumber": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "subjectCN": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "trusted": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "validFrom": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "validTo": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + } + }, + "type": "object" +}
- Changed
dkim_check1 field changed- changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": {}, + "properties": { + "bits": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "domain": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "error": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "found": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "hasKey": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "keyType": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "ok": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "record": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "selector": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "tags": { + "anyOf": [ + { + "items": { + "additionalProperties": {}, + "properties": { + "tag": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "value": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + } + }, + "type": "object" + }, + "type": "array" + }, + { + "type": "null" + } + ] + }, + "warnings": { + "anyOf": [ + { + "items": { + "type": "string" + }, + "type": "array" + }, + { + "type": "null" + } + ] + } + }, + "type": "object" +}
- Changed
dmarc_check1 field changed- changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": {}, + "properties": { + "domain": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "error": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "found": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "ok": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "pct": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "policy": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "record": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "subPolicy": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "tags": { + "anyOf": [ + { + "items": { + "additionalProperties": {}, + "properties": { + "tag": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "value": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + } + }, + "type": "object" + }, + "type": "array" + }, + { + "type": "null" + } + ] + }, + "warnings": { + "anyOf": [ + { + "items": { + "type": "string" + }, + "type": "array" + }, + { + "type": "null" + } + ] + } + }, + "type": "object" +}
- Changed
dns_propagation1 field changed- changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": {}, + "properties": { + "consistent": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "domain": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "ok": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "results": { + "anyOf": [ + { + "items": { + "additionalProperties": {}, + "properties": { + "error": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "resolver": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "server": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "values": { + "anyOf": [ + { + "items": { + "type": "string" + }, + "type": "array" + }, + { + "type": "null" + } + ] + } + }, + "type": "object" + }, + "type": "array" + }, + { + "type": "null" + } + ] + }, + "type": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + } + }, + "type": "object" +}
- Changed
dnsbl_check1 field changed- changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": {}, + "properties": { + "clean": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "ip": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "listedCount": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "ok": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "results": { + "anyOf": [ + { + "items": { + "additionalProperties": {}, + "properties": { + "code": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "delistUrl": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "error": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "listKey": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "listed": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "name": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "reason": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + } + }, + "type": "object" + }, + "type": "array" + }, + { + "type": "null" + } + ] + }, + "total": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + } + }, + "type": "object" +}
- Changed
domain_expiry1 field changed- changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": {}, + "properties": { + "createdAt": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "daysUntilExpiry": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "domain": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "error": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "expiresAt": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "found": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "ok": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "registrar": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "statuses": { + "anyOf": [ + { + "items": { + "type": "string" + }, + "type": "array" + }, + { + "type": "null" + } + ] + }, + "tld": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "tldSupported": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "updatedAt": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + } + }, + "type": "object" +}
- Changed
hsts_check1 field changed- changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": {}, + "properties": { + "domain": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "httpsRedirect": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "includeSubDomains": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "maxAge": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "ok": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "preload": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "preloadReady": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "present": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "raw": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "warnings": { + "anyOf": [ + { + "items": { + "type": "string" + }, + "type": "array" + }, + { + "type": "null" + } + ] + } + }, + "type": "object" +}
- Changed
http_headers1 field changed- changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": {}, + "properties": { + "headers": { + "anyOf": [ + { + "additionalProperties": { + "type": "string" + }, + "propertyNames": { + "type": "string" + }, + "type": "object" + }, + { + "type": "null" + } + ] + }, + "ok": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "redirects": { + "anyOf": [ + { + "items": { + "additionalProperties": {}, + "properties": { + "from": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "status": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "to": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + } + }, + "type": "object" + }, + "type": "array" + }, + { + "type": "null" + } + ] + }, + "status": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "statusText": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "url": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + } + }, + "type": "object" +}
- Changed
ip_geolocation1 field changed- changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": {}, + "properties": { + "asns": { + "anyOf": [ + { + "items": { + "additionalProperties": {}, + "properties": { + "allocated": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "asn": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "cc": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "name": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "registry": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + } + }, + "type": "object" + }, + "type": "array" + }, + { + "type": "null" + } + ] + }, + "cc": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "found": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "ip": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "ok": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "prefix": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "ptr": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "query": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "registry": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "resolvedFromDomain": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + } + }, + "type": "object" +}
- Changed
list_incidents1 field changed- changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": {}, + "properties": { + "incidents": { + "anyOf": [ + { + "items": { + "additionalProperties": {}, + "properties": { + "customer": { + "anyOf": [ + { + "additionalProperties": {}, + "properties": { + "company": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "email": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "id": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "publicId": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + } + }, + "type": "object" + }, + { + "type": "null" + } + ] + }, + "error_message": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "id": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "monitor": { + "anyOf": [ + { + "additionalProperties": {}, + "properties": { + "hostname": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "kind": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "name": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "publicId": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + } + }, + "type": "object" + }, + { + "type": "null" + } + ] + }, + "publicId": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "resolved_at": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "response_time_ms": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "severity": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "severityLevel": { + "anyOf": [ + { + "anyOf": [ + { + "type": "number" + }, + { + "type": "string" + } + ] + }, + { + "type": "null" + } + ] + }, + "source": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "started_at": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "status": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "status_code": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "summary": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "title": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "website": { + "anyOf": [ + { + "additionalProperties": {}, + "properties": { + "id": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "name": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "publicId": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "status": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "url": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + } + }, + "type": "object" + }, + { + "type": "null" + } + ] + }, + "websiteId": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + } + }, + "type": "object" + }, + "type": "array" + }, + { + "type": "null" + } + ] + } + }, + "type": "object" +}
- Changed
list_monitors1 field changed- changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": {}, + "properties": { + "items": { + "anyOf": [ + { + "items": { + "additionalProperties": {}, + "properties": { + "avgResponseDay": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "avgResponseMonth": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "avgResponseYear": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "hasCritical": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "hasWarning": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "id": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "isDown": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "isRecovering": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "monitoringType": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "name": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "publicId": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "upSinceAt": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "uptimeDay": { + "anyOf": [ + { + "anyOf": [ + { + "type": "number" + }, + { + "type": "string" + } + ] + }, + { + "type": "null" + } + ] + }, + "uptimeMonth": { + "anyOf": [ + { + "anyOf": [ + { + "type": "number" + }, + { + "type": "string" + } + ] + }, + { + "type": "null" + } + ] + }, + "uptimeYear": { + "anyOf": [ + { + "anyOf": [ + { + "type": "number" + }, + { + "type": "string" + } + ] + }, + { + "type": "null" + } + ] + }, + "url": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + } + }, + "type": "object" + }, + "type": "array" + }, + { + "type": "null" + } + ] + }, + "page": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "perPage": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "total": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + } + }, + "type": "object" +}
- Changed
monitor_status1 field changed- changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": {}, + "properties": { + "avgResponseDay": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "avgResponseMonth": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "avgResponseYear": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "createdAt": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "hasCritical": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "hasWarning": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "id": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "isActive": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "isDown": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "isRecovering": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "monitoringType": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "name": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "publicId": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "upSinceAt": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "updatedAt": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "uptimeDay": { + "anyOf": [ + { + "anyOf": [ + { + "type": "number" + }, + { + "type": "string" + } + ] + }, + { + "type": "null" + } + ] + }, + "uptimeMonth": { + "anyOf": [ + { + "anyOf": [ + { + "type": "number" + }, + { + "type": "string" + } + ] + }, + { + "type": "null" + } + ] + }, + "uptimeYear": { + "anyOf": [ + { + "anyOf": [ + { + "type": "number" + }, + { + "type": "string" + } + ] + }, + { + "type": "null" + } + ] + }, + "url": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + } + }, + "type": "object" +}
- Changed
mx_lookup1 field changed- changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": {}, + "properties": { + "domain": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "found": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "ok": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "servers": { + "anyOf": [ + { + "items": { + "additionalProperties": {}, + "properties": { + "exchange": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "ipv4": { + "anyOf": [ + { + "items": { + "type": "string" + }, + "type": "array" + }, + { + "type": "null" + } + ] + }, + "ipv6": { + "anyOf": [ + { + "items": { + "type": "string" + }, + "type": "array" + }, + { + "type": "null" + } + ] + }, + "priority": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "private": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + } + }, + "type": "object" + }, + "type": "array" + }, + { + "type": "null" + } + ] + } + }, + "type": "object" +}
- Changed
ping_test1 field changed- changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": {}, + "properties": { + "attempts": { + "anyOf": [ + { + "items": { + "additionalProperties": {}, + "properties": { + "seq": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "timeMs": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + } + }, + "type": "object" + }, + "type": "array" + }, + { + "type": "null" + } + ] + }, + "avgMs": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "host": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "ip": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "lossPct": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "maxMs": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "minMs": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "ok": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "port": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "received": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "sent": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + } + }, + "type": "object" +}
- Changed
port_check1 field changed- changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": {}, + "properties": { + "host": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "ip": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "ok": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "port": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "state": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "timeMs": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + } + }, + "type": "object" +}
- Changed
redirect_check1 field changed- changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": {}, + "properties": { + "finalStatus": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "finalStatusText": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "finalUrl": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "hops": { + "anyOf": [ + { + "items": { + "additionalProperties": {}, + "properties": { + "from": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "status": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "to": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + } + }, + "type": "object" + }, + "type": "array" + }, + { + "type": "null" + } + ] + }, + "ok": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "start": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "totalHops": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "warnings": { + "anyOf": [ + { + "items": { + "type": "string" + }, + "type": "array" + }, + { + "type": "null" + } + ] + } + }, + "type": "object" +}
- Changed
response_time1 field changed- changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": {}, + "properties": { + "avg": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "max": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "min": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "ok": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "samples": { + "anyOf": [ + { + "items": { + "type": "number" + }, + "type": "array" + }, + { + "type": "null" + } + ] + }, + "status": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "up": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "url": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + } + }, + "type": "object" +}
- Changed
reverse_dns1 field changed- changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": {}, + "properties": { + "error": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "hostnames": { + "anyOf": [ + { + "items": { + "type": "string" + }, + "type": "array" + }, + { + "type": "null" + } + ] + }, + "ip": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "ok": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + } + }, + "type": "object" +}
- Changed
spf_check1 field changed- changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": {}, + "properties": { + "all": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "domain": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "error": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "found": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "lookups": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "ok": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "record": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "terms": { + "anyOf": [ + { + "items": { + "additionalProperties": {}, + "properties": { + "qualifier": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "term": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "type": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + } + }, + "type": "object" + }, + "type": "array" + }, + { + "type": "null" + } + ] + }, + "warnings": { + "anyOf": [ + { + "items": { + "type": "string" + }, + "type": "array" + }, + { + "type": "null" + } + ] + } + }, + "type": "object" +}
- Changed
uptime_summary1 field changed- changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": {}, + "properties": { + "day": { + "anyOf": [ + { + "anyOf": [ + { + "type": "number" + }, + { + "type": "string" + } + ] + }, + { + "type": "null" + } + ] + }, + "dayAvgResponse": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "month": { + "anyOf": [ + { + "anyOf": [ + { + "type": "number" + }, + { + "type": "string" + } + ] + }, + { + "type": "null" + } + ] + }, + "monthAvgResponse": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "year": { + "anyOf": [ + { + "anyOf": [ + { + "type": "number" + }, + { + "type": "string" + } + ] + }, + { + "type": "null" + } + ] + }, + "yearAvgResponse": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + } + }, + "type": "object" +}
- Changed
website_status1 field changed- changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": {}, + "properties": { + "ok": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "redirects": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "responseTimeMs": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "server": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "status": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ] + }, + "statusText": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "up": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "url": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + } + }, + "type": "object" +}
- Changed
whois1 field changed- changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": {}, + "properties": { + "contacts": { + "anyOf": [ + { + "items": { + "additionalProperties": {}, + "properties": { + "name": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "role": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + } + }, + "type": "object" + }, + "type": "array" + }, + { + "type": "null" + } + ] + }, + "createdAt": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "domain": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "error": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "expiresAt": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "found": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "nameservers": { + "anyOf": [ + { + "items": { + "type": "string" + }, + "type": "array" + }, + { + "type": "null" + } + ] + }, + "ok": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "registrar": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "statuses": { + "anyOf": [ + { + "items": { + "type": "string" + }, + "type": "array" + }, + { + "type": "null" + } + ] + }, + "tld": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "tldSupported": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ] + }, + "updatedAt": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + } + }, + "type": "object" +}
25 tool updates
- First observed
asn_lookup - First observed
check_dns - First observed
check_history - First observed
check_ssl - First observed
dkim_check - First observed
dmarc_check - First observed
dns_propagation - First observed
dnsbl_check - First observed
domain_expiry - First observed
hsts_check - First observed
http_headers - First observed
ip_geolocation - First observed
list_incidents - First observed
list_monitors - First observed
monitor_status - First observed
mx_lookup - First observed
ping_test - First observed
port_check - First observed
redirect_check - First observed
response_time - First observed
reverse_dns - First observed
spf_check - First observed
uptime_summary - First observed
website_status - First observed
whois
Related MCP Connectors
Live DNS, email-auth and redirect checks, HTTP security headers, uptime history, PC hardware prices.
DNS lookups, health reports, SSL certs, security scans, GEO scoring, uptime checks
SSL/TLS scanning, free Let's Encrypt issuance, and certificate-expiry monitoring.
Free owned-agent uptime monitoring, DNS domain proof, signed alerts and opt-in endpoint checks.
Related MCP Servers
- AlicenseAqualityBmaintenanceProvides comprehensive tools for real-time DNS queries across 53 record types, global propagation checks, and SSL certificate analysis. It also enables domain security scans for SPF/DKIM/DMARC configurations and HTTP uptime monitoring.842 npm22Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables live TLS/SSL certificate health checks for any hostname, providing expiry, hostname match, trust verdict, and a health score. Supports both free and paid deep tiers with protocol/cipher analysis.MIT
- AlicenseAqualityCmaintenanceSix-layer website monitoring (uptime, performance, SSL, DNS, visual regression, content change) from Claude, Cline, and Cursor. Free tools (DNS lookup, SSL check, speed test, website checker) work without an account; monitor, incident, alert, and status-page tools use a personal API key.166 npm1MIT
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.