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.

Haulest

REMOTE · HAULEST.COM

Moving cost ranges, reviewed movers, licence checks, guides, and quote requests.

Available components

+3 this week 87 Trust /100

Last scanned (10 hours ago)

Scores higher than 94% of remote servers

Reachable. Last reached 5 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 Security80
Transport & Reachability100
Schema Quality & AI Usability80
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1840 tokens (~184/item across 10 items; 8 tools + 2 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 Management90
  • Stability observed for 27 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 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
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.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 23 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

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

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.haulest.com CN=YR1,O=Let's Encrypt,C=US 28 Sept 2026 27 Dec 2026 RSA 2048 SHA256-RSA 6166dd7e3b565f7d6fcca501dbcee7af7ad
SANs: *.haulest.com, haulest.com
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of haulest.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
haulest.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
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(self), payment=(), usb=(), interest-cohort=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://haulest.com/mcp Verified 200
http (plaintext) http://haulest.com/mcp HTTPS enforced 308 https://haulest.com/mcp
MCP tools · 8 exposed · ~1,557 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
check_mover_licence ~161

Looks a moving company up in the official register: for the United States, the FMCSA census by USDOT, MC, or legal name, with live operating authority, insurance on file, and safety rating when available; for the United Kingdom, Companies House by name or number. Returns the official record URL to confirm on. For Canada it explains the provincial checks instead. Use it before anyone pays a deposit or when a quote names a USDOT.

NameTypeReqDescription
marketstring–us (FMCSA, default), uk (Companies House), or ca (guidance only; Canada has no federal mover licence).
querystringyesUSDOT number, MC number, or company legal name (US); company name or number (UK).

No output schema declared.

No examples provided.

estimate_moving_cost ~267

Returns Haulest's research planning range (low and high, with currency) for a household move in the United States, Canada, or the United Kingdom, from home size and distance. Pass a distance band, a mileage, or an origin and destination; the tool resolves the distance from stored route data where it can. The range is compiled from published industry tables and public quotes, not a bid from a mover. Use it when someone asks what a move might cost.

NameTypeReqDescription
distanceBandstring–Distance band when known: local (under 50 mi; UK under 20), regional, mid, long, cross-country.
fromstring–Origin city or town, or a ZIP or postcode, e.g. "Austin, TX", "78701", or "London".
homeSizestringyesHome size: studio, 1bed, 2bed, 3bed, or 4bed (4bed covers larger homes).
marketstring–Country: us, ca, or uk. Inferred from the places when omitted; defaults to us.
milesnumber–Driving distance in miles when the user already knows it.
tostring–Destination city or town, or a ZIP or postcode.

No output schema declared.

No examples provided.

find_movers ~246

Lists moving companies Haulest holds dated, attributed reviews for in a city, state, province, or country (US, Canada, UK), with the average rating, the number of reviews on record, the newest review date, the USDOT number where there is one, and the profile URL. Ratings are means of real reviews on record; Haulest does not rank companies by payment. Use it when someone wants movers in a place; follow with the profile tool for one company.

NameTypeReqDescription
limitinteger–How many companies to return, up to 10 (larger values return 10). Default 6.
marketstring–Country to prefer when a place name exists in more than one: us, ca, or uk.
minReviewsinteger–Only companies with at least this many dated reviews on record.
placestringyesCity, state or province, country, or a ZIP or postcode, e.g. "Denver, CO", "Ontario", "Manchester", "Canada", "80202", "M5V".
sortstring–recommended (default), newest review, highest rating, or lowest rating.

No output schema declared.

No examples provided.

get_mover_profile ~129

One moving company in detail from its Haulest profile: rating and review counts, the three newest dated reviews, licence identifiers (USDOT, MC) with the live FMCSA authority and insurance summary when available, the company's own phone number from a public record, what reviewers paid, short checkable strengths and questions to ask, and the profile URL. Use it after find_movers or when someone names a company that has a Haulest page.

NameTypeReqDescription
slugstringyesThe company slug from find_movers, or the last part of a haulest.com/movers/... URL.

No output schema declared.

No examples provided.

get_moving_checklist ~83

Returns one of Haulest's checklists in full, grouped by section: the 8-week countdown, moving day, the first-night box, change of address for the US, Canada, or UK, or the 12-week international list. Use it when someone wants a to-do list for a move.

NameTypeReqDescription
liststringyesWhich checklist.

No output schema declared.

No examples provided.

get_route_facts ~120

Facts about a city-to-city moving lane that Haulest has a route page for: driving miles and hours, the research cost range by home size, how many households moved between the two states in the latest Census flow, and the page URL. Covers the main US, Canadian, and UK lanes. Use it when someone names both ends of a move; returns a clear not-covered message otherwise.

NameTypeReqDescription
fromstringyesOrigin city, e.g. "Austin" or "Austin, TX".
tostringyesDestination city.

No output schema declared.

No examples provided.

request_moving_quotes ~409

Submits a quote request to Haulest so licensed movers can call and email the person with written estimates for the move. Haulest is not a carrier; it introduces the request to movers through its lead desk, and in the US and UK the desk may phone within minutes. Call this only after the person has given their name, phone, and email for this purpose and has explicitly agreed to be contacted (consent must be true); confirm the details back to them first. Each call creates one request; a repeat with the same phone or email within a day is recognised and not duplicated. Returns a request reference and what happens next.

NameTypeReqDescription
callWindowstring–Best time to call.
consentbooleanyesMust be true: the person has explicitly agreed that Haulest may share these details with licensed movers who will call and email about this move.
dateFlexstring–How fixed the date is.
emailstringyesTheir email.
excludeMoverSlugstring–Haulest slug of a company the person does NOT want quotes from, e.g. one they already have a quote from.
fromstringyesWhere the move starts: city and state/province, or a postcode.
homeSizestringyesstudio, 1bed, 2bed, 3bed, or 4bed.
moveDatestringyesPlanned move date, YYYY-MM-DD, today or later.
moveTypestring–local, distance (long distance), or international.
namestringyesThe person's name.
notesstring–Anything else the movers should know: stairs, piano, elevator booking, access.
packingstring–Packing wanted: full pack, fragile only, or self pack.
phonestringyesA phone number the movers may call.
storageboolean–Storage needed.
tostringyesWhere it ends.

No output schema declared.

No examples provided.

search_moving_guides ~142

Searches Haulest's written guides, calculators, and checklists about hiring movers, estimates, deposits, consumer rights (US interstate rules, UK and Canadian practice), packing, and timing. Returns each match's title, one-paragraph answer, and URL. Use it for how-to and what-does-this-mean questions about moving.

NameTypeReqDescription
limitinteger–How many results, up to 8 (larger values return 8). Default 5.
querystringyesWhat the person wants to know, e.g. "binding estimate", "tipping movers", "deposit", "damage claim", "when to book".

No output schema declared.

No examples provided.

Install

How do I install the Haulest MCP server?

Haulest is a hosted endpoint at https://haulest.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 · haulest.com

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

What is the Haulest MCP server?

Haulest is an MCP server listed in the public MCP registry as com.haulest/haulest. Moving cost ranges, reviewed movers, licence checks, guides, and quote requests. This page covers its hosted endpoint (https://haulest.com/mcp).

Is the Haulest MCP server safe to use?

Haulest scores 87 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 Haulest MCP server expose?

Haulest exposes 8 tools: estimate_moving_cost, get_route_facts, find_movers, get_mover_profile, check_mover_licence, and 3 more. Their descriptions and schemas cost roughly 1,557 tokens of context every time the server is loaded.

Does the Haulest MCP server require authentication?

No. We connected to Haulest without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Haulest MCP server still maintained?

Haulest 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.