LeadShield Contact Form & B2B Solicitation Blocker
io.github.mooshee/leadshieldmoosheestreamable-httpv1.1.0Scanned
2-stage contact form spam and B2B solicitation blocker for HighLevel, WordPress, HubSpot, and web.
5 tools: 3 change things and 2 only read.
- Reads private data · 2
- Reads text others write · 2
- Can send data out · 1
- 2 findings
Anlyon alternative
3 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
5 tools
Changes things 3Claude Code: ask
leadshield_configure_spam_policyPreview (dryRun: true) or update server-side contact form spam rules for a site, including allowedCountries, allowedPhoneFormats, blockUrlsInMessage, formType preset, blockedKeywor…Reads private dataReads text others write1 finding
Why it is in this group
- The description's first verb is "preview": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
What it can reach
- private-dataThe description's first sentence says "preview" and "contact": it reads contacts.
- untrusted-inputThe description's first sentence says "preview" and "url": it reads web pages, which anyone can write.
Findings
- Warn
The server marks "leadshield_configure_spam_policy" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "preview": a word for reading.
Description, as the server wrote it Preview (dryRun: true) or update server-side contact form spam rules for a site, including allowedCountries, allowedPhoneFormats, blockUrlsInMessage, formType preset, blockedKeywords, and requiredKeywords. Example: leadshield_configure_spam_policy({"site":"pacific-coast-detailing","allowedCountries":["US","CA"],"blockUrlsInMessage":true,"dryRun":true})
Annotations the server declares
- title: Configure Site Spam Policy
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
leadshield_generate_guard_embedGenerate the 1-line zero-trust HTML script snippet, HighLevel workflow action/webhook config, WordPress plugin config, or HubSpot workflow webhook setup for any site.1 finding
Why it is in this group
- The name "leadshield_generate_guard_embed" says "generate": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "leadshield_generate_guard_embed" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "leadshield_generate_guard_embed" says "generate": a word for a change.
Description, as the server wrote it Generate the 1-line zero-trust HTML script snippet, HighLevel workflow action/webhook config, WordPress plugin config, or HubSpot workflow webhook setup for any site. Example: leadshield_generate_guard_embed({"site":"pacific-coast-detailing","platform":"highlevel"})
Annotations the server declares
- title: Generate Form Guard Embed & Webhook Config
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
leadshield_screen_submissionScreen a contact form or inbound lead message using LeadShield's 2-stage guard (Stage 0 deterministic rules at $0.00 + Stage 1 calibrated buyer-intent classification).Can send data outNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- outboundThe input takes a destination (input.phone): what the tool writes goes there.
Description, as the server wrote it Screen a contact form or inbound lead message using LeadShield's 2-stage guard (Stage 0 deterministic rules at $0.00 + Stage 1 calibrated buyer-intent classification). Returns allowed/blocked verdict, workflow branch ("deliver_to_client" or "spam_quarantine"), reason code, and buyer-intent probability. Example: leadshield_screen_submission({"site":"pacific-coast-detailing","name":"Jane Doe","email":"jane@example.com","phone":"(360) 555-0199","message":"Looking for a ceramic coating quote for my 2024 Tacoma."})
Annotations the server declares
- title: Screen Contact Form Submission
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 2Show 2 read-only tools
leadshield_get_blocked_spam_reportRetrieve quarantined contact form spam counts, Stage 0 vs Stage 1 breakdown, category counts, and recent blocked submissions for a client or site.Reads private dataNo findings
Why it is in this group
- The name "leadshield_get_blocked_spam_report" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "retrieve" and "contact": it reads contacts.
Description, as the server wrote it Retrieve quarantined contact form spam counts, Stage 0 vs Stage 1 breakdown, category counts, and recent blocked submissions for a client or site. Example: leadshield_get_blocked_spam_report({"clientSlug":"pacific-coast-detailing","days":7})
Annotations the server declares
- title: Get Blocked Form Spam Report
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
leadshield_get_spam_policyInspect the effective server-side spam guard policy for a site, including allowed countries, phone formats, URL rules, keyword lists, and active formType preset.Reads text others writeNo findings
Why it is in this group
- The name "leadshield_get_spam_policy" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "inspect" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it Inspect the effective server-side spam guard policy for a site, including allowed countries, phone formats, URL rules, keyword lists, and active formType preset. Example: leadshield_get_spam_policy({"site":"pacific-coast-detailing","formType":"quote_request"})
Annotations the server declares
- title: Inspect Site Spam Policy
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
4 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.
- Reads private data2
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__leadshield__leadshield_screen_submission"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Findings
Matches of fixed checks, with the text they matched.
The server marks "leadshield_configure_spam_policy" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "preview": a word for reading.
The server marks "leadshield_generate_guard_embed" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "leadshield_generate_guard_embed" says "generate": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http leadshield https://rankandrent-leads.hallmanlab.workers.dev/mcpclaude mcp add --transport http leadshield https://rankandrent-leads.hallmanlab.workers.dev/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__leadshield__leadshield_get_blocked_spam_report",
"mcp__leadshield__leadshield_get_spam_policy"
],
"ask": [
"mcp__leadshield__leadshield_screen_submission",
"mcp__leadshield__leadshield_configure_spam_policy",
"mcp__leadshield__leadshield_generate_guard_embed"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as leadshield. Review it before you use it.
Capability tags behind 4 rules
- mcp__leadshield__leadshield_screen_submission outbound
- mcp__leadshield__leadshield_get_blocked_spam_report private-data
- mcp__leadshield__leadshield_get_spam_policy untrusted-input
- mcp__leadshield__leadshield_configure_spam_policy private-data, untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://anlyon.dev/api/v1/servers/io.github.mooshee/leadshield/verify?hash=047ded962c62de1d82bb58f7eb1c1221fefa984b951483c74e9b8abcfb3cbd4a" | jq -e '.changed == false'Pinned hash 047ded962c62, from Oct 28, 2026, 13:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://anlyon.dev/servers/io.github.mooshee/leadshield/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://anlyon.dev/servers/io.github.mooshee/leadshield)Source: MCP Registry · repository. Synced Oct 28, 2026, 14:18 UTC.