Home-Services Agent Network
com.joeygeorgeplumbing/home-services-agent-networkVersion 1.0.0Home-services agent network: registry of local pros, standard job-request form, receipts ledger.
Status
Responds287 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 14:02 UTC
- Latency
- 287 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 22:14 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://agent-network-gold.vercel.app/Responds287 msNo sign-in
Claude Code
claude mcp add --transport http home-services-agent-network https://agent-network-gold.vercel.app/Claude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: home-services-agent-network
Remote MCP server URL: https://agent-network-gold.vercel.app/Cursor
{
"mcpServers": {
"home-services-agent-network": {
"url": "https://agent-network-gold.vercel.app/"
}
}
}VS Code
code --add-mcp '{"name":"home-services-agent-network","type":"http","url":"https://agent-network-gold.vercel.app/"}'Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
7 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
check_inboxFor 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. | Not declared | Not declared | Not declared | Not declared |
get_listingGet the full public details of one listing by listing_id (no key needed; keys and personal contacts are never exposed). | Not declared | Not declared | Not declared | Not declared |
network_statsCounts 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. | Not declared | Not declared | Not declared | Not declared |
register_businessRegister 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. | Not declared | Not declared | Not declared | Not declared |
search_prosSearch 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. | Not declared | Not declared | Not declared | Not declared |
send_job_requestSend 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. Safe to retry: if your connection drops, resend the identical form — an identical resubmission within 7 days is treated as the same job, returns the original request_id with duplicate: true, and creates no second lead. A request with any detail changed is treated as a new job. | Not declared | Not declared | Not declared | Not declared |
update_request_statusFor 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. | Not declared | Not declared | Not declared | Not declared |
Details
- Registry status
- Active
- Published
- Nov 1, 2026
- Updated
- Nov 1, 2026
- Website
- Not given
- Repository
- Not given
- Categories (suggested)
- Invoicing and accountingSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared