HireNimbus home services MCP
REMOTE · MCP.HIRENIMBUS.COM · SCANNED SEP 20
Find and book verified local home service professionals through AI agents.
Available components
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (cancel_booking). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability35
- 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 9616 tokens (~384/item across 25 items; 20 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 Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 61% of tool parameters carry a description.Partial
- Structured output schemas are declared (95% 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 20 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 22 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
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
claude mcp add --transport http hirenimbus-home-services-mcp 'https://mcp.hirenimbus.com/mcp'
{
"mcpServers": {
"hirenimbus-home-services-mcp": {
"url": "https://mcp.hirenimbus.com/mcp"
}
}
} {
"servers": {
"hirenimbus-home-services-mcp": {
"type": "http",
"url": "https://mcp.hirenimbus.com/mcp"
}
}
} [mcp_servers.hirenimbus-home-services-mcp] url = "https://mcp.hirenimbus.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"hirenimbus-home-services-mcp": {
"type": "remote",
"url": "https://mcp.hirenimbus.com/mcp",
"enabled": true
}
}
} openclaw mcp add hirenimbus-home-services-mcp --url 'https://mcp.hirenimbus.com/mcp' --transport streamable-http
mcp_servers:
hirenimbus-home-services-mcp:
url: "https://mcp.hirenimbus.com/mcp" {
"McpServers": {
"hirenimbus-home-services-mcp": {
"Transport": "http",
"Url": "https://mcp.hirenimbus.com/mcp"
}
}
} assistant mcp add hirenimbus-home-services-mcp -t streamable-http -u 'https://mcp.hirenimbus.com/mcp'
{
"mcpServers": {
"hirenimbus-home-services-mcp": {
"type": "http",
"url": "https://mcp.hirenimbus.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 0
- 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 “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_my_profile” 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
- Stability: unverified → 0.03 ▲ functional
- “book_electrician” reworded the description of “context” cosmetic
- “book_handyman” reworded the description of “context” cosmetic
- “book_hvac” reworded the description of “context” cosmetic
- “book_plumber” reworded the description of “context” cosmetic
- “book_renovation” reworded the description of “context” cosmetic
- “book_same_pro_again” reworded the description of “context” cosmetic
- “cancel_booking” reworded the description of “context” cosmetic
- “create_booking” reworded the description of “context” cosmetic
- “find_electrician” reworded the description of “context” cosmetic
- “find_handyman” reworded the description of “context” cosmetic
- “find_hvac” reworded the description of “context” cosmetic
- “find_plumber” reworded the description of “context” cosmetic
- “find_renovation” reworded the description of “context” cosmetic
- “get_booking_status” reworded the description of “context” cosmetic
- “get_more_tools” 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
- “book_electrician” made “context” optional cosmetic
- “book_handyman” made “context” optional cosmetic
- “book_hvac” made “context” optional cosmetic
- “book_plumber” made “context” optional cosmetic
- “book_renovation” made “context” optional cosmetic
- “book_same_pro_again” made “context” optional cosmetic
- “cancel_booking” made “context” optional cosmetic
- “create_booking” made “context” optional cosmetic
- “find_electrician” made “context” optional cosmetic
- “find_handyman” made “context” optional cosmetic
- “find_hvac” made “context” optional cosmetic
- “find_plumber” made “context” optional cosmetic
- “find_renovation” made “context” optional cosmetic
- “get_booking_status” made “context” optional cosmetic
- “get_more_tools” made “context” optional cosmetic
- “get_my_profile” made “context” optional cosmetic
- “get_previous_jobs” made “context” optional cosmetic
- “get_provider_details” made “context” optional cosmetic
- “get_provider_reviews” made “context” optional cosmetic
- “search_providers” made “context” optional cosmetic
- 16 Sept 26 59
First indexed and scored.
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 20 Sept 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 | 21 Aug 2026 | 19 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 82c4a52d769c47ca132b341139580a07 |
| 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. | present | 19718 | 13 | Verified |
| hirenimbus.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 |
| 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 |
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 →
book_electrician Book electrician ~399
Use when the user wants to book or hire a electrician — including when they describe a problem to fix, 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. Runs the provider search first (query='electrician' prefilled); after results, ask which pro they would like to book, then use create_booking. Do not start OTP until create_booking returns auth_required after they chose a pro. Do not use for DIY how-to advice or price research with no hiring intent. Always pass optional `context` on this call (15-25 words, third person, abstract purpose only, no PII) so analytics can record why the tool was called. Omitting it does not fail the call; do not send an empty string.
| Name | Type | Req | Description |
|---|---|---|---|
| context | – | – | Always include this argument on every call — do not omit it (analytics / Agent Intent). Write 15-25 words in third person explaining why this tool is being called. Abstract purpose only: never names,… |
| limit | integer | – | – |
| location | string | yes | Prefer a 5-digit US ZIP for location (e.g. "22307" or "94114"). This is the primary and preferred location input. After get_my_profile, if address.postalCode exists and the user confirmed the saved s… |
| page | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
book_handyman Book handyman ~413
Use when the user wants to book or hire a handyman — including when they describe a problem to fix, 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. Runs the provider search first (query='handyman' prefilled); after results, ask which pro they would like to book, then use create_booking. Do not start OTP until create_booking returns auth_required after they chose a pro. Do not use for DIY how-to advice or price research with no hiring intent. Always pass optional `context` on this call (15-25 words, third person, abstract purpose only, no PII) so analytics can record why the tool was called. Omitting it does not fail the call; do not send an empty string.
| Name | Type | Req | Description |
|---|---|---|---|
| context | – | – | Always include this argument on every call — do not omit it (analytics / Agent Intent). Write 15-25 words in third person explaining why this tool is being called. Abstract purpose only: never names,… |
| limit | integer | – | – |
| location | string | yes | Prefer a 5-digit US ZIP for location (e.g. "22307" or "94114"). This is the primary and preferred location input. After get_my_profile, if address.postalCode exists and the user confirmed the saved s… |
| page | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
book_hvac Book HVAC ~406
Use when the user wants to book or hire a HVAC — including when they describe a problem to fix, 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. Runs the provider search first (query='hvac' prefilled); after results, ask which pro they would like to book, then use create_booking. Do not start OTP until create_booking returns auth_required after they chose a pro. Do not use for DIY how-to advice or price research with no hiring intent. Always pass optional `context` on this call (15-25 words, third person, abstract purpose only, no PII) so analytics can record why the tool was called. Omitting it does not fail the call; do not send an empty string.
| Name | Type | Req | Description |
|---|---|---|---|
| context | – | – | Always include this argument on every call — do not omit it (analytics / Agent Intent). Write 15-25 words in third person explaining why this tool is being called. Abstract purpose only: never names,… |
| limit | integer | – | – |
| location | string | yes | Prefer a 5-digit US ZIP for location (e.g. "22307" or "94114"). This is the primary and preferred location input. After get_my_profile, if address.postalCode exists and the user confirmed the saved s… |
| page | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
book_plumber Book plumber ~400
Use when the user wants to book or hire a plumber — including when they describe a problem to fix, 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. Runs the provider search first (query='plumber' prefilled); after results, ask which pro they would like to book, then use create_booking. Do not start OTP until create_booking returns auth_required after they chose a pro. Do not use for DIY how-to advice or price research with no hiring intent. Always pass optional `context` on this call (15-25 words, third person, abstract purpose only, no PII) so analytics can record why the tool was called. Omitting it does not fail the call; do not send an empty string.
| Name | Type | Req | Description |
|---|---|---|---|
| context | – | – | Always include this argument on every call — do not omit it (analytics / Agent Intent). Write 15-25 words in third person explaining why this tool is being called. Abstract purpose only: never names,… |
| limit | integer | – | – |
| location | string | yes | Prefer a 5-digit US ZIP for location (e.g. "22307" or "94114"). This is the primary and preferred location input. After get_my_profile, if address.postalCode exists and the user confirmed the saved s… |
| page | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
book_renovation Book renovation ~393
Use when the user wants to book or hire a renovation — including when they describe a problem to fix, 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. Runs the provider search first (query='renovation' prefilled); after results, ask which pro they would like to book, then use create_booking. Do not start OTP until create_booking returns auth_required after they chose a pro. Do not use for DIY how-to advice or price research with no hiring intent. Always pass optional `context` on this call (15-25 words, third person, abstract purpose only, no PII) so analytics can record why the tool was called. Omitting it does not fail the call; do not send an empty string.
| Name | Type | Req | Description |
|---|---|---|---|
| context | – | – | Always include this argument on every call — do not omit it (analytics / Agent Intent). Write 15-25 words in third person explaining why this tool is being called. Abstract purpose only: never names,… |
| limit | integer | – | – |
| location | string | yes | Prefer a 5-digit US ZIP for location (e.g. "22307" or "94114"). This is the primary and preferred location input. After get_my_profile, if address.postalCode exists and the user confirmed the saved s… |
| page | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
book_same_pro_again Book same pro again ~397
Rebook a HireNimbus provider the homeowner has used before, by job ID. Requires authentication. Call with confirm_booking=false to preview the rebooking, then confirm_booking=true after homeowner approval. This tool may create a real booking request, including for an out-of-market address, because the provider is verified against the homeowner's owned prior job. Always pass optional `context` on this call (15-25 words, third person, abstract purpose only, no PII) so analytics can record why the tool was called. Omitting it does not fail the call; do not send an empty string.
| Name | Type | Req | Description |
|---|---|---|---|
| address | – | – | Optional street-level address override. Omit to use profile or prior-job address. Pass structured fields only (address1, city, region, postalCode, etc.) — never formattedAddress. |
| confirm_booking | boolean | – | false (default): return a rebooking preview; does NOT submit. true: submit the rebooking after the homeowner explicitly confirms. |
| context | – | – | Always include this argument on every call — do not omit it (analytics / Agent Intent). Write 15-25 words in third person explaining why this tool is being called. Abstract purpose only: never names,… |
| job_description | – | – | Description of the new work; omit to reuse the prior job description |
| job_id | – | yes | Job ID from get_previous_jobs for the prior booking to rehire |
| location | – | – | Optional geocoding hint when address lacks coordinates. Omit in normal flows. When needed, pass exactly one of: lat+lng, zip, or text. |
| name | – | – | Optional name override; omit to use authenticated homeowner profile |
| phone | – | – | Optional phone override; omit to use authenticated homeowner profile |
| source | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
cancel_booking Cancel booking ~188
Cancel one of the authenticated homeowner's bookings. First call with confirm_cancellation=false to present the booking and reason for review; call again with true only after explicit approval. The cancellation reason is delivered to the provider.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm_cancellation | boolean | – | false (default): return a cancellation preview without changing the booking; true: cancel after the homeowner explicitly confirms |
| context | string | – | Always include this argument on every call — do not omit it (analytics / Agent Intent). Write 15-25 words in third person explaining why this tool is being called. Abstract purpose only: never names,… |
| job_id | – | yes | Booking ID from get_previous_jobs |
| reason | string | yes | Short homeowner-provided cancellation reason |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
create_booking Create booking ~589
Secured booking after the homeowner has chosen a specific pro from search or book_* results. Do not call this to start discovery, and do not start OTP before the homeowner has seen and picked a pro. Agents should prefer book_handyman, book_hvac, book_plumber, book_electrician, or book_renovation for standard booking workflows when the category matches; those tools search first. Requires authentication to submit. If unauthenticated, returns status "auth_required" so you can trigger phone/OTP connect gracefully at book time. Default confirm_booking=false returns a preview. confirm_booking=true submits the request. Confirmed calls are not idempotent and may create duplicate requests. HireNimbus is currently active in Washington DC Metro, San Francisco Bay Area, and Austin Metro; providers found elsewhere may still be booked when returned by search, with the active-market disclosure shown to the homeowner. For an out-of-market booking, pass the search_result_id from that provider search. Do not call on ambiguous intent such as 'find and book someone' — the user must first pick a specific pro from search results. Always pass optional `context` on this call (15-25 words, third person, abstract purpose only, no PII) so analytics can record why the tool was called. Omitting it does not fail the call; do not send an empty string.
| Name | Type | Req | Description |
|---|---|---|---|
| address | – | – | Optional street-level address override. Omit to use the authenticated homeowner profile address. When overriding, pass only structured fields (address1, address2, city, region, postalCode, country) —… |
| confirm_booking | boolean | – | false (default): return booking_summary for user review; does NOT submit. true: submit the booking after the user explicitly confirms that summary. |
| context | – | – | Always include this argument on every call — do not omit it (analytics / Agent Intent). Write 15-25 words in third person explaining why this tool is being called. Abstract purpose only: never names,… |
| job_description | string | yes | – |
| location | – | – | Optional geocoding hint when address lacks coordinates. Omit in normal flows (profile address is used). When needed, pass exactly one of: lat+lng, zip, or text (e.g. {"text": "Alexandria, VA"}). |
| name | – | – | Optional override of profile name; omit to use authenticated homeowner profile |
| phone | – | – | Optional override of profile phone; omit to use authenticated homeowner profile |
| search_result_id | – | – | Search result ID returned by the provider search that produced the selected provider. Required for confirmed out-of-market bookings. |
| serviceProviderSlug | string | yes | – |
| source | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
find_electrician Find electrician ~440
Use when the user wants to find, search, or compare electrician professionals, or describes a problem a electrician solves — 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. Do not use for DIY how-to advice, cost research with no hiring intent, auto or appliance retail questions, or emergencies requiring 911 or the utility company. Read-only; does not create a booking. Showcase matching pros before any booking or OTP. If already signed in, get_my_profile may load the saved ZIP; otherwise search with the ZIP they provide. Prefer a 5-digit ZIP for location. If this ZIP returns no providers, keep the empty result; do not fill with providers from another area. Always pass optional `context` on this call (15-25 words, third person, abstract purpose only, no PII) so analytics can record why the tool was called. Omitting it does not fail the call; do not send an empty string.
| Name | Type | Req | Description |
|---|---|---|---|
| context | – | – | Always include this argument on every call — do not omit it (analytics / Agent Intent). Write 15-25 words in third person explaining why this tool is being called. Abstract purpose only: never names,… |
| limit | integer | – | – |
| location | string | yes | Prefer a 5-digit US ZIP for location (e.g. "22307" or "94114"). This is the primary and preferred location input. After get_my_profile, if address.postalCode exists and the user confirmed the saved s… |
| page | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
find_handyman Find handyman ~454
Use when the user wants to find, search, or compare handyman professionals, or describes a problem a handyman solves — 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. Do not use for DIY how-to advice, cost research with no hiring intent, auto or appliance retail questions, or emergencies requiring 911 or the utility company. Read-only; does not create a booking. Showcase matching pros before any booking or OTP. If already signed in, get_my_profile may load the saved ZIP; otherwise search with the ZIP they provide. Prefer a 5-digit ZIP for location. If this ZIP returns no providers, keep the empty result; do not fill with providers from another area. Always pass optional `context` on this call (15-25 words, third person, abstract purpose only, no PII) so analytics can record why the tool was called. Omitting it does not fail the call; do not send an empty string.
| Name | Type | Req | Description |
|---|---|---|---|
| context | – | – | Always include this argument on every call — do not omit it (analytics / Agent Intent). Write 15-25 words in third person explaining why this tool is being called. Abstract purpose only: never names,… |
| limit | integer | – | – |
| location | string | yes | Prefer a 5-digit US ZIP for location (e.g. "22307" or "94114"). This is the primary and preferred location input. After get_my_profile, if address.postalCode exists and the user confirmed the saved s… |
| page | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
find_hvac Find HVAC ~447
Use when the user wants to find, search, or compare HVAC professionals, or describes a problem a HVAC solves — 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. Do not use for DIY how-to advice, cost research with no hiring intent, auto or appliance retail questions, or emergencies requiring 911 or the utility company. Read-only; does not create a booking. Showcase matching pros before any booking or OTP. If already signed in, get_my_profile may load the saved ZIP; otherwise search with the ZIP they provide. Prefer a 5-digit ZIP for location. If this ZIP returns no providers, keep the empty result; do not fill with providers from another area. Always pass optional `context` on this call (15-25 words, third person, abstract purpose only, no PII) so analytics can record why the tool was called. Omitting it does not fail the call; do not send an empty string.
| Name | Type | Req | Description |
|---|---|---|---|
| context | – | – | Always include this argument on every call — do not omit it (analytics / Agent Intent). Write 15-25 words in third person explaining why this tool is being called. Abstract purpose only: never names,… |
| limit | integer | – | – |
| location | string | yes | Prefer a 5-digit US ZIP for location (e.g. "22307" or "94114"). This is the primary and preferred location input. After get_my_profile, if address.postalCode exists and the user confirmed the saved s… |
| page | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
find_plumber Find plumber ~441
Use when the user wants to find, search, or compare plumber professionals, or describes a problem a plumber solves — 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. Do not use for DIY how-to advice, cost research with no hiring intent, auto or appliance retail questions, or emergencies requiring 911 or the utility company. Read-only; does not create a booking. Showcase matching pros before any booking or OTP. If already signed in, get_my_profile may load the saved ZIP; otherwise search with the ZIP they provide. Prefer a 5-digit ZIP for location. If this ZIP returns no providers, keep the empty result; do not fill with providers from another area. Always pass optional `context` on this call (15-25 words, third person, abstract purpose only, no PII) so analytics can record why the tool was called. Omitting it does not fail the call; do not send an empty string.
| Name | Type | Req | Description |
|---|---|---|---|
| context | – | – | Always include this argument on every call — do not omit it (analytics / Agent Intent). Write 15-25 words in third person explaining why this tool is being called. Abstract purpose only: never names,… |
| limit | integer | – | – |
| location | string | yes | Prefer a 5-digit US ZIP for location (e.g. "22307" or "94114"). This is the primary and preferred location input. After get_my_profile, if address.postalCode exists and the user confirmed the saved s… |
| page | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
find_renovation Find renovation ~433
Use when the user wants to find, search, or compare renovation professionals, or describes a problem a renovation solves — 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. Do not use for DIY how-to advice, cost research with no hiring intent, auto or appliance retail questions, or emergencies requiring 911 or the utility company. Read-only; does not create a booking. Showcase matching pros before any booking or OTP. If already signed in, get_my_profile may load the saved ZIP; otherwise search with the ZIP they provide. Prefer a 5-digit ZIP for location. If this ZIP returns no providers, keep the empty result; do not fill with providers from another area. Always pass optional `context` on this call (15-25 words, third person, abstract purpose only, no PII) so analytics can record why the tool was called. Omitting it does not fail the call; do not send an empty string.
| Name | Type | Req | Description |
|---|---|---|---|
| context | – | – | Always include this argument on every call — do not omit it (analytics / Agent Intent). Write 15-25 words in third person explaining why this tool is being called. Abstract purpose only: never names,… |
| limit | integer | – | – |
| location | string | yes | Prefer a 5-digit US ZIP for location (e.g. "22307" or "94114"). This is the primary and preferred location input. After get_my_profile, if address.postalCode exists and the user confirmed the saved s… |
| page | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
get_booking_status Get booking status ~123
Check the current status of a HireNimbus booking by ID. Requires authentication. Read-only; does not create a booking.
| Name | Type | Req | Description |
|---|---|---|---|
| booking_id | string | yes | – |
| context | string | – | Always include this argument on every call — do not omit it (analytics / Agent Intent). Write 15-25 words in third person explaining why this tool is being called. Abstract purpose only: never names,… |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
get_more_tools ~114
Check for additional tools whenever your task might benefit from specialized capabilities - even if existing tools could work as a fallback.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | Always include this argument on every call — do not omit it (analytics / Agent Intent). Write 15-25 words in third person explaining why this tool is being called. Abstract purpose only: never names,… |
No output schema declared.
No examples provided.
get_my_profile Get my profile ~406
Load the authenticated homeowner profile. Use this only when the HireNimbus account is already connected, to fill the saved service address before search. Do not call this to start discovery for an anonymous user, and do not start phone/OTP just to search or compare pros. If this returns status "auth_required", continue with ZIP + search and show pros; trigger connect/OTP only when create_booking returns auth_required after the homeowner chose a pro. Returns GetMyProfileResult (structured JSON): - status (string, required): "ok", "error", or "auth_required" - name (string|null): homeowner full name when status is ok - phone (string|null): homeowner phone when status is ok - address (object|null): service street address with address1, address2, city, region, postalCode, country, formattedAddress - search_location (string|null): 5-digit ZIP from address.postalCode for search_providers.location (after user confirms the saved street address is the job site; never City, ST, the street line, formattedAddress, or address1) - error_code (string|null): "AUTH_REQUIRED" when status is auth_required - message (string|null): error or auth_required explanation If address.postalCode exists: show the saved street address, confirm it is the job site, then pass that postalCode as location. If address.postalCode is missing: ask once "What's the ZIP for the job?" Do not ask for city/state first. Name, street, and phone can wait until preview/book.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | Always include this argument on every call — do not omit it (analytics / Agent Intent). Write 15-25 words in third person explaining why this tool is being called. Abstract purpose only: never names,… |
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
| next_action | – | – | When status is auth_required: "continue_discovery" means search and show pros without OTP; "connect_to_book" means start phone/OTP connect now |
| phone | – | – | Homeowner phone from profile (present when status is ok) |
| search_location | – | – | 5-digit US ZIP from address.postalCode (e.g. "22307" or "94114") — pass to search_providers.location after the user confirms the saved street address is the job site. Never City, ST, a street line, f… |
| status | string | yes | Outcome: "ok" when profile loaded, "auth_required" when unsigned-in, "error" otherwise |
No examples provided.
get_previous_jobs Get previous jobs ~130
Return past and active jobs for the authenticated homeowner. Requires authentication. Use after search when augmenting recommendations, or when the user asks about job history. Read-only; does not create a booking.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | Always include this argument on every call — do not omit it (analytics / Agent Intent). Write 15-25 words in third person explaining why this tool is being called. Abstract purpose only: never names,… |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
get_provider_details Get provider details ~223
Fetch the full profile for a HireNimbus service provider by slug. Use after find_handyman, find_hvac, find_plumber, find_electrician, find_renovation, or search_providers when the homeowner wants more detail about a specific provider. Returns ratings, reviews, past work, and availability where available. Read-only; does not create a booking. Always pass optional `context` on this call (15-25 words, third person, abstract purpose only, no PII) so analytics can record why the tool was called. Omitting it does not fail the call; do not send an empty string.
| Name | Type | Req | Description |
|---|---|---|---|
| context | – | – | Always include this argument on every call — do not omit it (analytics / Agent Intent). Write 15-25 words in third person explaining why this tool is being called. Abstract purpose only: never names,… |
| slug | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
get_provider_reviews Get provider reviews ~201
Fetch reviews for a HireNimbus service provider by slug. Use when the homeowner wants to see what other homeowners have said about a provider before booking. Read-only; does not create a booking. Always pass optional `context` on this call (15-25 words, third person, abstract purpose only, no PII) so analytics can record why the tool was called. Omitting it does not fail the call; do not send an empty string.
| Name | Type | Req | Description |
|---|---|---|---|
| context | – | – | Always include this argument on every call — do not omit it (analytics / Agent Intent). Write 15-25 words in third person explaining why this tool is being called. Abstract purpose only: never names,… |
| page | integer | – | – |
| page_size | integer | – | – |
| slug | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
search_providers Search providers ~515
Use this when the user needs a home service outside the five dedicated find_* categories — such as house cleaning or deep cleaning, landscaping, lawn care or mowing, tree trimming, roofing or roof leak repair, gutter installation, pressure washing, junk removal, moving help, painting, or pest-adjacent cleanup — or when the service category is ambiguous. Prefer a 5-digit US ZIP for location (e.g. "22307", "94114"); never a street address, formattedAddress, or address1. Read-only; does not create a booking. Prefer the dedicated find_* tools (find_handyman, find_hvac, find_plumber, find_electrician, find_renovation) when the request matches those categories. Search results outside the supported launch markets can still be booked when returned by search; tell the homeowner about the active launch markets and the available provider. If the ZIP search returns no providers, keep that empty result — do not substitute providers from another area. The response includes a `search_result_id`; pass it to create_booking when booking a selected provider. Always pass optional `context` on this call (15-25 words, third person, abstract purpose only, no PII) so analytics can record why the tool was called. Omitting it does not fail the call; do not send an empty string.
| Name | Type | Req | Description |
|---|---|---|---|
| context | – | – | Always include this argument on every call — do not omit it (analytics / Agent Intent). Write 15-25 words in third person explaining why this tool is being called. Abstract purpose only: never names,… |
| limit | integer | – | – |
| location | string | yes | Prefer a 5-digit US ZIP for location (e.g. "22307" or "94114"). This is the primary and preferred location input. After get_my_profile, if address.postalCode exists and the user confirmed the saved s… |
| page | integer | – | – |
| query | string | yes | Service keyword for non-top categories (e.g. cleaning, landscaping, roofing). For handyman, HVAC, plumber, electrician, or renovation, use the dedicated find_* tools instead. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
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 60 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 20 tools: get_my_profile, search_providers, get_provider_details, get_provider_reviews, create_booking, and 15 more. Their descriptions and schemas cost roughly 7,112 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.