Doorman
REMOTE · WITHDOORMAN.COM
Spam, pitch and fraud screening for website forms. Sign up, wire forms, test and review.
Available components
Last scanned (19 hours ago)
Scores higher than 58% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Security
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability71
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1608 tokens (~134/item across 12 items; 12 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 Management60
- Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 86% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "doorman_send_test_delivery" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 16 Oct 26 +1
- A breaking change shipped without a version bump: still 0.1.0 ▼ security
- Tool “doorman_alerts” was removed ▼ security
- Tool “doorman_audit_rows” was removed ▼ security
- Tool “doorman_client_report” was removed ▼ security
- Tool “doorman_create_hook” was removed ▼ security
- Tool “doorman_create_workspace” was removed ▼ security
- Tool “doorman_delete_hook” was removed ▼ security
- Tool “doorman_hubspot_map_forms” was removed ▼ security
- Tool “doorman_hubspot_status” was removed ▼ security
- Tool “doorman_inbound_setup” was removed ▼ security
- Tool “doorman_invite” was removed ▼ security
- Tool “doorman_list_hooks” was removed ▼ security
- Tool “doorman_list_workspaces” was removed ▼ security
- Tool “doorman_update_workspace” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “doorman_get_install_snippet” rewrote its description, which is the text the model reads security
- Tool “doorman_label_submission” rewrote its description, which is the text the model reads security
- Tool “doorman_list_submissions” rewrote its description, which is the text the model reads security
- Tool “doorman_update_form” rewrote its description, which is the text the model reads security
- Tool “doorman_whoami” rewrote its description, which is the text the model reads security
- Tool coverage: 92% → 86% ▼ functional
- Schema quality: 188 → 134 ▲ functional
- Schema quality: excellent → good functional
- “doorman_signup” reworded the description of “mode” cosmetic
- “doorman_update_form” reworded the description of “mode” cosmetic
- “doorman_list_submissions” dropped the optional parameter “workspace_id” cosmetic
- “doorman_create_form” dropped the optional parameter “attachments” cosmetic
- “doorman_create_form” dropped the optional parameter “inbound_platform” cosmetic
- “doorman_create_form” dropped the optional parameter “routes” cosmetic
- “doorman_create_form” dropped the optional parameter “workspace_id” cosmetic
- “doorman_label_submission” dropped the optional parameter “always” cosmetic
- “doorman_list_forms” dropped the optional parameter “workspace_id” cosmetic
- “doorman_list_submissions” dropped the optional parameter “type” cosmetic
- “doorman_list_submissions” dropped the optional parameter “via” cosmetic
- “doorman_send_test_delivery” dropped the optional parameter “type” cosmetic
- “doorman_update_form” dropped the optional parameter “alert_delivery” cosmetic
- “doorman_update_form” dropped the optional parameter “alert_silent” cosmetic
- “doorman_update_form” dropped the optional parameter “alert_silent_days” cosmetic
- “doorman_update_form” dropped the optional parameter “alert_slack” cosmetic
- “doorman_update_form” dropped the optional parameter “alert_spike” cosmetic
- “doorman_update_form” dropped the optional parameter “attachments” cosmetic
- “doorman_update_form” dropped the optional parameter “learn” cosmetic
- “doorman_update_form” dropped the optional parameter “routes” cosmetic
- “doorman_update_form” dropped the optional parameter “welcome” cosmetic
- “doorman_update_form” dropped the optional parameter “welcome_note” cosmetic
- “doorman_update_form” dropped the optional parameter “workspace_id” cosmetic
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 40. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +1
- Schema quality: 158 → 188 ▼ functional
- 6 Oct 26 +1
- Schema quality: 133 → 158 ▼ functional
- 3 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
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 18 Oct 2026 · Probed https://withdoorman.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=withdoorman.com | CN=YE1,O=Let's Encrypt,C=US | 29 Sept 2026 | 28 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 59c5e3fadfbb802a971de725ef2eb3aa16d |
| SANs: withdoorman.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of withdoorman.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| withdoorman.com. | 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://withdoorman.com/mcp | Verified | 200 | |
| http (plaintext) | http://withdoorman.com/mcp | HTTPS enforced | 301 | https://withdoorman.com/mcp |
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 →
doorman_contact_support ~133
Stuck, or something isn't working? Send the problem straight to Doorman's founder, with the error you hit. Your account context (plan, forms, recent errors, never keys) is attached, and the reply goes to the account email. Use it instead of guessing at a fix.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Doorman API key (dm_live_...). Only needed if the MCP connection has no Authorization header. |
| category | string | – | – |
| error | string | – | The exact error text, if any |
| message | string | yes | What you were trying to do and what happened |
No output schema declared.
No examples provided.
doorman_create_form ~173
Create another form endpoint (one per distinct form on the site: contact, demo request, checkout, comments).
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Doorman API key (dm_live_...). Only needed if the MCP connection has no Authorization header. |
| email_to | string | – | Comma-separated emails to forward real submissions to |
| kind | string | – | lead = contact/demo/quote/sales form (default) |
| name | string | yes | Form name |
| redirect_url | string | – | Where to send the visitor after submitting (default: a Doorman thank-you page) |
| site_context | string | – | What the business sells and to whom |
| slack_url | string | – | Slack incoming webhook URL |
| webhook_url | string | – | HTTPS URL that receives a signed JSON POST per real submission |
No output schema declared.
No examples provided.
doorman_docs ~40
Read how Doorman works and how to integrate it (the same text as /llms.txt). Call this first if you haven't used Doorman before.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
doorman_get_install_snippet ~137
Get ready-to-paste integration code for a form on a given platform. Use 'html' for static sites, 'react' for SPA client components, and 'fetch' (plain fetch with timeout and fallback: Workers, Node, Next, Deno), 'nextjs', 'express', 'python', 'ruby' or 'elixir' when the form already posts to the project's own backend.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Doorman API key (dm_live_...). Only needed if the MCP connection has no Authorization header. |
| form_id | string | yes | f_... |
| platform | string | yes | – |
No output schema declared.
No examples provided.
doorman_label_submission ~72
Mark a submission real (delivers it if it was held or dropped) or spam.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Doorman API key (dm_live_...). Only needed if the MCP connection has no Authorization header. |
| label | string | yes | – |
| submission_id | string | yes | sub_... |
No output schema declared.
No examples provided.
doorman_list_forms ~49
List the account's forms with their action URLs and settings.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Doorman API key (dm_live_...). Only needed if the MCP connection has no Authorization header. |
No output schema declared.
No examples provided.
doorman_list_submissions ~88
Recent submissions with their verdicts. Use review=true for held ones waiting for a human.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Doorman API key (dm_live_...). Only needed if the MCP connection has no Authorization header. |
| form_id | string | – | Optional f_... |
| limit | number | – | – |
| review | boolean | – | – |
| route | string | – | – |
No output schema declared.
No examples provided.
doorman_send_test_delivery ~69
Send a sample delivery to the form's email/Slack/webhook destinations and report whether each one worked.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Doorman API key (dm_live_...). Only needed if the MCP connection has no Authorization header. |
| form_id | string | yes | f_... |
No output schema declared.
No examples provided.
doorman_signup ~271
Create a Doorman account for the user with a first form and an API key. Ask the user for their email first. They'll get an email to set a dashboard password. Creates the account's first form too and returns its id and action URL, plus the api_key (store it as DOORMAN_KEY in the project's local secrets file, never commit it). Only for new users: if they already have an account, ask for a key instead. Until the user clicks the confirmation link in that email, nothing is emailed to them (100 checks; Slack and webhooks work).
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The user's email. Real submissions are forwarded here by default. | |
| form_name | string | – | Optional name, e.g. 'Contact form' or 'Demo request' |
| mode | string | – | watch delivers would-be drops, tagged; holds still follow forward_holds. Recommended for a new lead form: switch to enforce after a week or two of verdicts look right. Default enforce. |
| site_context | string | yes | One or two sentences: what the business sells and to whom. Doorman compares every submission against this. Read the project's README/landing copy to write it. |
| site_url | string | yes | The website the form is on, e.g. acme.com |
No output schema declared.
No examples provided.
doorman_test_submission ~106
Judge a sample message against a form's settings. Free, not forwarded, not counted. Use it to show the user Doorman working after setup (try one genuine enquiry and one sales pitch).
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Doorman API key (dm_live_...). Only needed if the MCP connection has no Authorization header. |
| string | – | Optional sender email | |
| form_id | string | yes | f_... |
| message | string | yes | The message text |
No output schema declared.
No examples provided.
doorman_update_form ~252
Change a form's settings: context, destinations, thresholds, watch mode, allow/block lists.
| Name | Type | Req | Description |
|---|---|---|---|
| allow_list | array | – | Emails or domains always delivered without judging |
| api_key | string | – | Doorman API key (dm_live_...). Only needed if the MCP connection has no Authorization header. |
| block_list | array | – | Emails or domains always dropped |
| deliver_at | number | – | Deliver when P(real) >= this (default 0.8) |
| drop_below | number | – | Drop when P(real) < this (default 0.2) |
| email_to | string | – | Comma-separated emails |
| form_id | string | yes | f_... |
| forward_holds | boolean | – | Forward held submissions, flagged (default true) |
| kind | string | – | – |
| mode | string | – | watch = deliver would-be drops, tagged (a safe way to start) |
| name | string | – | Form name |
| redirect_url | string | – | Redirect after submit |
| site_context | string | – | What the business sells and to whom |
| slack_url | string | – | Slack incoming webhook URL |
| webhook_url | string | – | HTTPS webhook URL |
No output schema declared.
No examples provided.
doorman_whoami ~46
Account, plan and this month's usage.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Doorman API key (dm_live_...). Only needed if the MCP connection has no Authorization header. |
No output schema declared.
No examples provided.
How do I install the Doorman MCP server?
Doorman is a hosted endpoint at https://withdoorman.com/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 · withdoorman.com
claude mcp add --transport http com-withdoorman-doorman 'https://withdoorman.com/mcp'
What is the Doorman MCP server?
Doorman is an MCP server listed in the public MCP registry as com.withdoorman/doorman. Spam, pitch and fraud screening for website forms. Sign up, wire forms, test and review. This page covers its hosted endpoint (https://withdoorman.com/mcp).
Is the Doorman MCP server safe to use?
Doorman scores 68 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 Doorman MCP server expose?
Doorman exposes 12 tools: doorman_docs, doorman_signup, doorman_whoami, doorman_list_forms, doorman_create_form, and 7 more. Their descriptions and schemas cost roughly 1,436 tokens of context every time the server is loaded.
Does the Doorman MCP server require authentication?
No. We connected to Doorman without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Doorman MCP server still maintained?
Doorman is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.