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

valumech

https://valumech.com

Registry code: 720bd210d73f15cd

api record

Valumech is a read-only valuation reference for humanoid robots, robot dogs, home robots, robot vacuums, mobile manipulators and service robots. Every price, specification and availability state is sourced or null — a null is a fact about the evidence, never a gap to fill. Used values are illustrative models, not appraisals; keep the `warning`/`basis` fields and the `retainedPercent` label with the number. Preserve `verifiedAt`, `checkedAt`, `fxDate` and native currencies when relaying figures. Do not convert or round beyond `approximateUsd`. Tools never navigate, quote, order or pay. Obtain…

endpoint
https://valumech.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 it live, free and safe measured by this hub
Is valumech live?
Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
Is valumech free to use?
Yes — the hub reached it with no key and no payment.
What tools does valumech have?
5 tools: get_purchase_options, compare_robots, search_robot_catalog, get_robot_price, estimate_used_value.
Is valumech 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
339ms

last good check

priced tools
0

of 5 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 5 tools
5 never probed 0 of 5 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.

  • get_purchase_options unknown never probed

    Return dated official and affiliate buying links recorded by Valumech for one robot. This never opens a retailer, submits data, adds to cart, or purchases.

    mcp-tool

    {
      "type": "object",
      "required": [
        "robot"
      ],
      "properties": {
        "robot": {
          "type": "string",
          "maxLength": 100,
          "minLength": 1,
          "description": "Catalog ID or a sufficiently specific maker and model name."
        },
        "region": {
          "enum": [
            "US"
          ],
          "type": "string",
          "default": "US",
          "description": "Buyer region. The first pilot currently supports US offers."
        }
      },
      "additionalProperties": false
    }
    arguments 23 lines
  • compare_robots unknown 3h ago

    Compare two Valumech robots using sourced prices and specifications plus clearly labeled modeled depreciation. Returns a canonical or interactive comparison URL.

    mcp-tool

    {
      "type": "object",
      "required": [
        "firstRobot",
        "secondRobot"
      ],
      "properties": {
        "firstRobot": {
          "type": "string",
          "maxLength": 100,
          "minLength": 1,
          "description": "First catalog ID or sufficiently specific robot name."
        },
        "secondRobot": {
          "type": "string",
          "maxLength": 100,
          "minLength": 1,
          "description": "Second catalog ID or sufficiently specific robot name."
        }
      },
      "additionalProperties": false
    }
    arguments 22 lines
  • search_robot_catalog unknown 3h ago

    Search Valumech's read-only robot catalog by words, category, market status, or a maximum approximate USD price. At least one filter is required.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "default": 5,
          "maximum": 5,
          "minimum": 1,
          "description": "Maximum results to return, from 1 through 5."
        },
        "query": {
          "type": "string",
          "maxLength": 100,
          "description": "Robot, maker, capability, body form, or use-case words."
        },
        "status": {
          "enum": [
            "shipping",
            "preorder",
            "announced",
            "discontinued"
          ],
          "type": "string",
          "description": "Commercial status recorded by Valumech."
        },
        "category": {
          "enum": [
            "humanoid",
            "robot-dog",
            "home-robot",
            "robot-vacuum",
            "mobile-manipulator",
            "service-robot"
          ],
          "type": "string",
          "description": "Valumech's semantic robot category."
        },
        "maxPriceUsd": {
          "type": "number",
          "maximum": 10000000,
          "minimum": 0,
          "description": "Maximum new price normalized approximately to USD."
        }
      },
      "additionalProperties": false
    }
    arguments 46 lines
  • get_robot_price unknown never probed

    Return Valumech's sourced new-price record, configurations, evidence date, availability, modeled used-value summary, and canonical page for one robot.

    mcp-tool

    {
      "type": "object",
      "required": [
        "robot"
      ],
      "properties": {
        "robot": {
          "type": "string",
          "maxLength": 100,
          "minLength": 1,
          "description": "Catalog ID or a sufficiently specific maker and model name."
        }
      },
      "additionalProperties": false
    }
    arguments 15 lines
  • estimate_used_value unknown 3h ago

    Calculate Valumech's illustrative used-value range for a delivered, publicly priced robot. This is a modeled placeholder, not an appraisal or resale comp.

    mcp-tool

    {
      "type": "object",
      "required": [
        "robot",
        "ageYears",
        "condition"
      ],
      "properties": {
        "robot": {
          "type": "string",
          "maxLength": 100,
          "minLength": 1,
          "description": "Catalog ID or a sufficiently specific maker and model name."
        },
        "ageYears": {
          "type": "number",
          "maximum": 20,
          "minimum": 0,
          "description": "Robot age in years; decimals such as 0.5 are allowed."
        },
        "condition": {
          "enum": [
            "mint",
            "good",
            "fair",
            "heavy"
          ],
          "type": "string",
          "description": "Current condition using Valumech's four condition bands."
        }
      },
      "additionalProperties": false
    }
    arguments 33 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 720bd210d73f15cd.

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

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.