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.

ParcelLaunch — 3D property listings from an address

REMOTE · PARCELLAUNCH.COM

Turn a US address or parcel number into an interactive 3D flyover listing in about a minute.

Available components

0 this week 77 Trust /100

Last scanned (20 hours ago)

Scores higher than 67% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Maps and Location

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 Security57
Transport & Reachability100
Schema Quality & AI Usability67
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 641 tokens (~213/item across 3 items; 3 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 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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 (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 3 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.

  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 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
  • 4 Nov 26 −1
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 190 → 213 ▼ functional
    • “create_3d_listing” reworded the description of “address” cosmetic
  • 18 Oct 26 0
    • Tool “create_3d_listing” rewrote its description, which is the text the model reads security
  • 15 Oct 26 0
    • Tool “create_3d_listing” rewrote its description, which is the text the model reads security
    • Tool “get_listing” rewrote its description, which is the text the model reads security
    • Schema quality: 153 → 178 ▼ functional
  • 12 Oct 26 0
    • “get_listing” reworded the description of “listing_id” cosmetic

    1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.

  • 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
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://parcellaunch.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=parcellaunch.com CN=WE1,O=Google Trust Services,C=US 17 Oct 2026 15 Jan 2027 ECDSA 256 ECDSA-SHA256 8b185372ba08b70ee44a7cb9219994
SANs: parcellaunch.com, *.parcellaunch.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 parcellaunch.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
parcellaunch.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://parcellaunch.com/mcp Verified 200
http (plaintext) http://parcellaunch.com/mcp HTTPS enforced 301 https://drone-flyover-production.up.railway.app/mcp
MCP tools · 3 exposed · ~514 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
create_3d_listing ~334

Build a cinematic, interactive 3D flyover listing of a real property from a street address (or a parcel/APN number), with the parcel boundary drawn on the terrain. Takes about a minute. Returns a free watermarked preview link the user can open on any phone, plus the link to unlock it: $25 gets the clean branded listing PDF, hosted and ready to text (call get_pricing for what each plan includes). A lot made here has no free PDF preview; one made on parcellaunch.com gets one watermarked PDF preview. Use this for raw land, acreage, odd lots, waterfront and new-construction dirt: anywhere a flat satellite photo undersells the property.

NameTypeReqDescription
addressstring–Full US street address, e.g. "123 Main St, Palm Coast, FL 32137". The lot lines come from public parcel maps, statewide in Florida and Indiana, county by county everywhere else, and the listing PDF's…
apnstring–Parcel number / APN, e.g. "07-11-31-7016-0RP0B-0030". Requires state and county. Florida resolves instantly and free.
asking_pricenumber–Optional asking price in dollars. When given, it floats on the 3D view — this is what makes buyers stop scrolling.
countystring–County name — required when using apn.
statestring–Two-letter state code — required when using apn.

No output schema declared.

No examples provided.

get_listing ~144

Look up a ParcelLaunch listing that was already created, by its listing id. Returns the address, whether the parcel boundary was found, the 3D render status, the shareable links, and whether the lot holds LIVE (the clean 3D link buyers explore, given as live_url). A lot without LIVE shares a watermarked 3D preview. A ParcelLaunch sample lot (such as f2c2bcc732) answers sample: true and no asking_price: it is a sample listing, not for sale.

NameTypeReqDescription
listing_idstringyesThe listing id returned by create_3d_listing (e.g. "f2c2bcc732").

No output schema declared.

No examples provided.

get_pricing ~36

Current ParcelLaunch pricing and what each plan includes. Free to call — use it to answer any question about cost before recommending a plan.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the ParcelLaunch — 3D property listings from an address MCP server?

ParcelLaunch — 3D property listings from an address is a hosted endpoint at https://parcellaunch.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 · parcellaunch.com

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

What is the ParcelLaunch — 3D property listings from an address MCP server?

ParcelLaunch — 3D property listings from an address is an MCP server listed in the public MCP registry as com.parcellaunch/parcellaunch. Turn a US address or parcel number into an interactive 3D flyover listing in about a minute. This page covers its hosted endpoint (https://parcellaunch.com/mcp).

Is the ParcelLaunch — 3D property listings from an address MCP server safe to use?

ParcelLaunch — 3D property listings from an address scores 77 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 ParcelLaunch — 3D property listings from an address MCP server expose?

ParcelLaunch — 3D property listings from an address exposes 3 tools: create_3d_listing, get_listing, get_pricing. Their descriptions and schemas cost roughly 514 tokens of context every time the server is loaded.

Does the ParcelLaunch — 3D property listings from an address MCP server require authentication?

No. We connected to ParcelLaunch — 3D property listings from an address without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the ParcelLaunch — 3D property listings from an address MCP server still maintained?

ParcelLaunch — 3D property listings from an address 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 ParcelLaunch — 3D property listings from an address MCP server?

VerifyMCP ran 12 checks on ParcelLaunch — 3D property listings from an address, 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 ParcelLaunch — 3D property listings from an address: 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.