_ registry / mcp http-sse · checked 53m ago

Kelvin

https://kelvin.openconverters.com

Registry code: 696204e12b43bc83

api record

Kelvin is a deterministic parts librarian over the TAS component catalogue (no LLM inside). Start with list_families, then describe_family for the exact field names before search_parts — an unknown filter field is an error, not ignored. part_details looks up one MPN; recommend_parts ranks parts for a requirement; cross_reference finds scored substitutes for an MPN; spec_distribution shows what is actually available. Values are SI base units. A part whose record does not state a field is excluded by a filter on it — absence is never reported as 0.

endpoint
https://kelvin.openconverters.com/mcp
protocol
http-sse ·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 Kelvin live?
Yes — it answered the hub's last check (checked 53m ago). It answered 100% of checks over the last 30 days.
Is Kelvin free to use?
Yes — the hub reached it with no key and no payment.
What tools does Kelvin have?
7 tools: describe_family, search_parts, spec_distribution, part_details, recommend_parts, cross_reference, list_families.
Is Kelvin 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
100%

90 days 100%· all time 100%

latency
146ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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 7 tools
1 open 6 never probed 1 of 7 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.

  • list_families open 53m ago

    Every component family in the TAS catalogue, with how many parts it holds and whether it has a deterministic selector. Start here.

    mcp-tool

    {
  "type": "object",
  "title": "list_familiesArguments",
  "properties": {}
}
    arguments 5 lines
  • describe_family unknown 53m ago

    The exact field names one family can be filtered, sorted and bucketed on, and the designRequirements keys its selector reads. Call this before search_parts on an unfamiliar family rather than guessing field names.

    mcp-tool

    {
  "type": "object",
  "title": "describe_familyArguments",
  "required": [
    "family"
  ],
  "properties": {
    "family": {
      "type": "string",
      "title": "Family"
    }
  }
}
    arguments 13 lines
  • search_parts unknown never probed

    Parametric search over one family: numeric ranges, categorical values, MPN substring and manufacturer, with optional facet counts. This is the catalogue question — 'what parts do we have that ...' — and needs no converter design.

    mcp-tool

    {
  "type": "object",
  "title": "search_partsArguments",
  "required": [
    "family"
  ],
  "properties": {
    "sort": {
      "anyOf": [
        {
          "type": "object",
          "additionalProperties": true
        },
        {
          "type": "null"
        }
      ],
      "title": "Sort",
      "default": null
    },
    "limit": {
      "type": "integer",
      "title": "Limit",
      "default": 25
    },
    "family": {
      "type": "string",
      "title": "Family"
    },
    "offset": {
      "type": "integer",
      "title": "Offset",
      "default": 0
    },
    "filters": {
      "anyOf": [
        {
          "type": "object",
          "additionalProperties": true
        },
        {
          "type": "null"
        }
      ],
      "title": "Filters",
      "default": null
    },
    "with_facets": {
      "type": "boolean",
      "title": "With Facets",
      "default": false
    }
  }
}
    arguments 54 lines
  • spec_distribution unknown never probed

    How one numeric spec is distributed across a filtered slice of a family — bucket counts (log or linear) plus how many parts state the value at all. Answers 'what is available' questions that a top-N list cannot.

    mcp-tool

    {
  "type": "object",
  "title": "spec_distributionArguments",
  "required": [
    "family",
    "field"
  ],
  "properties": {
    "log": {
      "type": "boolean",
      "title": "Log",
      "default": true
    },
    "field": {
      "type": "string",
      "title": "Field"
    },
    "family": {
      "type": "string",
      "title": "Family"
    },
    "buckets": {
      "type": "integer",
      "title": "Buckets",
      "default": 20
    },
    "filters": {
      "anyOf": [
        {
          "type": "object",
          "additionalProperties": true
        },
        {
          "type": "null"
        }
      ],
      "title": "Filters",
      "default": null
    }
  }
}
    arguments 41 lines
  • part_details unknown never probed

    One part by MPN: its extracted specs and, optionally, the full TAS catalogue record behind them (datasheet URL, mechanical drawing, provenance).

    mcp-tool

    {
  "type": "object",
  "title": "part_detailsArguments",
  "required": [
    "family",
    "mpn"
  ],
  "properties": {
    "mpn": {
      "type": "string",
      "title": "Mpn"
    },
    "family": {
      "type": "string",
      "title": "Family"
    },
    "manufacturer": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Manufacturer",
      "default": null
    },
    "include_record": {
      "type": "boolean",
      "title": "Include Record",
      "default": true
    }
  }
}
    arguments 35 lines
  • recommend_parts unknown never probed

    Kelvin's deterministic selector: rank real parts against a designRequirements block and return the candidates with the margins that ranked them. Same authority Kirchhoff and Heaviside select through — no LLM judgement, reproducible.

    mcp-tool

    {
  "type": "object",
  "title": "recommend_partsArguments",
  "required": [
    "family",
    "requirements"
  ],
  "properties": {
    "family": {
      "type": "string",
      "title": "Family"
    },
    "options": {
      "anyOf": [
        {
          "type": "object",
          "additionalProperties": true
        },
        {
          "type": "null"
        }
      ],
      "title": "Options",
      "default": null
    },
    "max_results": {
      "type": "integer",
      "title": "Max Results",
      "default": 12
    },
    "requirements": {
      "type": "object",
      "title": "Requirements",
      "additionalProperties": true
    },
    "include_envelope": {
      "type": "boolean",
      "title": "Include Envelope",
      "default": false
    }
  }
}
    arguments 42 lines
  • cross_reference unknown 53m ago

    Find substitutes for a part by MPN — the deterministic, program-only cross-reference the Kelvin web app runs: pre-gate the catalogue at the ranker's own reject edges, then score every candidate on value, ratings, footprint and mount type. No LLM judgement. An original whose own specs are incomplete can never yield a clean 'recommended'.

    mcp-tool

    {
  "type": "object",
  "title": "cross_referenceArguments",
  "required": [
    "family",
    "mpn"
  ],
  "properties": {
    "mpn": {
      "type": "string",
      "title": "Mpn"
    },
    "family": {
      "type": "string",
      "title": "Family"
    },
    "same_type": {
      "type": "boolean",
      "title": "Same Type",
      "default": true
    },
    "max_results": {
      "type": "integer",
      "title": "Max Results",
      "default": 12
    },
    "manufacturer": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Manufacturer",
      "default": null
    },
    "target_manufacturers": {
      "anyOf": [
        {
          "type": "array",
          "items": {
            "type": "string"
          }
        },
        {
          "type": "null"
        }
      ],
      "title": "Target Manufacturers",
      "default": null
    }
  }
}
    arguments 55 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 696204e12b43bc83.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/696204e12b43bc83/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/696204e12b43bc83/badge.svg)](https://brick.blue/agent/696204e12b43bc83?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
100%

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.