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

vibecart

https://vibecart.vercel.app

Registry code: 3cdb3b656f0c94dc

api record

VibeCart exposes a compact trusted-catalog and multi-item checkout toolset for generic MCP clients; UCP-aware clients use /ucp/mcp for durable cart/order protocol capabilities.

endpoint
https://vibecart.vercel.app/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 vibecart live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is vibecart free to use?
Yes — the hub reached it with no key and no payment.
What tools does vibecart have?
4 tools: vibecart.create_checkout, vibecart.get_product, vibecart.list_products, vibecart.get_integration_instructions.
Is vibecart 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
99.6%

90 days 99.5%· all time 99.5%

latency
570ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 399 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
payments & commerce payment infrastructure
used for
  • list catalog products
  • get product price
  • create hosted checkout url
  • get checkout integration instructions
takes → gives
data → data, web pages
tools
3 reads1 changes data
_ 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
2 open 2 never probed 2 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.

  • vibecart.list_products reads open 20h ago

    Lists products from the configured trusted merchant catalog. Use the returned stable IDs for product lookup or checkout.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • vibecart.get_integration_instructions reads open 20h ago

    Returns concise Next.js App Router guidance for installing VibeCart with trusted catalog pricing, multi-item checkout, and the shared MCP endpoint.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • vibecart.create_checkout changes data unknown never probed

    Creates a hosted checkout URL for one or more trusted merchant-catalog products. Legacy productId + quantity input remains supported; new integrations should use items[]. VibeCart resolves all prices server-side. This can contact Stripe but never charges by itself; the customer must complete Stripe Checkout.

    mcp-tool

    {
  "type": "object",
  "oneOf": [
    {
      "required": [
        "productId"
      ]
    },
    {
      "required": [
        "items"
      ]
    }
  ],
  "properties": {
    "items": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "productId"
        ],
        "properties": {
          "quantity": {
            "type": "integer",
            "default": 1,
            "maximum": 99,
            "minimum": 1,
            "description": "Whole-number quantity from 1 through 99."
          },
          "productId": {
            "type": "string",
            "minLength": 1,
            "description": "A trusted server-side catalog product ID."
          }
        },
        "additionalProperties": false
      },
      "maxItems": 50,
      "minItems": 1,
      "description": "Trusted product IDs and quantities for a multi-item checkout."
    },
    "quantity": {
      "type": "integer",
      "default": 1,
      "maximum": 99,
      "minimum": 1,
      "description": "Legacy single-product quantity."
    },
    "productId": {
      "type": "string",
      "minLength": 1,
      "description": "Legacy single-product input. Use either productId or items, not both."
    }
  },
  "additionalProperties": false
}
    arguments 57 lines
  • vibecart.get_product reads unknown 20h ago

    Looks up one product and its trusted USD-cent price from the configured merchant catalog. Does not access Stripe or create a checkout.

    mcp-tool

    {
  "type": "object",
  "required": [
    "productId"
  ],
  "properties": {
    "productId": {
      "type": "string",
      "minLength": 1,
      "description": "A stable ID returned by vibecart.list_products."
    }
  },
  "additionalProperties": false
}
    arguments 14 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 3cdb3b656f0c94dc.

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