clearsigned-mcp
An MCP server that gives any agent a verify_claim tool: calibrated claim verification against
live web evidence, paid per call over x402 ($0.05 USDC on Base), with an Ed25519-signed receipt
the server verifies offline against Clearsigned's pinned published key before your agent sees it.
Tools
| Tool | Paid? | What it returns |
|---|---|---|
verify_claim(claim, evidence?) |
$0.05 USDC | SUPPORTED / REFUTED / UNVERIFIABLE, calibrated confidence (a measured realized rate), per-source stances, receipt id, settlement tx, signature_verified_offline |
quote() |
free | the price an unpaid request is quoted right now, decoded from the 402 |
service_status() |
free | what is serving, ledger height, published buyer counts |
UNVERIFIABLE is a real answer, not an error: the engine abstains instead of guessing. The price
never depends on the verdict; refunds exist only for failure to deliver. A request with no claim
is refused locally, before any payment.
Install
pip install clearsigned-mcp # or: pipx install clearsigned-mcp
export CLEARSIGNED_BUYER_KEY=0x… # an EVM key holding a little USDC on Base mainnet
clearsigned-mcp # stdio transport
Claude Desktop / Claude Code / any MCP client:
{
"mcpServers": {
"clearsigned": {
"command": "clearsigned-mcp",
"env": { "CLEARSIGNED_BUYER_KEY": "0x…" }
}
}
}
The key is used only to sign x402 payment authorizations from your own wallet. It is never sent to Clearsigned; the service sees the payment, not the key.
How to check us
- Pin the key at https://verify.clearsigned.com/pubkey; this server does, and refuses a receipt whose signature does not verify against it.
- Walk the public hash-chained ledger at https://verify.clearsigned.com/ledger/verify; every paid receipt and its on-chain settlement are separate events joined on payer and nonce.
- Read the live figures at https://clearsigned.com/quality (counts and timings, never a claim) and the serving calibration curve at https://clearsigned.com/stats.json.
Source of truth
This package is developed inside the Clearsigned monorepo (products/mcp-server/) and mirrored
to a public repository for registries and installs. Issues and pull requests on the mirror are
welcome; changes land in the monorepo first.
Development
python -m pytest tests/
The tests never touch the network or a wallet: the exchange is injected, and receipts are signed with a throwaway Ed25519 key to exercise the offline verification exactly as production does it.
Metadata
Release files for clearsigned-mcp 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| clearsigned_mcp-0.1.0.tar.gz | 8.6 kB | Without provenance | Details for clearsigned_mcp-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| clearsigned_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for clearsigned_mcp-0.1.0-py3-none-any.whl |
Total release size: 17.2 kB
Release files / clearsigned_mcp-0.1.0.tar.gz
| Download URL | clearsigned_mcp-0.1.0.tar.gz |
|---|---|
| Size | 8.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2fabeff9ac7fa9a968e4860339afa777ba0cef0189893ec677af21d2dd372eb1
|
|
BLAKE2b-256 checksum How to use checksums |
72f6ae12e1f210e7a974141039618a77ddf1e95aa9e2de24f48475a5f7b76725
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.14
|
Release files / clearsigned_mcp-0.1.0-py3-none-any.whl
| Download URL | clearsigned_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 8.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4af1ee800df2f8b16bf3c54ab80e39f883b567a853d6a0ca5f29f04318ba18e5
|
|
BLAKE2b-256 checksum How to use checksums |
ef69955be40d5116ad4ec8618e802217b737868751bf7daa683dcc70736993d8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.14
|
Security for clearsigned-mcp 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.