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.

com.dropwatchhq/parcel-edge

REMOTE · PARCELEDGE.DROPWATCHHQ.COM

Cook County IL commercial property-tax appeal leads: assessed value above recent arm's-length sale.

0 this week 69 Trust /100

Last scanned (14 hours ago)

Scores higher than 54% of remote servers

Reachable. Last reached 5 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 Security46
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1117 tokens (~159/item across 7 items; 7 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage87
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 60% 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
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (12)

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

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation 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.

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.

  • 28 Sept 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
  • 25 Sept 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
  • 26 Aug 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
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 11 Aug 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
  • 31 Jul 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
  • 27 Jul 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
  • 26 Jul 26 0

    First indexed and scored.

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 5 Nov 2026 · Probed https://parceledge.dropwatchhq.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=dropwatchhq.com CN=WE1,O=Google Trust Services,C=US 18 Oct 2026 16 Jan 2027 ECDSA 256 ECDSA-SHA256 b293b97347dcba430eb8baf88a15615e
SANs: dropwatchhq.com, parceledge.dropwatchhq.com, *.parceledge.dropwatchhq.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 insecure

Validation of parceledge.dropwatchhq.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
dropwatchhq.com. No DS 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://parceledge.dropwatchhq.com/mcp Verified 200
http (plaintext) http://parceledge.dropwatchhq.com/mcp Served over HTTP 200
MCP tools · 7 exposed · ~1,117 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
construction_window_leads ~125

Fresh ASSESSABLE construction permits (funded builds) entering the permit→financing window — prospects for hard-money / construction lenders racing the permit-to-loan gap. HONEST: loan-absence is UNVERIFIED (no current free per-parcel mortgage feed); this is a time-boxed absence-window WATCHLIST, re-checked as financing appears. Cook County. Permit amount, age, window status, applicant, work description.

NameTypeReqDescription
countystring–County (cook-il).
limitnumber––
minTierstring––

No output schema declared.

No examples provided.

county_coverage ~31

Covered counties, streams, buyers, data sources, methodology, and honest signal-density notes per stream. Free.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

exemption_flags ~256

Non-conclusory exemption-contradiction FLAGS: parcels where a residential/homestead exemption coexists with a NON-OWNER-OCCUPANT owner of record (Allegheny: HOMESTEADFLAG=HOM + corporate owner; Cook: residential parcel deeded to an LLC/corp/trust grantee; Philadelphia: single-family homestead exclusion + entity owner; Travis TX: active 10% homestead appraisal cap on a homesite parcel + LLC owner; Fulton GA: homestead ExCode + entity owner; Harris TX: LLC/corporate owner on a residential parcel — owner-type watchlist, HCAD publishes no homestead boolean to confirm). Candidate improper exemptions for exemption-audit / recovery contractors (~30% contingency of recovered liens). Full owner/exemption EVIDENCE CHAIN. NEVER a fraud verdict — the contractor confirms occupancy. Counties: cook-il, allegheny-pa, philadelphia-pa, travis-tx, harris-tx, fulton-ga.

NameTypeReqDescription
countystring–County (default allegheny-pa — densest). Only counties exposing an in-table exemption/owner field support this stream.
limitnumber––
minTierstring––

No output schema declared.

No examples provided.

lien_bundle_report ~222

INVESTOR DESK (paid, $0.50 USDC/call; free preview): per-parcel tax-deed title-research report for a single Allegheny County PA PIN. Returns every UNSATISFIED County/School/Municipal tax lien on the parcel bundled into one surviving-lien stack with a per-taxing-body split + total, the tax-year span (a long tail signals a likely JUDICIAL 'free & clear' sale; a short one an UPSET sale where the buyer takes SUBJECT to surviving liens), and the PA statutory redemption posture (72 P.S. §5860 — PA has no general post-sale redemption; the risk is surviving liens). The cross-join a tax-deed investor pays $150–500/parcel for. CANDIDATE title input, NOT a title opinion — confirm sale type + named lienholders with the county/counsel before bidding.

NameTypeReqDescription
pinstringyesAllegheny County PIN (parcel ID), e.g. 0138S00120000000.

No output schema declared.

No examples provided.

overassessment_leads ~191

Scored, dated, deadline-stamped COMMERCIAL property-tax over-assessment leads. Each lead is a parcel whose assessor implied-market value EXCEEDS its most recent CLEAN arm's-length sale price — a candidate over-payment a contingency tax-appeal firm pursues. Counties that publish a public sale price: cook-il, allegheny-pa, philadelphia-pa, king-wa, maricopa-az. (Texas/Georgia counties are non-disclosure — over-assessment is an honest null there; use exemption_flags instead.) Candidates from PUBLIC data; the firm confirms valuation. Not legal/valuation advice.

NameTypeReqDescription
countystring–County (default cook-il).
limitnumber–Max leads (default 25).
minRationumber–Min over-assessment ratio (default 1.15).
minTierstring–Min confidence tier (default high).

No output schema declared.

No examples provided.

parcel_overassessment ~61

Check a SINGLE Cook County PIN (14-digit) for over-assessment: latest certified AV + most recent clean sale, implied-market conversion, over-assessment ratio + appeal-window status. Free.

NameTypeReqDescription
pinstringyes14-digit Cook County PIN.

No output schema declared.

No examples provided.

stalled_surety ~231

STALLED-PROJECT candidates for SURETY / DRAW-CONTROL firms + the exposed construction lender. Each is a large ASSESSABLE building permit (real funded build) whose status is still NOT CLOSED well PAST its size-appropriate build window — an issued-but-never-finaled permit (no certificate-of-occupancy proxy reached). Built off the SAME nightly Cook Assessor Permits pull; the permit carries its own status field. Permit amount, age, expected build window, overdue days/%, current status. HONEST: 'stalled' is a STATUS+RECENCY inference, NOT a verified work-stoppage (paperwork lag / phased builds / slow finaling can also leave a permit OPEN) — the surety/draw-control firm confirms on the ground. Counties that do NOT expose permit status return an honest null for this stream; Cook does, so it ships here. Cook County.

NameTypeReqDescription
countystring–County (cook-il; only counties exposing permit status support this stream).
limitnumber––
minTierstring––

No output schema declared.

No examples provided.

Install

How do I install the com.dropwatchhq/parcel-edge MCP server?

com.dropwatchhq/parcel-edge is a hosted endpoint at https://parceledge.dropwatchhq.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 · parceledge.dropwatchhq.com

# add to Claude Code
claude mcp add --transport http com-dropwatchhq-parcel-edge 'https://parceledge.dropwatchhq.com/mcp'
Common questions

What is the com.dropwatchhq/parcel-edge MCP server?

com.dropwatchhq/parcel-edge is an MCP server listed in the public MCP registry as com.dropwatchhq/parcel-edge. Cook County IL commercial property-tax appeal leads: assessed value above recent arm's-length sale. This page covers its hosted endpoint (https://parceledge.dropwatchhq.com/mcp).

Is the com.dropwatchhq/parcel-edge MCP server safe to use?

com.dropwatchhq/parcel-edge scores 69 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 com.dropwatchhq/parcel-edge MCP server expose?

com.dropwatchhq/parcel-edge exposes 7 tools: overassessment_leads, construction_window_leads, stalled_surety, exemption_flags, lien_bundle_report, and 2 more. Their descriptions and schemas cost roughly 1,117 tokens of context every time the server is loaded.

Does the com.dropwatchhq/parcel-edge MCP server require authentication?

No. We connected to com.dropwatchhq/parcel-edge without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the com.dropwatchhq/parcel-edge MCP server still maintained?

com.dropwatchhq/parcel-edge 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.

What did VerifyMCP test on the com.dropwatchhq/parcel-edge MCP server?

VerifyMCP ran 12 checks on com.dropwatchhq/parcel-edge, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about com.dropwatchhq/parcel-edge: Authorization. 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.