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.

HireNimbus home services MCP

REMOTE · MCP.HIRENIMBUS.COM

Find and book verified local home service professionals through AI agents.

−1 this week 72 Trust /100

Last scanned (14 hours ago)

Scores higher than 58% of remote servers

Reachable. Last reached 5 Nov 2026.

Category E-commerce

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 Security63
Transport & Reachability100
Schema Quality & AI Usability38
  • 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 3246 tokens (~135/item across 24 items; 19 tools + 5 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 Management94
  • Stability check failed: schema churn in the 30 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage89
  • 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 19 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 21 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.

  • 2 Nov 26 −1
    • Stability: pass → fail ▼ security
    • A breaking change shipped without a version bump: still 1.26.0 ▼ security
    • Tool “get_more_tools” was removed ▼ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “book_electrician” rewrote its description, which is the text the model reads security
    • Tool “book_handyman” rewrote its description, which is the text the model reads security
    • Tool “book_hvac” rewrote its description, which is the text the model reads security
    • Tool “book_plumber” rewrote its description, which is the text the model reads security
    • Tool “book_renovation” rewrote its description, which is the text the model reads security
    • Tool “book_same_pro_again” rewrote its description, which is the text the model reads security
    • Tool “cancel_booking” rewrote its description, which is the text the model reads security
    • Tool “create_booking” rewrote its description, which is the text the model reads security
    • Tool “find_electrician” rewrote its description, which is the text the model reads security
    • Tool “find_handyman” rewrote its description, which is the text the model reads security
    • Tool “find_hvac” rewrote its description, which is the text the model reads security
    • Tool “find_plumber” rewrote its description, which is the text the model reads security
    • Tool “find_renovation” rewrote its description, which is the text the model reads security
    • Tool “get_booking_status” rewrote its description, which is the text the model reads security
    • Tool “get_my_profile” rewrote its description, which is the text the model reads security
    • Tool “get_previous_jobs” rewrote its description, which is the text the model reads security
    • Tool “get_provider_details” rewrote its description, which is the text the model reads security
    • Tool “get_provider_reviews” rewrote its description, which is the text the model reads security
    • Tool “search_providers” rewrote its description, which is the text the model reads security
    • Tool coverage: 95% → 100% ▲ functional
    • Schema quality: 384 → 135 ▲ functional
    • “book_electrician” reworded the description of “context” cosmetic
    • “book_electrician” reworded the description of “location” cosmetic
    • “book_handyman” reworded the description of “context” cosmetic
    • “book_handyman” reworded the description of “location” cosmetic
    • “book_hvac” reworded the description of “context” cosmetic
    • “book_hvac” reworded the description of “location” cosmetic
    • “book_plumber” reworded the description of “context” cosmetic
    • “book_plumber” reworded the description of “location” cosmetic
    • “book_renovation” reworded the description of “context” cosmetic
    • “book_renovation” reworded the description of “location” cosmetic
    • “book_same_pro_again” reworded the description of “address” cosmetic
    • “book_same_pro_again” reworded the description of “confirm_booking” cosmetic
    • “book_same_pro_again” reworded the description of “context” cosmetic
    • “book_same_pro_again” reworded the description of “job_description” cosmetic
    • “book_same_pro_again” reworded the description of “job_id” cosmetic
    • “book_same_pro_again” reworded the description of “location” cosmetic
    • “book_same_pro_again” reworded the description of “name” cosmetic
    • “book_same_pro_again” reworded the description of “phone” cosmetic
    • “cancel_booking” reworded the description of “confirm_cancellation” cosmetic
    • “cancel_booking” reworded the description of “context” cosmetic
    • “cancel_booking” reworded the description of “job_id” cosmetic
    • “create_booking” reworded the description of “address” cosmetic
    • “create_booking” reworded the description of “confirm_booking” cosmetic
    • “create_booking” reworded the description of “context” cosmetic
    • “create_booking” reworded the description of “location” cosmetic
    • “create_booking” reworded the description of “name” cosmetic
    • “create_booking” reworded the description of “phone” cosmetic
    • “create_booking” reworded the description of “search_result_id” cosmetic
    • “find_electrician” reworded the description of “context” cosmetic
    • “find_electrician” reworded the description of “location” cosmetic
    • “find_handyman” reworded the description of “context” cosmetic
    • “find_handyman” reworded the description of “location” cosmetic
    • “find_hvac” reworded the description of “context” cosmetic
    • “find_hvac” reworded the description of “location” cosmetic
    • “find_plumber” reworded the description of “context” cosmetic
    • “find_plumber” reworded the description of “location” cosmetic
    • “find_renovation” reworded the description of “context” cosmetic
    • “find_renovation” reworded the description of “location” cosmetic
    • “get_booking_status” reworded the description of “context” cosmetic
    • “get_my_profile” reworded the description of “context” cosmetic
    • “get_previous_jobs” reworded the description of “context” cosmetic
    • “get_provider_details” reworded the description of “context” cosmetic
    • “get_provider_reviews” reworded the description of “context” cosmetic
    • “search_providers” reworded the description of “context” cosmetic
    • “search_providers” reworded the description of “location” cosmetic
    • “search_providers” reworded the description of “query” cosmetic
  • 16 Oct 26 +1
    • Stability: 0.97 → pass security
  • 14 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 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 80 to 87. That category is still filling its 30-day observation window: 24 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.

  • 10 Oct 26 +3

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 80. That category is still filling its 30-day observation window: 18 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.

  • 3 Oct 26 +1

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

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

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

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

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
hirenimbus.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
Header Value
strict-transport-security max-age=63072000; includeSubDomains
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.hirenimbus.com/mcp Verified 200
http (plaintext) http://mcp.hirenimbus.com/mcp HTTPS enforced 301 https://mcp.hirenimbus.com/mcp
MCP tools · 19 exposed · ~3,167 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
book_electrician ~183

Searches HireNimbus providers for an electrician or electrical work, including jobs such as a dead outlet or outlet not working, breaker that keeps tripping, electrical panel upgrade, light fixture or ceiling fan installation, dimmer or switch replacement, EV charger installation, flickering lights, GFCI outlets, recessed lighting, hardwired smoke detectors, or exterior and landscape lighting. Does not require authentication. Inputs include a 5-digit US ZIP location, page, limit, and optional context. Returns provider records and resolved location. Read-only.

NameTypeReqDescription
context––Optional analytics context for a brief, non-identifying summary of the request purpose. The value is recorded as Agent Intent.
limitinteger––
locationstringyes5-digit US ZIP code (e.g. "22307" or "94114").
pageinteger––
NameTypeReqDescription
resultobjectyes–

No examples provided.

book_handyman ~199

Searches HireNimbus providers for a handyman or general home repair pro, including jobs such as TV mounting, furniture assembly, a hole in the drywall, a door that won't close or latch, sticking or squeaky doors, caulking or grout repair, shelving or picture hanging, weatherstripping, fence or gate repair, loose deck boards, gutter cleaning or minor gutter repair, trim and baseboard work, small tile fixes, or paint touch-ups. Does not require authentication. Inputs include a 5-digit US ZIP location, page, limit, and optional context. Returns provider records and resolved location. Read-only.

NameTypeReqDescription
context––Optional analytics context for a brief, non-identifying summary of the request purpose. The value is recorded as Agent Intent.
limitinteger––
locationstringyes5-digit US ZIP code (e.g. "22307" or "94114").
pageinteger––
NameTypeReqDescription
resultobjectyes–

No examples provided.

book_hvac ~193

Searches HireNimbus providers for HVAC heating, cooling, or AC service, including jobs such as AC not cooling or blowing warm air, furnace won't turn on or no heat, heat pump repair or installation, thermostat or smart-thermostat installation, refrigerant recharge, seasonal HVAC tune-up or maintenance, mini-split installation, duct sealing or cleaning, strange noises or smells from the unit, or uneven temperatures between rooms. Does not require authentication. Inputs include a 5-digit US ZIP location, page, limit, and optional context. Returns provider records and resolved location. Read-only.

NameTypeReqDescription
context––Optional analytics context for a brief, non-identifying summary of the request purpose. The value is recorded as Agent Intent.
limitinteger––
locationstringyes5-digit US ZIP code (e.g. "22307" or "94114").
pageinteger––
NameTypeReqDescription
resultobjectyes–

No examples provided.

book_plumber ~184

Searches HireNimbus providers for a plumber or plumbing repair, including jobs such as a leaky or dripping faucet, clogged drain or toilet, running toilet, low water pressure, water heater repair or replacement (including tankless), a leak under the sink, burst or frozen pipes, sump pump issues, garbage disposal repair, sewer line backup, shower valve replacement, or toilet installation. Does not require authentication. Inputs include a 5-digit US ZIP location, page, limit, and optional context. Returns provider records and resolved location. Read-only.

NameTypeReqDescription
context––Optional analytics context for a brief, non-identifying summary of the request purpose. The value is recorded as Agent Intent.
limitinteger––
locationstringyes5-digit US ZIP code (e.g. "22307" or "94114").
pageinteger––
NameTypeReqDescription
resultobjectyes–

No examples provided.

book_renovation ~176

Searches HireNimbus providers for a renovation or remodeling contractor, including jobs such as a kitchen remodel, bathroom remodel, basement finishing, flooring installation (hardwood, LVP, or tile), deck build, room addition, wall removal or open-floor-plan conversion, full interior painting, countertop replacement, or cabinet installation or refacing. Does not require authentication. Inputs include a 5-digit US ZIP location, page, limit, and optional context. Returns provider records and resolved location. Read-only.

NameTypeReqDescription
context––Optional analytics context for a brief, non-identifying summary of the request purpose. The value is recorded as Agent Intent.
limitinteger––
locationstringyes5-digit US ZIP code (e.g. "22307" or "94114").
pageinteger––
NameTypeReqDescription
resultobjectyes–

No examples provided.

book_same_pro_again ~290

Creates a service request for a provider associated with a prior job ID. Inputs include the job ID and optional work, profile, location, and confirmation values. Requires authentication. Unauthenticated requests return status "auth_required". confirm_booking=false returns a preview; confirm_booking=true submits the request. Confirmed submissions are not idempotent; repeated confirmed submissions create separate requests. Returns booking status, summary, identifiers, links, and notification statuses.

NameTypeReqDescription
address––Optional street-level address override. The profile or prior-job address is used otherwise. Accepted structured fields include address1, city, region, postalCode, etc.; formattedAddress is output onl…
confirm_bookingboolean–false (default) returns a rebooking preview without submitting. true submits the rebooking.
context––Optional analytics context for a brief, non-identifying summary of the request purpose. The value is recorded as Agent Intent.
job_description––Description of the new work; the prior job description is reused when absent
job_id–yesIdentifier of the prior job
location––Optional geocoding hint when address lacks coordinates. Accepted forms are lat+lng, zip, or text.
name––Optional name override; the authenticated homeowner profile supplies the value otherwise
phone––Optional phone override; the authenticated homeowner profile supplies the value otherwise
sourcestring––
NameTypeReqDescription
resultobjectyes–

No examples provided.

cancel_booking ~123

Cancels an authenticated homeowner booking identified by job ID. confirm_cancellation=false returns a preview; true submits the cancellation. The cancellation reason is delivered to the provider.

NameTypeReqDescription
confirm_cancellationboolean–false (default) returns a cancellation preview without changing the booking; true cancels the booking
contextstring–Optional analytics context for a brief, non-identifying summary of the request purpose. The value is recorded as Agent Intent.
job_id–yesIdentifier of the booking to cancel
reasonstringyesShort homeowner-provided cancellation reason
NameTypeReqDescription
resultobjectyes–

No examples provided.

create_booking ~317

Creates a service request for a provider slug and job description. Optional inputs include profile overrides, location, search result identifier, and confirmation flag. Requires authentication. Unauthenticated requests return status "auth_required". confirm_booking=false returns a preview with status "confirmation_required"; confirm_booking=true submits the request. Confirmed submissions are not idempotent; repeated confirmed submissions create separate requests. Returns booking status, identifiers, links, and notification statuses.

NameTypeReqDescription
address––Optional street-level address override. The authenticated homeowner profile address is used otherwise. Accepted fields are address1, address2, city, region, postalCode, and country; formattedAddress…
confirm_bookingboolean–false (default) returns booking_summary without submitting. true submits the booking.
context––Optional analytics context for a brief, non-identifying summary of the request purpose. The value is recorded as Agent Intent.
job_descriptionstringyes–
location––Optional geocoding hint when address lacks coordinates; the profile address is used otherwise. Accepted forms: lat+lng, zip, or text (e.g. {"text": "Alexandria, VA"}).
name––Optional name override; the authenticated homeowner profile supplies the value otherwise
phone––Optional phone override; the authenticated homeowner profile supplies the value otherwise
search_result_id––Search result identifier associated with the selected provider. Required for confirmed out-of-market bookings.
serviceProviderSlugstringyes–
sourcestring––
NameTypeReqDescription
resultobjectyes–

No examples provided.

find_electrician ~183

Searches HireNimbus providers for an electrician or electrical work, including jobs such as a dead outlet or outlet not working, breaker that keeps tripping, electrical panel upgrade, light fixture or ceiling fan installation, dimmer or switch replacement, EV charger installation, flickering lights, GFCI outlets, recessed lighting, hardwired smoke detectors, or exterior and landscape lighting. Does not require authentication. Inputs include a 5-digit US ZIP location, page, limit, and optional context. Returns provider records and resolved location. Read-only.

NameTypeReqDescription
context––Optional analytics context for a brief, non-identifying summary of the request purpose. The value is recorded as Agent Intent.
limitinteger––
locationstringyes5-digit US ZIP code (e.g. "22307" or "94114").
pageinteger––
NameTypeReqDescription
resultobjectyes–

No examples provided.

find_handyman ~199

Searches HireNimbus providers for a handyman or general home repair pro, including jobs such as TV mounting, furniture assembly, a hole in the drywall, a door that won't close or latch, sticking or squeaky doors, caulking or grout repair, shelving or picture hanging, weatherstripping, fence or gate repair, loose deck boards, gutter cleaning or minor gutter repair, trim and baseboard work, small tile fixes, or paint touch-ups. Does not require authentication. Inputs include a 5-digit US ZIP location, page, limit, and optional context. Returns provider records and resolved location. Read-only.

NameTypeReqDescription
context––Optional analytics context for a brief, non-identifying summary of the request purpose. The value is recorded as Agent Intent.
limitinteger––
locationstringyes5-digit US ZIP code (e.g. "22307" or "94114").
pageinteger––
NameTypeReqDescription
resultobjectyes–

No examples provided.

find_hvac ~193

Searches HireNimbus providers for HVAC heating, cooling, or AC service, including jobs such as AC not cooling or blowing warm air, furnace won't turn on or no heat, heat pump repair or installation, thermostat or smart-thermostat installation, refrigerant recharge, seasonal HVAC tune-up or maintenance, mini-split installation, duct sealing or cleaning, strange noises or smells from the unit, or uneven temperatures between rooms. Does not require authentication. Inputs include a 5-digit US ZIP location, page, limit, and optional context. Returns provider records and resolved location. Read-only.

NameTypeReqDescription
context––Optional analytics context for a brief, non-identifying summary of the request purpose. The value is recorded as Agent Intent.
limitinteger––
locationstringyes5-digit US ZIP code (e.g. "22307" or "94114").
pageinteger––
NameTypeReqDescription
resultobjectyes–

No examples provided.

find_plumber ~184

Searches HireNimbus providers for a plumber or plumbing repair, including jobs such as a leaky or dripping faucet, clogged drain or toilet, running toilet, low water pressure, water heater repair or replacement (including tankless), a leak under the sink, burst or frozen pipes, sump pump issues, garbage disposal repair, sewer line backup, shower valve replacement, or toilet installation. Does not require authentication. Inputs include a 5-digit US ZIP location, page, limit, and optional context. Returns provider records and resolved location. Read-only.

NameTypeReqDescription
context––Optional analytics context for a brief, non-identifying summary of the request purpose. The value is recorded as Agent Intent.
limitinteger––
locationstringyes5-digit US ZIP code (e.g. "22307" or "94114").
pageinteger––
NameTypeReqDescription
resultobjectyes–

No examples provided.

find_renovation ~176

Searches HireNimbus providers for a renovation or remodeling contractor, including jobs such as a kitchen remodel, bathroom remodel, basement finishing, flooring installation (hardwood, LVP, or tile), deck build, room addition, wall removal or open-floor-plan conversion, full interior painting, countertop replacement, or cabinet installation or refacing. Does not require authentication. Inputs include a 5-digit US ZIP location, page, limit, and optional context. Returns provider records and resolved location. Read-only.

NameTypeReqDescription
context––Optional analytics context for a brief, non-identifying summary of the request purpose. The value is recorded as Agent Intent.
limitinteger––
locationstringyes5-digit US ZIP code (e.g. "22307" or "94114").
pageinteger––
NameTypeReqDescription
resultobjectyes–

No examples provided.

get_booking_status ~65

Returns the current status of a HireNimbus booking by ID. Requires authentication. Read-only.

NameTypeReqDescription
booking_idstringyes–
contextstring–Optional analytics context for a brief, non-identifying summary of the request purpose. The value is recorded as Agent Intent.
NameTypeReqDescription
resultobjectyes–

No examples provided.

get_my_profile ~107

Returns the authenticated homeowner profile as structured JSON. Fields include status, name, phone, address, search_location, error_code, and message. Status values are "ok", "error", and "auth_required". search_location is a 5-digit ZIP from address.postalCode (e.g. "22307" or "94114").

NameTypeReqDescription
contextstring–Optional analytics context for a brief, non-identifying summary of the request purpose. The value is recorded as Agent Intent.
NameTypeReqDescription
address––Full service street address on file with fields address1, address2, city, region, postalCode, country, formattedAddress
error_code––Stable code such as "AUTH_REQUIRED" when status is auth_required
message––Error or auth_required explanation
name––Homeowner full name from profile (present when status is ok)
phone––Homeowner phone from profile (present when status is ok)
search_location––5-digit US ZIP from address.postalCode (e.g. "22307" or "94114").
statusstringyesOutcome: "ok" when profile loaded, "auth_required" when unsigned-in, "error" otherwise

No examples provided.

get_previous_jobs ~55

Returns past and active jobs for the authenticated homeowner. Requires authentication. Read-only.

NameTypeReqDescription
contextstring–Optional analytics context for a brief, non-identifying summary of the request purpose. The value is recorded as Agent Intent.
NameTypeReqDescription
resultobjectyes–

No examples provided.

get_provider_details ~84

Fetches a HireNimbus provider profile by slug. Does not require authentication. Inputs include slug and optional context. Returns ratings, reviews, past work, services, and availability where available. Read-only.

NameTypeReqDescription
context––Optional analytics context for a brief, non-identifying summary of the request purpose. The value is recorded as Agent Intent.
slugstringyes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

get_provider_reviews ~105

Fetches reviews for a HireNimbus provider by slug. Does not require authentication. Inputs include slug, page, page size, and optional context. Returns review text, ratings, dates, and review sources where available. Read-only.

NameTypeReqDescription
context––Optional analytics context for a brief, non-identifying summary of the request purpose. The value is recorded as Agent Intent.
pageinteger––
page_sizeinteger––
slugstringyes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

search_providers ~151

Searches providers by home service keyword and location. Does not require authentication. Inputs include query, 5-digit US ZIP location, page, limit, and optional context. Returns provider records, resolved location, market status, and a search result identifier. Read-only.

NameTypeReqDescription
context––Optional analytics context for a brief, non-identifying summary of the request purpose. The value is recorded as Agent Intent.
limitinteger––
locationstringyes5-digit US ZIP code (e.g. "22307" or "94114").
pageinteger––
querystringyesService keyword for a home service category (e.g. cleaning, landscaping, roofing).
NameTypeReqDescription
resultobjectyes–

No examples provided.

Install

How do I install the HireNimbus home services MCP server?

HireNimbus home services MCP is a hosted endpoint at https://mcp.hirenimbus.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 · mcp.hirenimbus.com

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

What is the HireNimbus home services MCP server?

HireNimbus home services MCP is listed in the public MCP registry as io.github.HireNimbus/home-services-mcp. Find and book verified local home service professionals through AI agents. This page covers its hosted endpoint (https://mcp.hirenimbus.com/mcp).

Is the HireNimbus home services MCP server safe to use?

HireNimbus home services MCP scores 72 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 HireNimbus home services MCP server expose?

HireNimbus home services MCP exposes 19 tools: get_my_profile, search_providers, get_provider_details, get_provider_reviews, create_booking, and 14 more. Their descriptions and schemas cost roughly 3,167 tokens of context every time the server is loaded.

Does the HireNimbus home services MCP server require authentication?

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

Is the HireNimbus home services MCP server still maintained?

HireNimbus home services MCP 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 HireNimbus home services MCP server?

VerifyMCP ran 13 checks on HireNimbus home services MCP, 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.