# LeadShield Contact Form & B2B Solicitation Blocker (remote · rankandrent-leads.hallmanlab.workers.dev)

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

- Trust score: 63/100 (medium)
- Change this week: −2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

> **Recent critical change**: Authorization (2026-10-30). See the changelog below before you install this server.

## Components

- remote · `rankandrent-leads.hallmanlab.workers.dev`: 63/100 (this document), [markdown](https://verifymcp.io/servers/mooshee-leadshield/rankandrent-leads.md), [page](https://verifymcp.io/servers/mooshee-leadshield/rankandrent-leads)

## Channel facts

- Endpoint: `https://rankandrent-leads.hallmanlab.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.3`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (leadshield_configure_spam_policy).
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 767 tokens (~153/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the LeadShield Contact Form & B2B Solicitation Blocker MCP server?

LeadShield Contact Form & B2B Solicitation Blocker is a hosted endpoint at https://rankandrent-leads.hallmanlab.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

```json
{
  "mcpServers": {
    "mooshee-leadshield": {
      "url": "https://rankandrent-leads.hallmanlab.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "mooshee-leadshield": {
      "type": "http",
      "url": "https://rankandrent-leads.hallmanlab.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.mooshee-leadshield]
url = "https://rankandrent-leads.hallmanlab.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mooshee-leadshield": {
      "type": "remote",
      "url": "https://rankandrent-leads.hallmanlab.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add mooshee-leadshield --url 'https://rankandrent-leads.hallmanlab.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  mooshee-leadshield:
    url: "https://rankandrent-leads.hallmanlab.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "mooshee-leadshield": {
      "Transport": "http",
      "Url": "https://rankandrent-leads.hallmanlab.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add mooshee-leadshield -t streamable-http -u 'https://rankandrent-leads.hallmanlab.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "mooshee-leadshield": {
      "type": "http",
      "url": "https://rankandrent-leads.hallmanlab.workers.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 60, −5)

- [critical regression] Authorization: partial → fail
- [security] Tool “leadshield_configure_spam_policy” rewrote its description, which is the text the model reads
- [security] Tool “leadshield_generate_guard_embed” rewrote its description, which is the text the model reads
- [security] Tool “leadshield_get_blocked_spam_report” rewrote its description, which is the text the model reads
- [security] Tool “leadshield_get_spam_policy” rewrote its description, which is the text the model reads
- [security] Tool “leadshield_screen_submission” rewrote its description, which is the text the model reads
- [security] Tool “leadshield_configure_spam_policy” is now declared destructive
- [functional improvement] Schema quality: 182 → 153
- [functional] Server version: 1.1.0 → 1.2.0
- [cosmetic] “leadshield_configure_spam_policy” reworded the description of “allowedPhoneFormats”
- [cosmetic] “leadshield_configure_spam_policy” reworded the description of “blockedKeywords”
- [cosmetic] “leadshield_configure_spam_policy” reworded the description of “dryRun”
- [cosmetic] “leadshield_configure_spam_policy” reworded the description of “requiredKeywords”
- [cosmetic] “leadshield_generate_guard_embed” reworded the description of “site”
- [cosmetic] “leadshield_get_blocked_spam_report” reworded the description of “clientSlug”
- [cosmetic] “leadshield_get_spam_policy” reworded the description of “site”
- [cosmetic] “leadshield_screen_submission” reworded the description of “site”
- [cosmetic] Tool “leadshield_configure_spam_policy” changed its title: Configure or Preview Server-Side Site Spam Policy → Preview or Save Site Screening Rules
- [cosmetic] Tool “leadshield_generate_guard_embed” changed its title: Generate Zero-Trust Form Guard Embed Snippet or CRM Webhook Config → Generate a form guard setup snippet
- [cosmetic] Tool “leadshield_screen_submission” changed its title: Screen Contact Form Submission for Spam & B2B Solicitation → Screen a contact form message

### 2026-10-29 (score 65, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-28 (score 65)

First indexed and scored.

## MCP tools (5)

### `leadshield_screen_submission` (~190 tokens)

Screen a contact form message

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.

Input parameters:

- `country` (string): Two-letter ISO 3166-1 alpha-2 country code (e.g. 'US', 'CA').
- `email` (string): Submitter email address.
- `formType` (string): Optional form-type preset to evaluate against.
- `message` (string, required): Inbound form message or inquiry text to evaluate.
- `name` (string): Submitter full name.
- `phone` (string): Submitter phone number.
- `site` (string, required): A site connected to your LeadShield account, such as 'review-demo'.
- `timezone` (string): Submitter IANA timezone (e.g. 'America/Los_Angeles').

### `leadshield_get_blocked_spam_report` (~114 tokens)

Get Blocked Contact Form Spam Report & Metrics

Read blocked-message counts, categories, screening stages, and recent submissions for your connected sites. The date window uses UTC calendar days and includes today.

Input parameters:

- `clientSlug` (string): A connected site to report on. Omit to combine only the sites connected to your account.
- `days` (integer): Lookback window in days (1 to 90, default 7).
- `limit` (integer): Maximum number of recent blocked records to include (1 to 50, default 10).

### `leadshield_get_spam_policy` (~80 tokens)

Inspect Site Contact Form Spam Policy & Form-Type Presets

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.

Input parameters:

- `formType` (string): Optional formType preset to preview.
- `site` (string, required): A site connected to your LeadShield account.

### `leadshield_configure_spam_policy` (~286 tokens)

Preview or Save Site Screening Rules

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.

Input parameters:

- `allowedCountries` (array): Allowed ISO 3166-1 alpha-2 country codes (e.g. ['US', 'CA']).
- `allowedPhoneFormats` (array): Accept a phone number when it matches any listed format. Supported formats: us-nanp, uk, au, eu, international, e164, any. US_NANP and E164 are accepted aliases. An empty list restores the single-for…
- `blockUrlsInMessage` (boolean): Whether to block URLs and HTML anchor tags in messages.
- `blockedKeywords` (array): Keywords or phrases that block a submission, matched without regard to case.
- `dryRun` (boolean): Defaults to true. Set to false with account write access to save changes.
- `formType` (string): Default form-type preset for this site.
- `maxUrls` (integer): Maximum allowed URLs when blockUrlsInMessage is false.
- `requiredKeywords` (array): At least one listed phrase must appear in the message, matched without regard to case. An empty list disables this rule.
- `site` (string, required): Target site or client slug.

### `leadshield_generate_guard_embed` (~97 tokens)

Generate a form guard setup snippet

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.

Input parameters:

- `formType` (string): Optional formType preset attribute.
- `platform` (string): Target website or CRM platform.
- `site` (string, required): Your site's LeadShield identifier, such as 'review-demo'.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/mooshee-leadshield/rankandrent-leads#diagnostics

## Score history

- 2026-11-05: 63
- 2026-11-04: 62
- 2026-11-03: 62
- 2026-11-02: 61
- 2026-11-01: 61
- 2026-10-31: 60
- 2026-10-30: 60
- 2026-10-29: 65
- 2026-10-28: 65

## Common questions

### What is the LeadShield Contact Form & B2B Solicitation Blocker MCP server?

LeadShield Contact Form & B2B Solicitation Blocker is an MCP server listed in the public MCP registry as io.github.mooshee/leadshield. Preview form screening and manage site rules. Built by Moosh Works (https://mooshworks.com). This page covers its hosted endpoint (https://rankandrent-leads.hallmanlab.workers.dev/mcp).

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

LeadShield Contact Form & B2B Solicitation Blocker scores 63 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

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

LeadShield Contact Form & B2B Solicitation Blocker exposes 5 tools: leadshield_screen_submission, leadshield_get_blocked_spam_report, leadshield_get_spam_policy, leadshield_configure_spam_policy, leadshield_generate_guard_embed. Their descriptions and schemas cost roughly 767 tokens of context every time the server is loaded.

### Does the LeadShield Contact Form & B2B Solicitation Blocker MCP server require authentication?

No. We connected to LeadShield Contact Form & B2B Solicitation Blocker without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the LeadShield Contact Form & B2B Solicitation Blocker MCP server still maintained?

LeadShield Contact Form & B2B Solicitation Blocker is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://rankandrent-leads.hallmanlab.workers.dev/mcp
- Repository: https://github.com/mooshee/leadshield-mcp
- Website: https://ghlagencymcp.com/use-cases/ghl-contact-form-spam-blocker
- Changelog RSS feed: https://verifymcp.io/servers/mooshee-leadshield/rankandrent-leads.xml
- Changelog JSON feed: https://verifymcp.io/servers/mooshee-leadshield/rankandrent-leads.json
- HTML version of this page: https://verifymcp.io/servers/mooshee-leadshield/rankandrent-leads