About Witnessory
Witnessory measures post-quantum readiness for websites and tracks adoption across the internet. Developers and agents can access it through Python functions, a CLI, or an MCP server, with paid fresh checks available per request.
Key features
- 01Check a site's post-quantum readiness
- 02View adoption figures by layer
- 03Explore the probe map
- 04Check service status and pricing
- 05Verify signed results
- 06Pay per request for fresh checks
Use cases
- 01Check whether a website supports post-quantum key exchange
- 02Track internet adoption of post-quantum cryptography
- 03Read check results in Python scripts
- 04Let an agent purchase a one-off check
MCP support
Witnessory's MCP server provides tools for site checks, adoption figures, probe locations, service status, and pricing, plus llms.txt and pricing.json resources. The pay_check tool supports per-request paid checks.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
6Saved tool list · updated 2d ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| domain | string | Yes | e.g. example.org |
Details
From the project READMEWitnessory client
Witnessory measures how far the internet has moved to post-quantum cryptography. This is the client: the services as Python functions, a command line, and an MCP server so an agent can use them as tools. Standard library only; Apache 2.0.
pip install witnessory
From the command line
witnessory check example.org # one site's post-quantum readiness, in a sentence
witnessory check example.org --json # the whole signed result
witnessory headline # the observatory's headline figures, by layer
witnessory probes # where the probes measure from
witnessory status # whether every service is up
witnessory pricing # what is paid, and the prices
From Python
import witnessory
r = witnessory.check("example.org")
print(r["summary"]) # "example.org: a current browser gets post-quantum key exchange ..."
witnessory.verify(r) # {"ed25519": True, "mldsa65": True} (needs: pip install "witnessory[verify]")
witnessory.headline()["layers"]["keys"]
As an MCP server, for agents
Command witnessory, argument mcp. For example, in a client's configuration:
{"mcpServers": {"witnessory": {"command": "witnessory", "args": ["mcp"]}}}
Tools: check_site, pq_headline, probe_map, service_status, pricing. Resources: Witnessory's llms.txt and
pricing.json. Messages are JSON-RPC, one per line, on stdin and stdout.
Limits and keys
A free check is one vantage, once: 20 new checks an hour from one address, results reused for 10 minutes. A paid
plan's key (WITNESSORY_KEY, or --key) makes checks fresh and counted per month instead of per address. Every
answer carries offers: what more there is and where the prices are (https://witnessory.org/pricing.json). Watching
your own sites over time from several networks, with alerts and signed evidence, is a separate product on the same
page.
Paying per request, as an agent
No account is needed: GET https://api.witnessory.org/pay/check?domain=example.org answers 402 with what to pay
(x402 v2; USDC on Base), and any x402-capable client pays and resends. This client can pay too:
pip install "witnessory[pay]"
export WITNESSORY_PAY_KEY=0x... # a wallet holding a little USDC on Base
witnessory pay address # where to send the USDC
witnessory pay check example.org # $0.01, one fresh signed check
witnessory pay key api-developer # $19, a key for 2,000 fresh checks in 31 days -> WITNESSORY_KEY
From code: witnessory.pay.check("example.org") and witnessory.pay.buy_key("api-developer"). As an MCP tool:
pay_check. Index of what is sold: https://api.witnessory.org/pay.
Terms: https://witnessory.org/terms.html. Privacy: https://witnessory.org/privacy.html. Contact: [email protected].
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.