wells-us
Registry code: 9815893dc54ad4dd
Rural Home Pros: Find a water-well driller or septic contractor near you. Checked facts on services, emergency service, and estimates. Read-only. search_listings finds businesses with the filters of the site; get_listing returns every fact with the page it comes from and the date it was checked. Link the listing URL when you use a fact.
- endpoint
- https://ruralhomepros.com/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is wells-us live?
- Yes — it answered the hub's last check (checked 2h ago). It answered 98% of checks over the last 30 days.
- Is wells-us free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does wells-us have?
- 5 tools: compare_listings, get_listing, list_places, search_listings, list_categories.
- Is wells-us safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 98.6%· all time 98.6%
last good check
of 5 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- used for
- find a water well driller nearby
- find a septic contractor
- compare contractor listings
- takes → gives
- text → data
- tools
- 5 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
list_places reads open 24h ago
The places with listings and their numbers: the top level, or the places inside a parent place.
{ "type": "object", "properties": { "parent": { "type": "string", "description": "The path of a place from an earlier answer, for its towns" }, "category": { "enum": [ "well-drillers", "septic-contractors" ], "type": "string" } }, "additionalProperties": false }arguments 17 linessearch_listings reads open 24h ago
Find listings of Rural Home Pros with the filters of the site, 20 per page, most checked facts first. list_categories names the filters and values of each category.
{ "type": "object", "properties": { "page": { "type": "integer", "minimum": 1 }, "sort": { "enum": [ "relevance", "name", "checked" ], "type": "string" }, "query": { "type": "string", "description": "Free text: a name or a word" }, "where": { "type": "string", "description": "A place: town, region, or state (a part of the name is enough)" }, "filters": { "type": "object", "properties": { "services": { "type": "array", "items": { "enum": [ "well_drilling", "well_pump", "well_inspection", "water_treatment", "geothermal", "well_abandonment", "septic_install", "septic_pumping", "septic_inspection", "septic_repair", "aerobic_systems", "excavation" ], "type": "string" }, "description": "Services: any of these values" }, "financing": { "type": "boolean", "description": "Financing offered" }, "ngwa_member": { "type": "boolean", "description": "NGWA member or certified" }, "family_owned": { "type": "boolean", "description": "Family owned" }, "free_estimates": { "type": "boolean", "description": "Free estimates" }, "emergency_service": { "type": "boolean", "description": "24/7 emergency service" } }, "additionalProperties": false }, "category": { "enum": [ "well-drillers", "septic-contractors" ], "type": "string", "description": "Category, default: well-drillers" } }, "additionalProperties": false }arguments 81 lineslist_categories reads open 24h ago
The categories with their number of listings and their filters, each with its values.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linescompare_listings reads unknown 5h ago
Two to five listings side by side, fact by fact.
{ "type": "object", "required": [ "listings" ], "properties": { "listings": { "type": "array", "items": { "type": "string", "description": "The listing URL or its slug (the last part of the URL)." }, "maxItems": 5, "minItems": 2 } }, "additionalProperties": false }arguments 18 linesget_listing reads unknown 5h ago
One listing with every fact, the page each fact comes from, and the date it was checked.
{ "type": "object", "required": [ "listing" ], "properties": { "listing": { "type": "string", "description": "The listing URL or its slug (the last part of the URL)." } }, "additionalProperties": false }arguments 13 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id9815893dc54ad4dd.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/9815893dc54ad4dd/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/9815893dc54ad4dd?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.