Home-Services Agent Network
REMOTE · AGENT-NETWORK-GOLD.VERCEL.APP
Home-services agent network: registry of local pros, standard job-request form, receipts ledger.
Available components
Last scanned (9 hours ago)
Scores higher than 44% of remote servers
Reachable. Last reached 5 Nov 2026.
Category CRM and Sales
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 not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability68
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 996 tokens (~142/item across 7 items; 7 tools + 0 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 Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 63% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_job_request" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
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 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.
- 3 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 2 Nov 26 61
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 5 Nov 2026 · Probed https://agent-network-gold.vercel.app
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.vercel.app | CN=WR1,O=Google Trust Services,C=US | 31 Oct 2026 | 29 Jan 2027 | RSA 2048 | SHA256-RSA | 9c5f0e6a35c955e113044c86848e4cd5 |
| SANs: *.vercel.app | ||||||
| CN=WR1,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7fd9e2c2d2048a0474b627a26d0868a7 |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of agent-network-gold.vercel.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| vercel.app. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agent-network-gold.vercel.app | Verified | 200 | |
| http (plaintext) | http://agent-network-gold.vercel.app | HTTPS enforced | 308 | https://agent-network-gold.vercel.app/ |
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 →
check_inbox ~68
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.
| Name | Type | Req | Description |
|---|---|---|---|
| listing_id | string | yes | – |
| listing_key | string | yes | The secret key returned by register_business. |
No output schema declared.
No examples provided.
get_listing ~51
Get the full public details of one listing by listing_id (no key needed; keys and personal contacts are never exposed).
| Name | Type | Req | Description |
|---|---|---|---|
| listing_id | string | yes | The listing_id returned by register_business or search_pros. |
No output schema declared.
No examples provided.
network_stats ~50
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
register_business ~302
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.
| Name | Type | Req | Description |
|---|---|---|---|
| business_name | string | yes | Public business name. |
| endpoint_url | string | – | Optional: the business's own agent endpoint URL for request routing. |
| hours | string | – | Hours, e.g. '24/7' or 'Mon-Fri 8am-6pm'. |
| rules | string | – | The owner's rules for requests: how to qualify, what contact info to collect, pricing policy, etc. |
| service_area | array | yes | Cities and/or ZIP codes served. |
| services | array | yes | Services offered, plain words. |
| trade | string | yes | Trade, e.g. 'plumbing', 'electrical', 'hvac', 'handyman'. |
| website | string | – | Optional public website URL. |
No output schema declared.
No examples provided.
search_pros ~108
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.
| Name | Type | Req | Description |
|---|---|---|---|
| location | string | yes | City name or ZIP code where the work is. |
| service | string | – | Optional service keyword, e.g. 'water heaters'. |
| trade | string | yes | Trade to find, e.g. 'plumbing'. |
No output schema declared.
No examples provided.
send_job_request ~243
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.
| Name | Type | Req | Description |
|---|---|---|---|
| access_notes | string | – | Optional: gate codes, dogs, parking, access constraints. |
| description | string | yes | Plain-language description of the problem / work. |
| homeowner_contact | string | yes | Phone number or email the pro can reach the homeowner at. |
| homeowner_name | string | yes | – |
| job_type | string | yes | Short job type, e.g. 'water heater leaking'. |
| listing_id | string | yes | – |
| property_city | string | yes | – |
| property_zip | string | yes | – |
| urgency | string | yes | – |
No output schema declared.
No examples provided.
update_request_status ~81
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.
| Name | Type | Req | Description |
|---|---|---|---|
| listing_id | string | yes | – |
| listing_key | string | yes | – |
| new_status | string | yes | – |
| request_id | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Home-Services Agent Network MCP server?
Home-Services Agent Network is a hosted endpoint at https://agent-network-gold.vercel.app/, 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 · agent-network-gold.vercel.app
claude mcp add --transport http com-joeygeorgeplumbing-home-services-agent-netwo 'https://agent-network-gold.vercel.app/'
What is the Home-Services Agent Network MCP server?
Home-Services Agent Network is an MCP server listed in the public MCP registry as com.joeygeorgeplumbing/home-services-agent-network. Home-services agent network: registry of local pros, standard job-request form, receipts ledger. This page covers its hosted endpoint (https://agent-network-gold.vercel.app).
Is the Home-Services Agent Network MCP server safe to use?
Home-Services Agent Network scores 62 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 Home-Services Agent Network MCP server expose?
Home-Services Agent Network exposes 7 tools: register_business, search_pros, get_listing, send_job_request, check_inbox, and 2 more. Their descriptions and schemas cost roughly 903 tokens of context every time the server is loaded.
Does the Home-Services Agent Network MCP server require authentication?
No. We connected to Home-Services Agent Network without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Home-Services Agent Network MCP server still maintained?
Home-Services Agent Network 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.