_ registry / mcp streamable-http · checked 2h ago

harness-atlas

https://qahxbracftdyarpzplzf.supabase.co

Registry code: 3a680fb0eb6bb34b

api record

Search 500+ wire-harness & cable-assembly manufacturers by country, industry, and capability.

from a public catalogue that lists it, not from the operator

endpoint
https://qahxbracftdyarpzplzf.supabase.co/functions/v1/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 it live, free and safe measured by this hub
Is harness-atlas live?
Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
Is harness-atlas free to use?
Yes — the hub reached it with no key and no payment.
What tools does harness-atlas have?
2 tools: find_alternative, find_manufacturer.
Is harness-atlas 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.
reachable
live
uptime, 30 days
99.2%

90 days 99%· all time 99%

latency
298ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 395 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • find wire harness manufacturers
  • cross-reference harness part numbers
takes → gives
text → data
tools
2 reads
_ usage and payments 30 days

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.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 2 tools
1 open 1 never probed 1 of 2 classified

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.

  • find_manufacturer reads open 14h ago

    Search the Harness Atlas directory of wire-harness and cable-assembly manufacturers. Filter by country, industry served, process capability, or name. Returns listed manufacturer profiles (location, website, industries, capabilities).

    mcp-tool

    {
      "type": "object",
      "properties": {
        "name": {
          "type": "string",
          "description": "Partial company name to match."
        },
        "limit": {
          "type": "integer",
          "default": 20,
          "maximum": 50,
          "minimum": 1
        },
        "country": {
          "type": "string",
          "description": "HQ country, e.g. 'Germany', 'Poland', 'China'."
        },
        "industry": {
          "enum": [
            "aerospace",
            "appliances",
            "automotive",
            "commercial-vehicles",
            "electronics",
            "energy",
            "hvac",
            "industrial",
            "marine",
            "medical",
            "off-road",
            "rolling-stock",
            "telecommunications"
          ],
          "type": "string",
          "description": "Industry the manufacturer serves."
        },
        "capability": {
          "enum": [
            "crimp_force_monitoring",
            "ultrasonic_welding",
            "soldering",
            "overmolding",
            "braiding",
            "twisting",
            "sealing_grommets",
            "heatshrink",
            "labeling_marking",
            "testing_continuity",
            "hipot",
            "functional_test",
            "hv_capable",
            "ipc_whma_620"
          ],
          "type": "string",
          "description": "Required process capability, e.g. 'hv_capable', 'ultrasonic_welding', 'ipc_whma_620'."
        }
      },
      "additionalProperties": false
    }
    arguments 59 lines
  • find_alternative reads unknown 14h ago

    Cross-reference a wire-harness component part number (connectors, terminals, seals, cable protection) against the XrefBase equivalence graph. Results are grouped by how strong the relationship is, and the groups are not interchangeable: `verified_replacements` are corroborated drop-in or manufacturer-superseded parts; `functional_equivalents` do the same job but need engineering review; `same_series` and `variants` are the same family in a different configuration and are NOT substitutes; `mates_with` is the counterpart connector the part plugs into, which is specifically not a substitute for it. Every claim carries a confidence level and, where one exists, a public source URL.

    mcp-tool

    {
      "type": "object",
      "required": [
        "part_number"
      ],
      "properties": {
        "part_number": {
          "type": "string",
          "description": "Manufacturer part number to cross-reference. Punctuation and case are normalised, so '1-967616-1' and '19676161' both match."
        },
        "manufacturer": {
          "type": "string",
          "description": "Optional original manufacturer name. Accepts known aliases ('TE', 'H+S'). Disambiguates when one MPN exists under several manufacturers."
        }
      },
      "additionalProperties": false
    }
    arguments 17 lines
_ try it through the hub, ceiling 0

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.

_ is this your agent? claim it: badge, payouts, history

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.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. 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.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 3a680fb0eb6bb34b.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/3a680fb0eb6bb34b/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/3a680fb0eb6bb34b/badge.svg)](https://brick.blue/agent/3a680fb0eb6bb34b?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.

_ how we know
card completeness
60%

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.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
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.

_ also on supabase.co 123 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

115 more sit on this domain. All of them.