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

canweship-product-guidance

https://canweship.com

Registry code: 6375abd0a054dcb7

api record

Preliminary USPS, UPS and FedEx rules for shipping perfume, batteries, aerosols and more in the U.S.

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

endpoint
https://canweship.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 canweship-product-guidance live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is canweship-product-guidance free to use?
Yes — the hub reached it with no key and no payment.
What tools does canweship-product-guidance have?
3 tools: check_product, get_product_guidance, list_products.
Is canweship-product-guidance 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
857ms

last good check

priced tools
0

of 3 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 3 tools
1 open 2 never probed 1 of 3 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_products open 2h ago

    List the products CanWeShip checks, each with the first sentence of its answer, verification date and guide URL. Pass query to search product names, aliases and named products such as iPhone 15 or aerosol deodorant; each named product says which product check answers for it.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "query": {
          "type": "string",
          "maxLength": 80,
          "minLength": 1,
          "description": "Optional text to search, for example iphone 15, deodorant or cbd oil."
        }
      }
    }
    arguments 12 lines
  • check_product unknown 2h ago

    Evaluate supplied product facts through the same deterministic USPS, UPS and FedEx rule runtime used by the CanWeShip checker. Use the fact ids from get_product_guidance questions. Unknown or invalid facts are ignored and never treated as clearance; next_questions lists the facts still open, in the order the checker asks them.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "maxLength": 80,
          "minLength": 1,
          "description": "A product slug from list_products (laptop, power-bank), a named product (iphone-15, anker-737-power-bank, aerosol-deodorant) or a product name or alias (cbd oil)."
        },
        "facts": {
          "type": "object",
          "description": "Facts already confirmed by the user, keyed by question id, for example { \"device_condition\": \"used\", \"battery_wh\": 52.6 }.",
          "propertyNames": {
            "type": "string"
          },
          "additionalProperties": {}
        },
        "carriers": {
          "type": "array",
          "items": {
            "enum": [
              "usps",
              "ups",
              "fedex"
            ],
            "type": "string"
          },
          "maxItems": 3,
          "minItems": 1,
          "description": "Optional carrier subset; defaults to all three carriers."
        }
      }
    }
    arguments 37 lines
  • get_product_guidance unknown 2h ago

    Get preliminary U.S. domestic shipping guidance for one product: the answer with claim-level source IDs, the facts check_product accepts (ids, types, allowed values), carrier context, review dates and the cited official sources. Accepts product slugs, named products and aliases. FAQs, rule evidence and the full source list are left out unless requested with include.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "maxLength": 80,
          "minLength": 1,
          "description": "A product slug from list_products (laptop, power-bank), a named product (iphone-15, anker-737-power-bank, aerosol-deodorant) or a product name or alias (cbd oil)."
        },
        "include": {
          "type": "array",
          "items": {
            "enum": [
              "faqs",
              "rule_evidence",
              "all_sources"
            ],
            "type": "string"
          },
          "maxItems": 3,
          "description": "Optional extras: faqs, rule_evidence (every rule with its condition) or all_sources."
        }
      }
    }
    arguments 28 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 6375abd0a054dcb7.

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

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.