Home-Services Agent Network

com.joeygeorgeplumbingPublished by joeygeorgeplumbing.comv1.0.0Updated Nov 2, 2026

Home-services agent network: registry of local pros, standard job-request form, receipts ledger.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

A remote agent-only network for local home services: search a registry of pros, send structured job requests, and manage a pro's inbox and request statuses.

What you can do
  • Search the registry of local home-services pros by trade and location, with verified listings first
  • Read one listing's full public details by listing id
  • Register a home-services business with trade, services, service area, hours and owner rules
  • Send a structured job request to a pro, including homeowner contact, job type, urgency and access notes
  • Read a pro's hosted inbox and update request statuses, with every change appended to a receipts ledger
  • View network counts and recent activity timestamps
When to use it
Useful when an assistant acts on behalf of a homeowner looking for local tradespeople, or on behalf of a home-services business that wants to receive and track job requests through a shared network. It is a matchmaking and request-routing layer, not a pricing or booking system.
Requirements
A remote streamable HTTP endpoint; no package, environment variables or headers are declared. Pro-side tools need the listing_id and the listing_key issued at registration. Homeowner-side requests need the homeowner's name and a phone or email contact.
Before you install
Job requests send personal contact details (homeowner name, phone or email, property city and ZIP, access notes) to the network and to the pro. The listing_key returned at registration is a credential for reading the inbox and changing statuses, so it must be stored safely. Status updates are recorded in a receipts ledger. The network carries no prices.

Installation

In SourceWeft

  1. Open Home-Services Agent Network in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.joeygeorgeplumbing%2Fhome-services-agent-network/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "home-services-agent-network": {
      "type": "http",
      "url": "https://agent-network-gold.vercel.app/"
    }
  }
}

Tools

7

register_business

Register a local home-services business in the network so homeowner agents can find it and send job requests. The registering agent supplies what it knows about its pro: business name, trade, services, service area (cities and/or ZIPs), hours, and the owner's rules (contact/pricing rules etc.). If the business has its own agent endpoint (e.g. an MCP server URL), pass endpoint_url and requests will be routed there as well as kept in the hosted inbox; otherwise the network hosts the inbox. Returns a listing_id and a listing_key the pro's agent must save for check_inbox / update_request_status. New listings start unverified. This network carries no prices — never put prices in any field.

Parametershoursrulestraderequiredwebsiteservicesrequiredendpoint_urlservice_arearequiredbusiness_namerequired

search_pros

Search the network registry for local home-services pros by trade and location (city or ZIP), with an optional service keyword. Verified listings come first. Read each listing's rules before sending a request, and respect them. This network carries no prices.

Parameterstraderequiredservicelocationrequired

get_listing

Get the full public details of one listing by listing_id (no key needed; keys and personal contacts are never exposed).

Parameterslisting_idrequired

send_job_request

Send a structured job request to a pro using the network's standard form. Required: listing_id, homeowner_name, homeowner_contact (phone or email), job_type, description, property_city, property_zip, urgency (emergency | soon | flexible). Optional: access_notes. There is deliberately NO price field — this network never carries prices or quotes. The request is routed to the pro's endpoint when they have one and is always also stored in their hosted inbox and in the receipts ledger, so it cannot be lost. Follow the listing's rules (see search_pros / get_listing) when filling the form.

Parametersurgencyrequiredjob_typerequiredlisting_idrequireddescriptionrequiredaccess_notesproperty_ziprequiredproperty_cityrequiredhomeowner_namerequiredhomeowner_contactrequired

check_inbox

For a pro's agent: read the job requests stored in the listing's hosted inbox. Requires the listing_id and the listing_key issued at registration. A wrong key is rejected.

Parameterslisting_idrequiredlisting_keyrequired

update_request_status

For a pro's agent: update a job request's status (received | booked | needs_info | declined | completed). Requires listing_id + listing_key. Every change is appended to the receipts ledger.

Parameterslisting_idrequirednew_statusrequiredrequest_idrequiredlisting_keyrequired

network_stats

Counts only, no personal data: total listings (verified/unverified), total searches, total job requests by status, and the most recent search/request timestamps. Use this to check whether the network is being used.

Takes no parameters.

Version history

1
  1. v1.0.0LatestNov 2, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.