reliance-trenchless
https://reliancetrenchless.com
Registry code: 5b56bf3309e50676
Use Reliance Trenchless Technology's published catalogue and buyer guides to answer product and project-enquiry questions. Always link to the canonical source returned by a tool. Do not invent price, stock, lead time, certification, compatibility, or a project-specific operating setting. Some brochure and spreadsheet values differ; preserve the source note and ask Reliance to confirm the applicable document. Product matching is a shortlist for enquiry, not an engineering approval or installation procedure. For a project decision, ask for measured dimensions, pipe material, service conditions,…
- endpoint
- https://reliancetrenchless.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 reliance-trenchless live?
- Yes — it answered the hub's last check (checked 11h ago). It answered 100% of checks over the last 30 days.
- Is reliance-trenchless free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does reliance-trenchless have?
- 6 tools: search_products, get_product, shortlist_products, compare_products, list_product_families, prepare_technical_enquiry.
- Is reliance-trenchless 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 100%· all time 100%
last good check
of 6 tools
- unknown → live
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_product_families open 11h ago
List the published product families and their canonical pages.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesprepare_technical_enquiry open 11h ago
Turn known project facts into a review checklist for Reliance. This tool does not send email or place an order.
{ "type": "object", "properties": { "task": { "type": "string" }, "product": { "type": "string" }, "quantity": { "type": "string" }, "targetDate": { "type": "string" }, "destination": { "type": "string" }, "pipeMaterial": { "type": "string" }, "pipeDiameterMm": { "type": "number", "exclusiveMinimum": 0 }, "defectOrIntendedTask": { "type": "string" }, "bypassOrFlowRequirements": { "type": "string" }, "pressureOrServiceConditions": { "type": "string" }, "accessAndInstallationConstraints": { "type": "string" }, "requiredStandardOrInspectionDocuments": { "type": "string" } }, "additionalProperties": false }arguments 43 linessearch_products unknown never probed
Find published Reliance products by task, product name, pipe application, or product family.
{ "type": "object", "required": [ "query" ], "properties": { "query": { "type": "string", "description": "Search terms such as repair packer, pipe plug, joint seal, testing, or mortar sprayer." }, "family": { "type": "string", "description": "Optional family slug from list_product_families." }, "maxResults": { "type": "integer", "default": 5, "maximum": 10, "minimum": 1 } }, "additionalProperties": false }arguments 23 linesget_product unknown never probed
Return the published overview, technical guide, source notes, specification tables, and documents for one product.
{ "type": "object", "required": [ "product" ], "properties": { "product": { "type": "string", "description": "Product name, product ID, or canonical URL slug." } }, "additionalProperties": false }arguments 13 linesshortlist_products unknown never probed
Map a stated task to relevant Reliance product families. This returns enquiry candidates and missing information; it does not approve a model or operating procedure.
{ "type": "object", "required": [ "task" ], "properties": { "task": { "type": "string", "description": "The job, for example temporary isolation, bypass, testing, joint sealing, point repair, defect pretreatment, or manhole mortar rehabilitation." }, "pipeMaterial": { "type": "string" }, "bypassRequired": { "type": "boolean" }, "pipeDiameterMm": { "type": "number", "description": "Measured internal diameter at the work location, in mm.", "exclusiveMinimum": 0 }, "serviceConditions": { "type": "string" } }, "additionalProperties": false }arguments 27 linescompare_products unknown 11h ago
Compare two to four published products and expose the dimensions or operating details that still need confirmation.
{ "type": "object", "required": [ "products" ], "properties": { "products": { "type": "array", "items": { "type": "string" }, "maxItems": 4, "minItems": 2, "description": "Product names, IDs, or canonical URL slugs." } }, "additionalProperties": false }arguments 18 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 id5b56bf3309e50676.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/5b56bf3309e50676/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/5b56bf3309e50676?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.