Learn MCP Attestor: from zero to expert, then sell it
No AI background needed. Five levels, each with something to actually do, at your own pace. Tick items as you go (your ticks stay in this browser).
Evidence, proof and selling tools for MCP Attestor
Level 1 Beginner: understand it
Scan the description, then probe the behaviour, then sign the result.
Think of it like this: A car inspection that reads the paperwork and then actually test-drives the car.
Read the full plain-English explanation: MCP Attestor, explained.
Level 2 User: see it work
Run it live: open the live demo. Before each result, guess what will happen. These are checks it must pass:
- A calculator that really adds: Clean.
- A description with a hidden instruction: Prompt injection in the description.
- A command parameter that exposes a secret: Unconstrained parameter.
- A 'search' that ignores the query (scan only): The scan alone cannot see this: its description is fine. That is why the probe below exists.
- Probe the canned search, then prove the fix: Behaviour tests fail on the canned tool (same answer for different queries) and pass on the fixed one.
Level 3 Verifier: prove it yourself
This is the skill that sets you apart: you don't have to believe us, and neither do your customers.
- Install Python 3 if you don't have it (python.org/downloads).
- Download the kit and unzip it.
- Open a terminal in that folder. On Windows, click the folder's address bar, type
cmdand press Enter. On a Mac, right-click the folder and choose New Terminal at Folder. - Run
python3 verify.py(on Windows,python verify.py). It checks the seal without the internet. - Run
python3 verify.py --live. It repeats every check from your own computer. - Try to cheat it: open
transcript.jsonin a text editor, change one character, save, and runpython3 verify.pyagain. It must now say FAIL. Unzip a fresh copy afterward.
Level 4 Expert: know the edges
An expert knows what a product does not do, and says it first. That is what makes a buyer trust you.
- The public demo uses four sample tools; your own tools are attested in an engagement.
- The static scan is heuristic; the probe proves only what its tests check.
You can say
- Behaviour is tested in a sandbox.
- Fixes must pass the same tests.
Never say
- "Proves a tool is safe in every way".
Read the questions real buyers send, with honest answers: answers to buyer questions.
Test yourself (click a question to see the answer)
Can a description scan catch a canned search?
No; the probe can.
How many probes per hour on the demo?
3 per visitor.
In the live check "A description with a hidden instruction", what answer must come back, and why?
"STUB". Prompt injection in the description.
In the live check "A command parameter that exposes a secret", what answer must come back, and why?
"PARTIAL". Unconstrained parameter.
In the live check "Probe the canned search, then prove the fix", what answer must come back, and why?
"VERIFIED_ATTESTATION". Behaviour tests fail on the canned tool (same answer for different queries) and pass on the fixed one.
Does a passing kit prove the product is safe for every possible input?
No. It proves what the live product answered to the inputs listed in the kit, and lets anyone check that again.
Has an independent party audited or certified this product?
No. No third-party audit is complete and no certification is held. Say so if asked.
Want a formal study path? The CAIN Academy has courses and exams. Finishing this page is your own practice; it is not a qualification or certification.
Level 5 Seller: put it in front of a customer
- Copy, paste, send: the shortest route, no technical skill needed.
- Who buys it and where to find them.
- The sales conversation, then the offer and the close.
- The rules: read these before your first message.
- Selling tools with this product's evidence built in: pitch, emails, call script, objection answers, one-pager.
About money: your share is agreed in writing with FIRME AI CORPORATION before your first message (email vincent@firmeai.com). Nothing here promises income. Most messages get no reply; that is normal.