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

Nord Trail Reference Store

https://ready.expandingweb.com

Registry code: da41f515fa581e91

api record

Demonstration storefront operated by Expanding Web. Catalog tools are live; orders are not fulfilled. If anything here stops you from completing a task, call report_problem and say what happened — it is read by a human and it is how this store gets fixed.

endpoint
https://ready.expandingweb.com/mcp
protocol
streamable-http ·2025-11-25
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 Nord Trail Reference Store live?
Yes — it answered the hub's last check (checked 1h ago). It answered 98% of checks over the last 30 days.
Is Nord Trail Reference Store free to use?
Yes — the hub reached it with no key and no payment.
What tools does Nord Trail Reference Store have?
6 tools: report_problem, get_product, check_stock, lookup_catalog, list_products, search_catalog.
Is Nord Trail Reference Store 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
98.4%

90 days 99%· all time 99%

latency
106ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 303 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
payments & commerce shopping & products
used for
  • search an outdoor gear catalog
  • check stock and price
  • report a problem with the store
takes → gives
text → data
tools
5 reads1 sends messages
note
demo or test
_ 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 6 tools
3 open 3 never probed 3 of 6 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.

  • lookup_catalog reads open 23h ago

    UCP 2026-04-08 catalog lookup: resolve one or more product or variant identifiers (slug or SKU) to UCP product objects.

    mcp-tool

    {
  "type": "object",
  "required": [
    "ids"
  ],
  "properties": {
    "ids": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Product ids (slugs, e.g. nord-trail-boot) or variant ids (SKUs, e.g. MGN-204)."
    }
  }
}
    arguments 15 lines
  • list_products reads open 15h ago

    List every product in the Nord Trail catalog with slug, SKU, price and URL.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • search_catalog reads open 15h ago

    UCP 2026-04-08 catalog search. Free-text query over the catalog; returns UCP product objects in structuredContent. Call with no query to list everything.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Free text, e.g. \"waterproof jacket\". Omit to return the whole catalog."
    }
  }
}
    arguments 9 lines
  • report_problem sends messages unknown never probed

    Tell this store that something stopped you from completing a task: a product you could not price, a variant you could not find, a request that was refused. Read by a human. Use it instead of giving up silently — a store only learns that an agent failed if the agent says so.

    mcp-tool

    {
  "type": "object",
  "required": [
    "summary"
  ],
  "properties": {
    "kind": {
      "enum": [
        "blocked_by_edge",
        "checkout_blocked",
        "not_found",
        "server_error",
        "timeout",
        "missing_data",
        "search_dead_end",
        "mcp_error",
        "manifest_error",
        "other"
      ],
      "type": "string",
      "description": "Closest category; omit if unsure."
    },
    "path": {
      "type": "string",
      "description": "URL or path where it happened, if there was one."
    },
    "contact": {
      "type": "string",
      "description": "Optional address to reply to."
    },
    "summary": {
      "type": "string",
      "description": "What you were trying to do and what stopped you, in your own words."
    },
    "expected": {
      "type": "string",
      "description": "What you expected to find instead."
    }
  }
}
    arguments 40 lines
  • get_product reads unknown 15h ago

    One product: the UCP product object in structuredContent, and the schema.org Product JSON-LD the product page publishes as text.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "description": "Product slug, e.g. nord-trail-boot, or a variant SKU."
    },
    "slug": {
      "type": "string",
      "description": "Deprecated alias for id."
    }
  }
}
    arguments 13 lines
  • check_stock reads unknown 23h ago

    Live stock and price for a SKU.

    mcp-tool

    {
  "type": "object",
  "required": [
    "sku"
  ],
  "properties": {
    "sku": {
      "type": "string",
      "description": "Product SKU, e.g. MGN-204"
    }
  }
}
    arguments 12 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 da41f515fa581e91.

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

_ also on expandingweb.com 1 entry

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.