MCP Security Scanner: selling tools
Evidence for MCP Security Scanner: 1. Evidence pack · 2. Answers to buyer questions · 3. Figures & benchmarks · 4. Selling tools · IHVRK kit · Learn it
The evidence is your best sales tool: a buyer can check it without trusting you. Press Copy on any box, fill in the [brackets] and send it, one person at a time.
What to send, and when
| When | Send this |
|---|---|
| First message | A short personal note with the kit page |
| They reply, "show me" | The live demo on a call, using the script below |
| "Send it to our engineer" | The kit and the evidence pack |
| Security review or questionnaire | The answers page. Never upgrade a NO to a YES. |
| Finance or procurement wants records | The figures page and figures.tsv |
| Ready to go ahead | The hand-off below. The founder does the contract, price and setup. |
Who to approach
- Platform / security lead: Unvetted MCP tools.
- MCP server publisher: Customer trust.
Questions to ask them
- Which MCP servers?
- Any third-party ones?
- Who reviews them?
30-second pitch
MCP Security Scanner reads the tools an AI agent connects to and quarantines the poisoned ones before the agent sees them. We recorded 5 live checks, including 4 attack cases it had to refuse or flag, and every one matched. You can re-run them yourself without an account. Don't trust us. Check it: https://cainstudio.online/ihvrk-mcp-security-scanner.html
First email
Subject: the tool descriptions your agent obeys Hi [first name], AI agents follow the descriptions of the MCP tools they connect to, and a poisoned description can make them leak keys. We scan tools, a person reviews every flag, and you get a signed report. Live demo: https://cainstudio.online/guide-mcp-security-scanner-lab.html The evidence: We recorded 5 live checks, including 4 attack cases it had to refuse or flag, and every one matched. You can re-run them yourself without an account. Check it yourself: https://cainstudio.online/ihvrk-mcp-security-scanner.html [your name], working with FIRME AI CORPORATION [your postal address] If you'd rather not hear from me again, just say so and I won't write again.
LinkedIn connection note (under 300 characters)
Hi [name], we review MCP tool definitions for poisoning, with a person checking every flag. Happy to show a live scan.
One follow-up, three days later (then stop)
Hi [first name], demo: https://cainstudio.online/guide-mcp-security-scanner-lab.html
Live demo call script
1. Show the normal case Do: Open https://cainstudio.online/guide-mcp-security-scanner-lab.html and run: Ordinary add and send_email tools Say: Nothing suspicious: passes. 2. Now the attack Do: Run: A description that grabs the SSH key Say: Classic tool poisoning. 3. Now the attack Do: Run: A tool that changes another tool (BCC an outsider) Say: Shadowing: one tool altering another. 4. Let them check you Do: Send the kit link and ask them to run python3 verify.py --live on their own computer. Say: They don't have to take your word for any of this. That's the point. 5. Say the limit yourself Do: It is heuristic and cautious: in our own check on 2026-11-03 it quarantined a harmless 'do not reveal the puzzle solution' description. A person reviews every flag in paid work. Say: Say it before they ask. It costs nothing and it earns trust.
When they push back
Does it false-alarm?
Yes, sometimes. That's why a person reviews every flag in our paid reviews.
Does it check behaviour?
Definitions only; MCP Attestor probes behaviour.
Why should I believe your numbers?
You shouldn't have to. Run the kit on your own computer: https://cainstudio.online/ihvrk-mcp-security-scanner.html. It re-sends every request and compares the answers, using no code of ours.
What doesn't it do?
Written down here: https://cainstudio.online/guide-mcp-security-scanner-limits.html
Are you SOC 2 or ISO certified?
No, we hold no certification. What we offer instead is evidence you can check yourself.
Has anyone independent tested it?
No third-party audit has been completed. The attack cases in the kit are our own. I'd rather tell you that now.
Who else uses it?
We are an early company. I can show you the product working and the evidence, not a customer list.
It found nothing. So we're safe?
No. It means none of its checks fired. It doesn't prove something is safe.
How much is it?
Sell the scanner as the MCP / Agent Tool Review: scan plus human review plus signed report.
One-page summary (paste into a document or email)
MCP Security Scanner by FIRME AI CORPORATION, a California corporation What it does MCP Security Scanner reads the tools an AI agent connects to and quarantines the poisoned ones before the agent sees them. The evidence We recorded 5 live checks, including 4 attack cases it had to refuse or flag, and every one matched. You can re-run them yourself without an account. Recorded 2026-11-03. 5 live checks. Median round trip 50 ms including network; this is not a load test or an SLA. Check it yourself https://cainstudio.online/ihvrk-mcp-security-scanner.html Zip SHA-256: d7fcdbdb0195dee69345ac27737d7d3d4abbd662a3388ddbc927508c934a5652 Signing key fingerprint: 1cacdfc1fc2024b6bb4f8fb02c7c80f4a57f44c5adb11c507190781b5d613de3 Run: python3 verify.py --live (Python 3, no account, no code of ours) What it does not do Written down here: https://cainstudio.online/guide-mcp-security-scanner-limits.html What this is not Not a third-party audit, a certification or a guarantee. No SOC 2 or ISO certification is held. Contact [your name], working with FIRME AI CORPORATION, [your email]
After the call: the proposal email
Hi [first name], Thanks for your time. As discussed, here is what I suggest for MCP Security Scanner. What you told me: [their problem, in their words] What we'd do: Sell the scanner as the MCP / Agent Tool Review: scan plus human review plus signed report. Evidence you can check before deciding: https://cainstudio.online/ihvrk-mcp-security-scanner.html Answers for your security review: https://cainstudio.online/evidence-mcp-security-scanner-answers.html Figures for your files: https://cainstudio.online/evidence-mcp-security-scanner-figures.html Limits: Written down here: https://cainstudio.online/guide-mcp-security-scanner-limits.html Next step: [date], [who]. The founder, Vincent Noriega, handles contract and setup. [your name], working with FIRME AI CORPORATION [your postal address] If you'd rather not hear from me again, just say so and I won't write again.
Hand-off to the founder
To: vincent@firmeai.com Subject: Lead: MCP Security Scanner - [company] Company: [company] Person: [name], [job title], [email] What they said: [paste their reply] Evidence already sent: https://cainstudio.online/ihvrk-mcp-security-scanner.html Price mentioned: [what you quoted, or none] Next date: [date]
The rules
- Send each message yourself, one person at a time. No bulk lists and no automated sending.
- Commercial email needs your real name, a real postal address and a way to opt out, and you stop when someone asks (US CAN-SPAM; many countries are stricter, so check yours).
- Never change a number, invent a customer, or say certified, audited or guaranteed.
- Only test a system the client owns or operates, after they confirm it in writing.
- 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.