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).
Available components
Last scanned (9 hours ago)
Scores higher than 44% of remote servers
Reachable. Last reached 5 Nov 2026.
Category CRM and Sales
Recent critical change
Authorization (30 Oct 2026). See the changelog before you install this server.
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. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (leadshield_configure_spam_policy). See how to fix → View diagnostics → Fail
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +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.
- 3 Nov 26 +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.
- 1 Nov 26 +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.
- 30 Oct 26 −5
- Authorization: partial → fail ▼ critical
- 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 security
- Schema quality: 182 → 153 ▲ functional
- Server version: 1.1.0 → 1.2.0 functional
- “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 cosmetic
- 29 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 28 Oct 26 65
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://rankandrent-leads.hallmanlab.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=hallmanlab.workers.dev | CN=WE1,O=Google Trust Services,C=US | 5 Oct 2026 | 3 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | dc2b1d7b93fc8ba21363455ac37d9738 |
| SANs: hallmanlab.workers.dev, *.hallmanlab.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of rankandrent-leads.hallmanlab.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://rankandrent-leads.hallmanlab.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://rankandrent-leads.hallmanlab.workers.dev/mcp | Served over HTTP | 200 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
leadshield_configure_spam_policy Preview or Save Site Screening Rules ~286
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Target site or client slug. |
No output schema declared.
No examples provided.
leadshield_generate_guard_embed Generate a form guard setup snippet ~97
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.
| Name | Type | Req | Description |
|---|---|---|---|
| formType | string | – | Optional formType preset attribute. |
| platform | string | – | Target website or CRM platform. |
| site | string | yes | Your site's LeadShield identifier, such as 'review-demo'. |
No output schema declared.
No examples provided.
leadshield_get_blocked_spam_report Get Blocked Contact Form Spam Report & Metrics ~114
Read blocked-message counts, categories, screening stages, and recent submissions for your connected sites. The date window uses UTC calendar days and includes today.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
leadshield_get_spam_policy Inspect Site Contact Form Spam Policy & Form-Type Presets ~80
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.
| Name | Type | Req | Description |
|---|---|---|---|
| formType | string | – | Optional formType preset to preview. |
| site | string | yes | A site connected to your LeadShield account. |
No output schema declared.
No examples provided.
leadshield_screen_submission Screen a contact form message ~190
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.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Two-letter ISO 3166-1 alpha-2 country code (e.g. 'US', 'CA'). |
| string | – | Submitter email address. | |
| formType | string | – | Optional form-type preset to evaluate against. |
| message | string | yes | Inbound form message or inquiry text to evaluate. |
| name | string | – | Submitter full name. |
| phone | string | – | Submitter phone number. |
| site | string | yes | A site connected to your LeadShield account, such as 'review-demo'. |
| timezone | string | – | Submitter IANA timezone (e.g. 'America/Los_Angeles'). |
No output schema declared.
No examples provided.
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.
remote · rankandrent-leads.hallmanlab.workers.dev
claude mcp add --transport http mooshee-leadshield 'https://rankandrent-leads.hallmanlab.workers.dev/mcp'
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.