Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

DealMachine

REMOTE · MCP.DEALMACHINE.COM

Find US property owners, including LLCs, plus owner phones and emails. Needs a DealMachine account.

+2 this week 86 Trust /100

Last scanned (16 hours ago)

Scores higher than 88% of remote servers

Reachable. Last reached 21 Nov 2026.

Category CRM and Sales

Trust breakdown (7 categories)

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 Security91
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
  • 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
  • The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
Schema Quality & AI Usability65
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 14737 tokens (~113/item across 130 items; 130 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 Management82
  • Stability check failed: schema churn in the 30 days we've observed: 8 tool removals, 0 breaking changes, 0 auth/transport breaks, 92 additions. See how to fix → Fail
Tool Coverage84
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 53% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 14 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 131 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 76 to 79.

  • 18 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “dealmachine_enrich_address” rewrote its description, which is the text the model reads security
    • Tool “dealmachine_enrich_apn” rewrote its description, which is the text the model reads security
    • Tool “dealmachine_enrich_latlng” rewrote its description, which is the text the model reads security
    • Tool “dealmachine_get_mail_designs_id” rewrote its description, which is the text the model reads security
    • Tool “dealmachine_patch_mail_designs_id” rewrote its description, which is the text the model reads security
    • Tool “dealmachine_people_search” rewrote its description, which is the text the model reads security
    • Tool “dealmachine_post_lists_list_id_export” rewrote its description, which is the text the model reads security
    • Tool “dealmachine_post_mail_designs” rewrote its description, which is the text the model reads security
    • Tool “dealmachine_property_count” rewrote its description, which is the text the model reads security
    • Tool “dealmachine_property_export” rewrote its description, which is the text the model reads security
    • Tool “dealmachine_property_search” rewrote its description, which is the text the model reads security
    • Schema quality: pass → fail ▼ functional
    • New tool “dealmachine_mail_settings_update” functional
    • “dealmachine_enrich_address” added an optional parameter “anchor” cosmetic
    • “dealmachine_enrich_address” added an optional parameter “require_phone” cosmetic
    • “dealmachine_enrich_apn” added an optional parameter “anchor” cosmetic
    • “dealmachine_enrich_apn” added an optional parameter “require_phone” cosmetic
    • “dealmachine_enrich_latlng” added an optional parameter “anchor” cosmetic
    • “dealmachine_enrich_latlng” added an optional parameter “require_phone” cosmetic
    • “dealmachine_people_count” added an optional parameter “active_phones_only” cosmetic
    • “dealmachine_people_count” added an optional parameter “exclude_lists” cosmetic
    • “dealmachine_people_count” added an optional parameter “include_lists” cosmetic
    • “dealmachine_people_count” added an optional parameter “landline_only” cosmetic
    • “dealmachine_people_count” added an optional parameter “mobile_only” cosmetic
    • “dealmachine_people_count” added an optional parameter “require_email” cosmetic
    • “dealmachine_people_count” added an optional parameter “require_phone” cosmetic
    • “dealmachine_people_count” added an optional parameter “scrub_dnc” cosmetic
    • “dealmachine_people_search” added an optional parameter “exclude_lists” cosmetic
    • “dealmachine_people_search” added an optional parameter “include_lists” cosmetic
    • “dealmachine_property_count” added an optional parameter “active_phones_only” cosmetic
    • “dealmachine_property_count” added an optional parameter “exclude_lists” cosmetic
    • “dealmachine_property_count” added an optional parameter “include_lists” cosmetic
    • “dealmachine_property_count” added an optional parameter “landline_only” cosmetic
    • “dealmachine_property_count” added an optional parameter “mobile_only” cosmetic
    • “dealmachine_property_count” added an optional parameter “require_email” cosmetic
    • “dealmachine_property_count” added an optional parameter “scrub_dnc” cosmetic
    • “dealmachine_property_export” added an optional parameter “estimate_cost” cosmetic
    • “dealmachine_property_export” added an optional parameter “exclude_lists” cosmetic
    • “dealmachine_property_export” added an optional parameter “include_lists” cosmetic
    • “dealmachine_property_search” added an optional parameter “exclude_lists” cosmetic
    • “dealmachine_property_search” added an optional parameter “include_lists” cosmetic
    • “dealmachine_prospect_search” added an optional parameter “exclude_tag_ids” cosmetic
    • “dealmachine_prospect_search” added an optional parameter “include_tag_ids” cosmetic
    • “dealmachine_people_count” made “locations” optional cosmetic
    • “dealmachine_people_search” made “locations” optional cosmetic
    • “dealmachine_property_count” made “locations” optional cosmetic
    • “dealmachine_property_export” made “locations” optional cosmetic
    • “dealmachine_property_search” made “locations” optional cosmetic
  • 16 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 62 to 66.

  • 14 Nov 26 +2
    • DNSSEC: fail → pass ▲ security
  • 12 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 49 to 52.

  • 10 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 42 to 46.

  • 7 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 32 to 36.

  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

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 21 Nov 2026 · Probed https://mcp.dealmachine.com

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=dealmachine.com CN=WE1,O=Google Trust Services,C=US 3 Oct 2026 1 Jan 2027 ECDSA 256 ECDSA-SHA256 ff510c57aef6be050e06b74cab7da350
SANs: dealmachine.com, mcp.dealmachine.com, *.mcp.dealmachine.com
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 secure

Validation of mcp.dealmachine.com. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
dealmachine.com. DS published 2371 13 Verified
mcp.dealmachine.com. Verified address RRset verified with the apex keys
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer realm="dealmachine", resource_metadata="https://mcp.dealmachine.com/.well-known/oauth-protected-resource", scope="account:read"

Bearer realm="dealmachine", resource_metadata="https://mcp.dealmachine.com/.well-known/oauth-protected-resource", scope="account:read"

Protected resource metadata

Document https://mcp.dealmachine.com/.well-known/oauth-protected-resource
Retrieved Yes
Resource https://mcp.dealmachine.com
Authorisation server https://dealmachine.com

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.dealmachine.com Verified 200
http (plaintext) http://mcp.dealmachine.com HTTPS enforced 301 https://mcp.dealmachine.com/
MCP tools · 130 exposed · ~14,350 tokens

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 →

Tool Tokens
dealmachine_post_people_export ~119

Export people to CSV. Export matching people as a CSV file. Returns signed download URLs. Limited to 1,000,000 records per export. Pass limit to export only the first N matching records. The request is synchronous — the response is returned once the export is complete (typically up to 30 seconds). Requires user approval and confirmed=true before changes or credit use. Writes are never retried automatically.

NameTypeReqDescription
bodyobjectyes–
confirmedboolean–Set true only after the user approves this change or credit use.

No output schema declared.

No examples provided.

dealmachine_post_phones_dnc ~97

Check DNC status. Check Do Not Call (DNC) registry status and phone type for an array of phone numbers. Returns DNC status and phone type without performing a full person enrichment. Requires user approval and confirmed=true before changes or credit use. Writes are never retried automatically.

NameTypeReqDescription
bodyobjectyes–
confirmedboolean–Set true only after the user approves this change or credit use.

No output schema declared.

No examples provided.

dealmachine_post_prospects_check ~83

Check prospect state. For up to 500 record IDs, say which are prospects and where they are. Use it to avoid duplicate adds. Retrieves data without changing records or spending credits. Requires confirmed=true for this request.

NameTypeReqDescription
bodyobject––
confirmedboolean–Set true only after the user approves this change or credit use.

No output schema declared.

No examples provided.

dealmachine_post_prospects_id_files ~85

Register uploaded file. Step two: after the PUT succeeds, record the file on the prospect. Requires user approval and confirmed=true before changes or credit use. Writes are never retried automatically.

NameTypeReqDescription
bodyobject––
confirmedboolean–Set true only after the user approves this change or credit use.
pathobjectyes–

No output schema declared.

No examples provided.

dealmachine_post_prospects_id_files_upload_url ~117

Get file upload URL. Step one of attaching a file: returns a presigned URL to PUT the bytes to (valid 5 minutes, max 25 MB) and the `s3_key` to register afterwards with `POST /files`. Requires user approval and confirmed=true before changes or credit use. Writes are never retried automatically.

NameTypeReqDescription
bodyobject––
confirmedboolean–Set true only after the user approves this change or credit use.
pathobjectyes–

No output schema declared.

No examples provided.

dealmachine_post_prospects_id_photos ~107

Add prospect photo. Attach a photo to the prospect’s property from base64 (small images) or a public https URL (up to 10 MB). Needs an API key created by a user. Requires user approval and confirmed=true before changes or credit use. Writes are never retried automatically.

NameTypeReqDescription
bodyobject––
confirmedboolean–Set true only after the user approves this change or credit use.
pathobjectyes–

No output schema declared.

No examples provided.

dealmachine_post_prospects_id_tags_tag_id ~67

Add tag to prospect. Requires user approval and confirmed=true before changes or credit use. Writes are never retried automatically.

NameTypeReqDescription
confirmedboolean–Set true only after the user approves this change or credit use.
pathobjectyes–

No output schema declared.

No examples provided.

dealmachine_post_tags ~86

Create tag. Add a workspace tag. Names are unique per workspace and cannot reuse a built-in tag’s name. Up to 200 tags per workspace. Requires user approval and confirmed=true before changes or credit use. Writes are never retried automatically.

NameTypeReqDescription
bodyobject––
confirmedboolean–Set true only after the user approves this change or credit use.

No output schema declared.

No examples provided.

dealmachine_post_tags_reorder ~80

Reorder tags. Set the display order of workspace tags. IDs not listed keep their order after the listed ones. Requires user approval and confirmed=true before changes or credit use. Writes are never retried automatically.

NameTypeReqDescription
bodyobject––
confirmedboolean–Set true only after the user approves this change or credit use.

No output schema declared.

No examples provided.

dealmachine_post_tasks ~76

Create task. Create a new task. Optionally link it to an opportunity, property, or person. Requires user approval and confirmed=true before changes or credit use. Writes are never retried automatically.

NameTypeReqDescription
bodyobject––
confirmedboolean–Set true only after the user approves this change or credit use.

No output schema declared.

No examples provided.

dealmachine_post_webhooks_id_deliveries_delivery_id_redeliver ~104

Redeliver. Queue one delivery to be sent again. Pass `delivery_id=all` with `since` to requeue every delivery after a time. Requires user approval and confirmed=true before changes or credit use. Writes are never retried automatically.

NameTypeReqDescription
confirmedboolean–Set true only after the user approves this change or credit use.
pathobjectyes–
queryobject––

No output schema declared.

No examples provided.

dealmachine_post_webhooks_id_rotate_secret ~86

Rotate webhook secret. Issue a new signing secret. The old one keeps validating signatures for 24 hours so your consumer can switch over. Requires user approval and confirmed=true before changes or credit use. Writes are never retried automatically.

NameTypeReqDescription
confirmedboolean–Set true only after the user approves this change or credit use.
pathobjectyes–

No output schema declared.

No examples provided.

dealmachine_post_webhooks_id_test ~86

Send test event. Sends one `ping` event to the URL right now, signed like a real delivery, and returns what came back. Requires user approval and confirmed=true before changes or credit use. Writes are never retried automatically.

NameTypeReqDescription
confirmedboolean–Set true only after the user approves this change or credit use.
pathobjectyes–

No output schema declared.

No examples provided.

dealmachine_property_count ~268

Counts properties matching locations and filters (provide locations, filters, include_lists or exclude_lists), such as is_corporate_owned for corporation, LLC or business owners, or with anchor=people their matching contacts. Use the same anchor, contact_audience and require_phone as the search. Needs a connected DealMachine account; counting consumes no credits.

NameTypeReqDescription
active_phones_onlyboolean–Count only contacts with an active reported phone number
anchorstring––
contact_audiencestring–Required for anchor=people; cannot be none
exclude_listsobject–Remove records in any excluded list, including records in included lists.
filtersarray––
include_listsobject–Return records in any included list. Can be combined with exclude_lists.
landline_onlyboolean–Count only contacts with a landline phone number
locationsarray––
mobile_onlyboolean–Count only contacts with a wireless phone number
require_emailboolean–Count only contacts with an email address
require_phoneboolean–With anchor=people, count only contacts with a phone
scrub_dncboolean–Count only contacts with a phone not on the Do Not Call registry

No output schema declared.

No examples provided.

dealmachine_property_export ~390

Creates a downloadable CSV of properties or property-owner contacts matching locations and filters. Defaults to owner contact rows (`contact_audience=owners`, `anchor=person`) with names, phones, emails, and property addresses. `contact_audience=none` or `anchor=property` produces property rows without contacts. `estimate_cost=true` returns the row count and the credits this export would charge, net of records already billed this billing cycle, without creating a file or spending credits; quote with the same inputs before exporting. In the quote, `credits.estimated` is the charge; `credits.properties` and `credits.people` count records before repeats are subtracted. Exported records can consume credits.

NameTypeReqDescription
active_phones_onlyboolean–Only include phone numbers with active reported phone activity
anchorstring–default: person for property-owner contact rows
contact_audiencestring–default: owners; "none" creates a property-only export
estimate_costboolean–Return the row count and credit quote without creating a file or spending credits
exclude_listsobject–Remove records in any excluded list, including records in included lists.
fieldsarray–Additional fields to include. Omit for the owner-contact default fields.
filtersarray––
include_listsobject–Return records in any included list. Can be combined with exclude_lists.
landline_onlyboolean–Only include landline phone numbers
limitinteger–Maximum records to export
locationsarray––
mobile_onlyboolean–Only include wireless phone numbers
require_emailboolean–Only include contacts with an email address
require_phoneboolean–Only include contacts with a phone number
scrub_dncboolean–Exclude contacts on the Do Not Call registry

No output schema declared.

No examples provided.

dealmachine_property_get ~138

Returns one property by DealMachine property ID (id, required), with its owners and their names, phones and emails by default. `contact_audience=none` returns property-only data. Needs a connected DealMachine account with paid access. Enriched data costs one property credit unless `enrich=false`; owner contacts cost people credits.

NameTypeReqDescription
contact_audiencestring–default: owners; use none for property-only data with zero people credits
enrichboolean–false = base fields only, 0 credits
fieldsarray–DealMachine property field IDs
idstringyesprop_XXXXX

No output schema declared.

No examples provided.

dealmachine_property_get_many ~111

Returns up to 25 properties by DealMachine property ID (ids, required), with their owners and their names, phones and emails by default. `contact_audience=none` returns property-only data. Needs a connected DealMachine account with paid access. Owner contacts cost people credits; same-cycle repeats are free.

NameTypeReqDescription
contact_audiencestring–default: owners; use none for property-only data with zero people credits
enrichboolean––
idsarrayyes–

No output schema declared.

No examples provided.

dealmachine_property_search ~287

Finds US properties matching locations and filters (provide locations, filters, include_lists or exclude_lists) from the filter list, such as is_corporate_owned for properties owned by a corporation, LLC or business. Returns the properties with their owner contacts (names, phones and emails) by default, or with anchor=people one result per contact. contact_audience selects whose contacts and `none` leaves them out; require_phone keeps contacts with a phone. `estimate_cost=true` returns a credit estimate without records or credit use. Needs a connected DealMachine account with paid access. Returned property data and contacts can consume credits.

NameTypeReqDescription
anchorstring–Default properties; people returns contacts of matching properties
contact_audiencestring–default: owners; "none" skips contacts
estimate_costboolean–true = preview cost, no data returned
exclude_listsobject–Remove records in any excluded list, including records in included lists.
fieldsarray––
filtersarray––
include_listsobject–Return records in any included list. Can be combined with exclude_lists.
locationsarray––
pageinteger––
per_pageinteger––
require_phoneboolean–With anchor=people, only contacts with a phone
sortarray––

No output schema declared.

No examples provided.

dealmachine_prospect_add ~108

Tracks one record or up to 1,000 records as prospects in the workspace. Records that are prospects already are returned unchanged; archived ones come back to active. Free; no credits are charged.

NameTypeReqDescription
favoriteboolean–Also star them for the connected user
record_idsarrayyesRecord IDs such as `prop_12345` or `person_777`, or bare numbers
record_typestring–What kind of record. Defaults to property.

No output schema declared.

No examples provided.

dealmachine_prospect_get ~116

Returns one prospect by prospect ID, or by the record it tracks, with its lifecycle, status (Hot, Warm, Cold, Follow up, Do Not Contact; read only), tags, and note and file counts. Free.

NameTypeReqDescription
prospect_idstring–Prospect ID such as `prospect_8812`
record_idstring–Record ID such as `prop_12345`, used when prospect_id is not known
record_typestring–What kind of record. Defaults to property.

No output schema declared.

No examples provided.

dealmachine_prospect_note_add ~58

Adds a note (up to 10,000 characters) to a prospect. Free.

NameTypeReqDescription
bodystringyesThe note text
prospect_idstringyesProspect ID such as `prospect_8812`

No output schema declared.

No examples provided.

dealmachine_prospect_search ~366

Lists the workspace prospects by lifecycle and source, optionally scoped to a list or a tag, starred only, matching address or name words, by status, by who added them, or by when they were added. Paged, up to 100 per page. Free.

NameTypeReqDescription
added_afterstring–Only prospects added on or after this ISO 8601 date or date-time. A date such as 2026-10-01 means midnight UTC
added_beforestring–Only prospects added before this ISO 8601 date or date-time (not including it). A date means midnight UTC
added_byarray–Only prospects added by these user IDs, such as [7, 12]
exclude_tag_idsarray–Remove prospects with any excluded tag, even if they match the included tags.
favorites_onlyboolean––
include_tag_idsarray–Match any included tag; applied together with exclude_tag_ids.
lifecyclestring–Defaults to active
list_idstring–Only members of this list
pageinteger––
per_pageinteger––
record_typestring–Defaults to property
searchstring–Address words for properties; name or city words for people
sortstring––
sourcestring–How the prospect was added. Use driving for prospects added during drives.
source_groupstring–d4d for prospects added while driving; map for prospects added any other way
statusarray–Only prospects with any of these statuses; none means no status set
tag_idstring–Only prospects with this tag, such as `tag_31`

No output schema declared.

No examples provided.

dealmachine_prospect_tags_set ~68

Replaces the tags on a prospect with exactly the given tag IDs; an empty list clears them. Free.

NameTypeReqDescription
prospect_idstringyesProspect ID such as `prospect_8812`
tag_idsarrayyesTag IDs such as `tag_31`

No output schema declared.

No examples provided.

dealmachine_prospect_update ~113

Moves a prospect between active, opportunity, and archived, or stars it. Archiving ends its mail. With cascade enabled, it also closes open opportunities. List memberships are kept either way. Free.

NameTypeReqDescription
cascadeboolean–When archiving, close open opportunities. Mail ending is unaffected and list memberships are kept either way. Defaults to true
favoriteboolean––
lifecyclestring––
prospect_idstringyesProspect ID such as `prospect_8812`

No output schema declared.

No examples provided.

dealmachine_signup ~56

Start a free DealMachine account. Returns the secure browser signup URL. Ask the user to finish signup and connect DealMachine using OAuth. Never ask for passwords, payment details or API keys in chat. Signup does not purchase a plan.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

dealmachine_tags_list ~50

Lists the prospect tag catalog: the built-in tags every workspace has plus the workspace’s own, with how many prospects carry each. Free.

NameTypeReqDescription
include_inactiveboolean–Include archived tags

No output schema declared.

No examples provided.

dealmachine_usage ~46

Returns live credit usage for the current billing cycle, including the total cap, spendable balance, monthly and additional pools, and usage by entity type. This read-only request is free.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

dealmachine_webhook_create ~115

Registers an https URL to receive prospect and list events. Returns the signing secret once; relay it to the user. Free.

NameTypeReqDescription
batch_maxinteger–Most events per request. Default 50
descriptionstring––
event_typesarrayyesEvent types such as `prospect.added`, `prospect.*`, or `*`
include_contactsboolean–Include phone numbers and emails on person prospects
urlstringyesPublic https URL that accepts POST requests

No output schema declared.

No examples provided.

dealmachine_webhook_list ~53

Lists the workspace’s outbound webhooks with their event types and delivery health, plus the catalog of event types when asked. Free.

NameTypeReqDescription
include_eventsboolean–Also return the event catalog with example bodies

No output schema declared.

No examples provided.

dealmachine_whoami ~36

Returns whether the current credential is valid, the active organization name, and the authentication type. This read-only request is free.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the DealMachine MCP server?

DealMachine is a hosted endpoint at https://mcp.dealmachine.com/, 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 · mcp.dealmachine.com

# add to Claude Code
claude mcp add --transport http dealmachine-dealmachine 'https://mcp.dealmachine.com/'
Common questions

What is the DealMachine MCP server?

DealMachine is an MCP server listed in the public MCP registry as io.github.DealMachine/dealmachine. Find US property owners, including LLCs, plus owner phones and emails. Needs a DealMachine account. This page covers its hosted endpoint (https://mcp.dealmachine.com).

Is the DealMachine MCP server safe to use?

DealMachine scores 86 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 DealMachine MCP server expose?

DealMachine exposes 130 tools: dealmachine_signup, dealmachine_account, dealmachine_enrich_address, dealmachine_enrich_latlng, dealmachine_enrich_apn, and 125 more. Their descriptions and schemas cost roughly 14,350 tokens of context every time the server is loaded.

Does the DealMachine MCP server require authentication?

Yes. DealMachine asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the DealMachine MCP server still maintained?

DealMachine is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the DealMachine MCP server?

VerifyMCP ran 13 checks on DealMachine, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.