MCP servers › io.github.Nutshell2000 › agent-data-tools-compliance

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

io.github.Nutshell2000/agent-data-tools-compliance

15 tools: OFAC sanctions, counterparty checks, company, domain, email. 25 free calls. — the publisher's description

4 of 5 record checks metRead-only · tools listed 2026-10-23version 1.50.5JavaScriptstreamable HTTP15 tools

Summary

io.github.Nutshell2000/agent-data-tools-compliance is a remote MCP server listed in the official MCP registry at version 1.50.5. On 2026-10-23 ProtocolProbe connected to it in read-only mode and read its inventory: 15 tools, 0 resources and 0 prompts.

Record checks

4 of 5 record checks met · 4 do not apply

met: Registry entry is active and says how to run it
met: Source repository link opens
met: Repository is not archived
met: Code pushed to the repository in the 90 days before our check
not met: Repository publishes a security policy (SECURITY.md)
not applicable: Package names its licence with a standard (SPDX) identifier
not applicable: The version the registry lists can be installed and is not withdrawn
not applicable: npm package carries build provenance (attestation)
not applicable: No known critical or high advisory in the package or its dependencies

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: 0 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs: remote (hosted by the publisher)
Transport: streamable HTTP
Sign-in: none needed to open a session
Repository: public
Tools: 15
Described as changing data: 0 of 15 toolsAI-classified
Mainly works on: accounts and data in outside web services; nothing outside itself: it only answers questionsAI-classified
Last tested: 2026-10-23

Add to your client

How fresh this is

Live-tested

yes, a real session (not a text-only review)

Last tested

2026-10-23

Mode

read-only (no tool calls)

Latest version

1.50.5, published 2026-10-22 (registry, as of the 2026-10-23 snapshot)

First listed version

2026-10-19 (earliest version still in the registry; older removed versions would be earlier)

Version history

54 versions listed, 2026-10-19 to 2026-10-22; 54 in the 90 days before the 2026-10-23 snapshot.

Most recent 12 versions

1.50.5 · 2026-10-22
1.50.4 · 2026-10-22
1.50.3 · 2026-10-22
1.50.2 · 2026-10-22
1.50.1 · 2026-10-22
1.50.0 · 2026-10-22
1.49.1 · 2026-10-22
1.49.0 · 2026-10-22
1.48.6 · 2026-10-22
1.48.5 · 2026-10-22
1.48.4 · 2026-10-22
1.48.3 · 2026-10-22

(versions still listed in the registry only)

Registry data

snapshot 2026-10-23

Package and repository

checked 2026-10-23

Engine

mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 1.50.5 (published 2026-10-22).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory

15tools

0resources

0prompts

What it mainly works on, as our AI model read its tool descriptions: accounts and data in outside web services; nothing outside itself: it only answers questions.

None of its 15 tools are described as changing anything.

check_payeeon 3 other serversreads or searches
“Fast check of a payee before an agent pays it: OFAC SDN match on the address, account type (wallet, delegated wallet or contract) and nonce on Base, Ethereum, Arbitrum, Optimism or Polygon, and optio…”
Publisher declares: read-only yes · destructive no · idempotent no · open-world yes
3 inputs, 1 required
- addressstringrequired“0x address you are about to pay”
- chainstring“Network of the payment: base (default), eth, arb, op or polygon”
- domainstring“Optional: the payee's domain or website URL, e.g.”
check_counterpartyon 6 other serversreads or searches
“Screen a payee before paying, trading or onboarding: one call vets an address on Base, Ethereum, Arbitrum or Optimism with an OFAC SDN match, account type and activity, USD holdings and, on Base, wal…”
Publisher declares: read-only yes · destructive no · idempotent no · open-world yes
3 inputs, 1 required
- addressstringrequired“0x address to check”
- chainstring“Network: base (default), eth, arb or op”
- domainstring“Optional: the payee's domain or website URL, e.g.”
check_x402_selleron 1 other serverreads or searches
“Audit an x402 seller before an agent buys from it: decodes the endpoint's 402 terms without paying, OFAC-screens each payTo address, reads its account type and nonce on the payment network, checks th…”
Publisher declares: read-only yes · destructive no · idempotent no · open-world yes
1 input, 1 required
- urlstringrequired“Absolute public https URL of the paid endpoint, with any query it needs”
sanctions_checkon 6 other serversreads or searches
“OFAC sanctions screen for a crypto wallet before you pay it: checks an address (BTC, ETH, USDT, TRX and more) or a person or company name against the US Treasury SDN list, aliases included.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world yes
2 inputs
- addressstring“Crypto address to check (give address, name or both)”
- namestring“Person or company name; matches when every word appears in a listed name or alias”
x402_checkon 9 other serversreads or searches
“Check an x402 seller before you pay it: decode any public endpoint's 402 payment requirements without paying (v1 body or v2 header) into USD price for native USDC, network, asset, recipient, scheme a…”
Publisher declares: read-only yes · destructive no · idempotent no · open-world yes
1 input, 1 required
- urlstringrequired“Absolute public https URL of the paid endpoint, with any query it needs”
sec_filingson 9 other serversreads or searches
“Latest SEC EDGAR filings for a US-listed company by stock ticker or CIK: form (10-K, 10-Q, 8-K, 4, S-1…), filing and report dates, accession number, document description and a direct link, newest fir…”
Publisher declares: read-only yes · destructive no · idempotent no · open-world yes
4 inputs
- tickerstring“Stock ticker such as AAPL (or give cik)”
- cikstring or number or boolean“SEC Central Index Key, e.g.”
- formstring“Only this form type, e.g.”
- limitinteger“Filings to return, 1-50 (default 10)”
emailon 3 other serversreads or searches
“Check email syntax, DNS and MX records, disposable providers, role addresses, free providers and SPF/DMARC presence.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world yes
1 input, 1 required
- addressstringrequired“The email address to check”
companyon 7 other serversreads or searches
“Facts about a company by name or Wikidata ID: official website, founding date, country, headquarters, industries, CEO, founders, parent, employee count, stock tickers and exchanges, and LEI, with Wik…”
Publisher declares: read-only yes · destructive no · idempotent no · open-world yes
2 inputs
- namestring“Company name to search for (give name or id)”
- idstring“Wikidata item ID such as Q689141, instead of name”
domainon 6 other serversreads or searches
“Domain intelligence in one call: DNS records (A, AAAA, CNAME, MX, NS, TXT, CAA), DNSSEC status, registrar, registration and expiry dates with domain age in days (RDAP/WHOIS), and email authentication…”
Publisher declares: read-only yes · destructive no · idempotent no · open-world yes
1 input, 1 required
- namestringrequired“Domain name, e.g.”
domain_reporton 8 other serversreads or searches
“A trust verdict for any domain in one call: high/medium/low trust with named flags for very new registrations, expiry, missing or weak SPF and DMARC, too few nameservers, no web host and non-resolvin…”
Publisher declares: read-only yes · destructive no · idempotent no · open-world yes
1 input, 1 required
- namestringrequired“Domain name, e.g.”
packageon 2 other serversreads or searches
“Reports package existence, latest version and release, age, version count, npm weekly downloads, licenses, deprecation and known advisory severity.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world yes
3 inputs, 2 required
- ecosystemstringrequired“One of npm, pypi, cargo, go, maven, nuget”
- namestringrequired“Exact package name, e.g.”
- versionstring“Optional exact version to inspect; ranges and tags are not accepted”
package_auditon 3 other serversreads or searches
“Check up to 10 public dependencies, optionally pinned to exact versions, for advisory IDs, OSV affected/fixed ranges and dated FIRST EPSS CVE estimates.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world yes
1 input, 1 required
- packagesstringrequired“Comma-separated ecosystem:name items, optionally name@exact-version; max 10.”

Show 3 more tools

text_prompt_injectionon 1 other serverreads or searches
“Scan text an agent is about to read (web page, email, tool result; up to 8,000 characters) for prompt-injection attempts: instruction overrides, fake system messages, asks to hide things from the use…”
Publisher declares: read-only yes · destructive no · idempotent no · open-world yes
1 input, 1 required
- textstringrequired“The text to scan (up to 8,000 characters)”
http_security_headerson 2 other serversreads or searches
“Fetch a public URL and grade its HTTP security headers: HSTS, Content-Security-Policy, framing protection, nosniff, Referrer-Policy and Permissions-Policy, plus version leaks (Server, X-Powered-By) a…”
Publisher declares: read-only yes · destructive no · idempotent no · open-world yes
1 input, 1 required
- urlstringrequired“Public http(s) URL to check”
dockerfile_linton 1 other serverreads or searches
“Check a Dockerfile (up to 8,000 characters) for common security and image-size problems: unpinned or :latest base images, running as root, piping downloads into a shell, sensitive values baked into E…”
Publisher declares: read-only yes · destructive no · idempotent no · open-world yes
1 input, 1 required
- dockerfilestringrequired“Dockerfile contents (up to 8,000 characters)”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does: 100% of 15 tools
Says what it returns: 100% of 15 tools
States limits, defaults or errors: 100% of 4 tools
Says when to use it: 100% of 15 tools
Items covered per tool: 4.0 of 4 on average

Counted from the listing

Parameters with a description: 100% of 26
Tools with a description: 100% of 15
Typical description length: 660 characters

The tool set

Counted from the listing

Tools: 15
Size of the list: about 4,924 tokens for an agent to load (characters ÷ 4)
Naming: 11 of 15 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 15 of 15 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-23 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai

Settings → Connectors → Add custom connector, then paste:
https://agent-data-tools.revmesh2074.workers.dev/mcp/compliance

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "agent-data-tools-compliance": {
      "url": "https://agent-data-tools.revmesh2074.workers.dev/mcp/compliance"
    }
  }
}

VS Code · .vscode/mcp.json

{
  "servers": {
    "agent-data-tools-compliance": {
      "type": "http",
      "url": "https://agent-data-tools.revmesh2074.workers.dev/mcp/compliance"
    }
  }
}

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"agent-data-tools-compliance","type":"http","url":"https://agent-data-tools.revmesh2074.workers.dev/mcp/compliance"}'

Claude Code

claude mcp add --transport http agent-data-tools-compliance https://agent-data-tools.revmesh2074.workers.dev/mcp/compliance

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 --server-url https://agent-data-tools.revmesh2074.workers.dev/mcp/compliance --transport http

Optional settings the entry also lists (left out above): Authorization.
The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Remote endpoint agent-data-tools.revmesh2074.workers.dev/mcp/compliance	Session opened	matches	our test · 2026-10-23
No credential declared as required	Opened a session without any credential	matches	our test · 2026-10-23
Repository github.com/Nutshell2000/agent-data-tools	Opens publicly	matches	api.github.com · 2026-10-23

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace: io.github.Nutshell2000 · 8 servers
GitHub owner: a personal account (Nutshell2000)

Repository: github.com/Nutshell2000/agent-data-tools
Stars: 0
Repository age: 0–30 days
Last push: 0–30 days ago
Archived: no
Security policy: none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)

Source: the registry entry and api.github.com · 2026-10-23; security policy read from GitHub · 2026-10-23.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

4 of 5 record checks met · 4 do not apply

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: 0 stars (ranked from 10)

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
MetSource repository link opensThe linked GitHub repository is public.
MetRepository is not archivedNot archived.
MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.
Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.github.Nutshell2000/agent-data-tools-compliance

Answered from the data above

Is io.github.Nutshell2000/agent-data-tools-compliance safe to install?

We do not rate servers as safe or unsafe. 4 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does io.github.Nutshell2000/agent-data-tools-compliance need an API key or sign-in?

It opened a session without any credential on 2026-10-23. The registry entry declares no required credential; no declaration is not a guarantee.

Has io.github.Nutshell2000/agent-data-tools-compliance been security tested?

Partly. 3 of the 15 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security verdict is published before verification.

What can io.github.Nutshell2000/agent-data-tools-compliance do?

It lists 15 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search. We did not call any tool, so this describes the text, not the behaviour.

Can io.github.Nutshell2000/agent-data-tools-compliance change or delete data?

None of its 15 tools is described as changing anything (our AI model's reading of the descriptions; nobody checked it by hand). We did not call any tool.

Does io.github.Nutshell2000/agent-data-tools-compliance publish a security policy?

We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.

Where is the source code of io.github.Nutshell2000/agent-data-tools-compliance?

In github.com/Nutshell2000/agent-data-tools, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (we call no server's tools)

We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: not run · nothing to check it against
Fake assistant turns: not applicable
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not run · our policy
Consent handling: not testable from outside
Sign-in metadata: exercised

3 exercised12 not run (reason given)3 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 3 of the 15 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 3

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.exercised

Not run, with the reason · 12

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside

Does not apply to this server · 3

13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted a read-only session with the server's remote endpoint
34 msConnected after 0 redirects. No credential was sent or needed.
Read the inventory: 15 tools, 0 resources, 0 prompts.
672 msFinished: 3 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

no value

No value: the two AI models (Gemini and Claude) disagreed, so neither answer is shown.

Pricing modelAI-classified

no value

No value: the AI answer was held back because the quoted text did not clearly support it.

Programming language

JavaScript

api.github.com · 2026-10-23

Hosting type

remote (hosted by the publisher)

registry · 2026-10-23

MCP capability

tools

our test · 2026-10-23

Transport

streamable HTTP

registry · 2026-10-23

Required credentials

none declared

registry · no declaration is not a guarantee

Package registry

does not apply

remote-only server: no package is shipped, so there is no package registry

Freshness

0–30 days

registry updatedAt · 2026-10-23

Lifecycle status

active

registry · 2026-10-23

License class

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Integrity hash

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Signature / provenance

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Dependency advisories

does not apply

ships no package, so there are no dependencies to audit

Popularity

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Publisher signals

owner: a personal account · repository age: 0–30 days · stars: 0–9

api.github.com · 2026-10-23

Maintenance

active

api.github.com · 2026-10-23

Environment

the publisher's infrastructure

where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.Nutshell2000/agent-data-tools-compliance: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.github.Nutshell2000/agent-data-tools-compliance

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.Nutshell2000/agent-data-tools-compliance)](https://protocolprobe.com/mcp/servers/io.github.Nutshell2000/agent-data-tools-compliance)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology