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

wegravel

https://www.wegravel.com

Registry code: 168a71ac358d430c

api record

WeGravel delivers bulk soil, sand, gravel and mulch in Florida only. A price needs the 5-digit ZIP code of the delivery address and a material slug from list_materials. For an area and a depth, calculate_quantity returns orderQuantity and unit for get_prices. get_prices returns one total in US dollars with delivery included. compare_prices prices several materials at one ZIP code. A ZIP code outside Florida has no price. quoteUrl opens the quote form on wegravel.com with the job filled in.

endpoint
https://www.wegravel.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 wegravel live?
Yes — it answered the hub's last check (checked 12h ago). It answered 100% of checks over the last 30 days.
Is wegravel free to use?
Yes — the hub reached it with no key and no payment.
What tools does wegravel have?
4 tools: get_prices, compare_prices, calculate_quantity, list_materials.
Is wegravel 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
569ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 2 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 4 tools
1 open 3 never probed 1 of 4 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_materials open 12h ago

    List the materials WeGravel sells in bulk, delivered in Florida (soils, sands, gravel, mulch). Returns the slug, name, category, description, and `unit` of each material: the unit WeGravel sells it by ("yd3" = cubic yards, "ton" = tons). Call this first to get valid slugs for the other tools.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {},
      "additionalProperties": false
    }
    arguments 6 lines
  • get_prices unknown never probed

    Get the delivered price of one material, for one quantity, at one US ZIP code. Only Florida ZIP codes are served; other ZIPs return an error. `total` is the full price in USD with delivery included; nothing is added to it. `fullLoad` is the price of one full truck load, the lowest price per unit. `notes` are facts about this order: the minimum order, how the price compares with a full load, and whether WeGravel prices the job by hand. `quoteUrl` opens the WeGravel quote form with the material, ZIP, and quantity filled in. `pageUrl` is the WeGravel page for this material in the delivery city (null when there is no page).

    mcp-tool

    {
      "type": "object",
      "required": [
        "material",
        "quantity",
        "zip"
      ],
      "properties": {
        "zip": {
          "type": "string",
          "pattern": "^\\d{5}$",
          "description": "5-digit US ZIP code of the delivery address. Florida only."
        },
        "unit": {
          "enum": [
            "yd3",
            "ton"
          ],
          "type": "string",
          "description": "Unit of `quantity`: \"yd3\" (cubic yards) or \"ton\". Default: the unit the material sells by (see list_materials)."
        },
        "material": {
          "type": "string",
          "description": "Material slug from list_materials (a material name also works)."
        },
        "quantity": {
          "type": "number",
          "title": "Quantity",
          "description": "Quantity to deliver, in `unit`. Must be greater than 0.",
          "exclusiveMinimum": 0
        }
      },
      "additionalProperties": false
    }
    arguments 34 lines
  • compare_prices unknown 12h ago

    Compare the delivered price of several materials at one Florida ZIP code, cheapest first. Each row is the price of one full truck load, in USD with delivery included, in the unit the material sells by. An entry of `materials` can be a slug, a name, or a word that names a group ("mulch", "sand", "crushed stone"): a group word adds every material that matches it. At most 12 materials are priced in one call; `notPriced` lists the rest with the reason. Use get_prices for the price of an exact quantity.

    mcp-tool

    {
      "type": "object",
      "required": [
        "materials",
        "zip"
      ],
      "properties": {
        "zip": {
          "type": "string",
          "pattern": "^\\d{5}$",
          "description": "5-digit US ZIP code of the delivery address. Florida only."
        },
        "materials": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "title": "maxItems(12)",
          "maxItems": 12,
          "minItems": 1,
          "description": "Material slugs, names, or group words such as \"mulch\"."
        }
      },
      "additionalProperties": false
    }
    arguments 25 lines
  • calculate_quantity unknown 12h ago

    Calculate how much material a rectangular area needs. Give the length and width in feet and the depth in inches. The result gives cubic yards and tons, and `orderQuantity` in the unit WeGravel sells the material by, with a safety margin and the minimum order included. Pass `orderQuantity` and `unit` to get_prices to get the price and the quote link.

    mcp-tool

    {
      "type": "object",
      "required": [
        "material",
        "lengthFt",
        "widthFt",
        "depthInches"
      ],
      "properties": {
        "widthFt": {
          "type": "number",
          "title": "Width",
          "description": "Width of the area, in feet.",
          "exclusiveMinimum": 0
        },
        "lengthFt": {
          "type": "number",
          "title": "Length",
          "description": "Length of the area, in feet.",
          "exclusiveMinimum": 0
        },
        "material": {
          "type": "string",
          "description": "Material slug from list_materials (a material name also works)."
        },
        "depthInches": {
          "type": "number",
          "title": "Depth",
          "description": "Depth of the material, in inches.",
          "exclusiveMinimum": 0
        }
      },
      "additionalProperties": false
    }
    arguments 34 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 168a71ac358d430c.

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

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.