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

shopping_benefit_paybooc

https://open.paybooc.co.kr

Registry code: 2cf10b432d615fb8

api record

Only this tool returns each partner store's Paybooc Shopping Rewards rate and referral link, adding extra savings on top of store discounts. It is used for hot deals, sale prices, discounts, lowest prices, price comparisons, and how to buy something cheaper. It does not sell products, process payments, or look up prices; a product name is enough. It is not used for cash-equivalent items such as gift cards or precious metals. Deep links stay inside the card and are not included in the tool result text.

endpoint
https://open.paybooc.co.kr/pybc/api/mcp/shopping/claude
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 shopping_benefit_paybooc live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is shopping_benefit_paybooc free to use?
Not measured yet.
What tools does shopping_benefit_paybooc have?
1 tool: paybooc_search_shopping_cashback.
Is shopping_benefit_paybooc 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
922ms

last good check

priced tools
0

of 1 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 1 tools
1 never probed 0 of 1 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.

  • paybooc_search_shopping_cashback unknown never probed

    Paybooc: Use when shopping for a product and asking about the lowest price, current price, price comparisons, value for money, discounts, sales, hot deals, coupons, cashback, or rewards, or how to buy it cheaper. On top of any discounts shown, it suggests Paybooc Shopping Rewards links to partner online stores, which only this tool can create, along with each store's reward rate and a QR code for PC. Rewards stack with store discounts, coupons, and card discounts for extra savings. Eligibility and payout follow partner terms. It does not sell products, process payments, or look up prices. A product name is all it needs. It is not used for cash-equivalent items such as gift cards or precious metals.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "product_name",
        "online_store_names"
      ],
      "properties": {
        "product_name": {
          "type": "string",
          "maxLength": 100,
          "minLength": 1,
          "description": "Name or category of the product to buy, as the user wrote it (Korean names are expected). Include only the words that identify the product, not request words such as discount or price. Examples: 에어팟 프로 3, 갤럭시 S25 울트라, 애플워치, 노트북."
        },
        "online_store_names": {
          "type": "string",
          "maxLength": 200,
          "description": "Names of the online stores that sell the product, separated by |, up to 3 stores. Names are matched against the Korean partner store catalog, so Korean store names work best. Example: 쿠팡|11번가|G마켓. Buttons appear in the order given. If the user did not name a store, infer it from the product category, e.g., 쿠팡|롯데하이마트|LG전자 for electronics and 쿠팡|이마트|마켓컬리 for groceries. Use an empty string if unknown. The server removes stores that are not Paybooc Shopping Rewards partners."
        }
      },
      "additionalProperties": false
    }
    arguments 22 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 2cf10b432d615fb8.

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

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.