Skip to content

LeadShield Contact Form & B2B Solicitation Blocker MCP server

io.github.mooshee/leadshieldmoosheestreamable-httpv1.1.3Scanned

Preview form screening and manage site rules. Built by Moosh Works (https://mooshworks.com).

5 tools: 1 can delete or cancel things, 2 change things and 2 only read.

Tools: 1 delete, 0 irreversible, 2 write, 2 read.
  • Reads private data · 1
  • Reads text others write · 2
  • Can send data out · 1
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the LeadShield Contact Form & B2B Solicitation Blocker MCP server can do

The LeadShield Contact Form & B2B Solicitation Blocker MCP server is published by the GitHub account mooshee. It has 5 tools. It can delete or cancel things (1 tool: leadshield_configure_spam_policy) and create or change data (2 tools: leadshield_screen_submission and leadshield_generate_guard_embed). 2 tools only read.

1 tool reads private data (leadshield_get_blocked_spam_report); 2 tools bring in text other people can write (leadshield_screen_submission and leadshield_get_blocked_spam_report); 1 tool can send data out of your system (leadshield_screen_submission). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 12, 2026, version 1.1.3.

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

Deletes or cancels 1Claude Code: deny
  • leadshield_configure_spam_policyPreview changes to a connected site's spam rules.No findings

    Why it is in this group

    • The description's first verb is "preview": a word for reading.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Preview changes to a connected site's spam rules. Set dryRun to false to save them with write access. Saved rules affect future submissions. Omitted settings are preserved. A successful save returns the policy read back from storage.

    Annotations the server declares

    • title: Configure Site Spam Policy
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
Changes things 2Claude Code: ask
  • leadshield_generate_guard_embedGenerate an HTML script snippet and setup addresses for a 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".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "leadshield_generate_guard_embed" says "generate": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Generate an HTML script snippet and setup addresses for a site. Choose HTML, HighLevel, WordPress, HubSpot, or Astro. The result is setup guidance; this tool does not install or activate the guard.

    Annotations the server declares

    • title: Generate Form Guard Embed & Webhook Config
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • leadshield_screen_submissionCheck a message against the connected site's spam rules and, when configured, its intent classifier.Reads text others writeCan 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

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a destination (input.phone): what the tool writes goes there.
    Description, as the server wrote it
    Check a message against the connected site's spam rules and, when configured, its intent classifier. Returns the screening decision and reason. This preview does not store the message, send it to a customer, or process a payment.

    Annotations the server declares

    • title: Screen Contact Form Submission
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 2Show 2 read-only tools
  • leadshield_get_blocked_spam_reportRead blocked-message counts, categories, screening stages, and recent submissions for your connected sites.Reads private dataReads text others writeNo 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 "read" and "message": it reads messages.
    • untrusted-inputThe description's first sentence says "read" and "message": it reads messages, which other people can write.
    Description, as the server wrote it
    Read blocked-message counts, categories, screening stages, and recent submissions for your connected sites. The date window uses UTC calendar days and includes today.

    Annotations the server declares

    • title: Get Blocked Form Spam Report
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • leadshield_get_spam_policyInspect the saved spam rules for a connected site, including countries, phone formats, URLs, keywords, and its form preset.No findings

    Why it is in this group

    • The name "leadshield_get_spam_policy" says "get": a word for reading.
    Description, as the server wrote it
    Inspect the saved spam rules for a connected site, including countries, phone formats, URLs, keywords, and its form preset. Supply a formType to preview that preset without changing the saved policy.

    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.

2 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 data1
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.
deny to break every path
{
  "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.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 19, 2026, 17:24 UTC, unchanged since Nov 5, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://rankandrent-leads.hallmanlab.workers.dev/.well-known/oauth-protected-resource/mcp
Authorization servers
https://rankandrent-leads.hallmanlab.workers.dev
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (1 destructive, 2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://rankandrent-leads.hallmanlab.workers.dev/mcp: tools/list returned 5 tools to an anonymous client, including leadshield_configure_spam_policy (destructive), leadshield_screen_submission (write), leadshield_generate_guard_embed (write)

    What this check looks for

Posture changes

  1. Nov 5, 2026
    • Authorization servers: none to https://rankandrent-leads.hallmanlab.workers.dev
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to no

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "leadshield_generate_guard_embed" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "leadshield_generate_guard_embed" says "generate": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Authorization servers: none -> https://rankandrent-leads.hallmanlab.workers.dev; Dynamic client registration: not observed -> yes; Client ID metadata documents: not observed -> no.View diff
    • Authorization servers: none to https://rankandrent-leads.hallmanlab.workers.dev
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to no
  2. Tools5 changed.~5 changedView diff

Install

Pinned to version 1.1.3. Values in angle brackets are yours to fill in.

claude mcp add --transport http leadshield https://rankandrent-leads.hallmanlab.workers.dev/mcp
claude mcp add --transport http leadshield https://rankandrent-leads.hallmanlab.workers.dev/mcp

Run 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.

.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_generate_guard_embed"
    ],
    "deny": [
      "mcp__leadshield__leadshield_configure_spam_policy"
    ]
  }
}

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 2 rules
  • mcp__leadshield__leadshield_screen_submission untrusted-input, outbound
  • mcp__leadshield__leadshield_get_blocked_spam_report 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://radar.anlyon.com/api/v1/servers/io.github.mooshee/leadshield/verify?hash=98211082147a88e8cbd70ab061f8fba02c425ba2ed573d9ebc15a488f6be3809" | jq -e '.changed == false'

Pinned hash 98211082147a, from Nov 12, 2026, 09:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.mooshee/leadshield/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.mooshee/leadshield
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.mooshee/leadshield.svg)](https://radar.anlyon.com/servers/io.github.mooshee/leadshield)

Source: MCP Registry · repository. Synced Oct 30, 2026, 16:17 UTC.

LeadShield Contact Form & B2B Solicitation Blocker MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the LeadShield Contact Form & B2B Solicitation Blocker MCP server safe?

No scan can promise that. What its definitions show: 5 tools, 3 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the LeadShield Contact Form & B2B Solicitation Blocker MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: leadshield_configure_spam_policy.

Can the LeadShield Contact Form & B2B Solicitation Blocker MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the LeadShield Contact Form & B2B Solicitation Blocker MCP server have?

5 tools: 1 destructive, 2 write, 2 read. leadshield_configure_spam_policy, leadshield_screen_submission, leadshield_generate_guard_embed, leadshield_get_blocked_spam_report and leadshield_get_spam_policy.

Does the LeadShield Contact Form & B2B Solicitation Blocker MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the LeadShield Contact Form & B2B Solicitation Blocker MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): leadshield_screen_submission.

Has the LeadShield Contact Form & B2B Solicitation Blocker MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Oct 30, 2026. Every change is on this page and in its Atom feed.