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

jangbogi

https://jangbogi.getnunchi.app

Registry code: 211355770af18cca

api record

장보기 — 미리 계산해 둔 주간 식단·장바구니(마켓컬리)를 읽어 온다. 계산하지 않는다. 먼저 사용자에게 인원(1~5)·1인 1끼 예산(원)·이번 주 끼니 수(1~7)를 묻고, 세 값을 모두 들은 뒤 get_plan 을 부른다. 묻지 않은 칸에 기본값을 넣지 마라. 예산은 3000·5000·7000 중 가까운 단계(중간값은 낮은 쪽)로 서버가 보낸다 — budget_bucket 과 requested_budget 을 둘 다 사용자에게 알려라. 범위 확인은 list_options. include_recipes=true 는 사용자가 조리법을 물을 때만 쓴다. 알레르기·제외 재료는 반영되지 않았다. 결제는 사용자가 직접 한다.

endpoint
https://jangbogi.getnunchi.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 jangbogi live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is jangbogi free to use?
Yes — the hub reached it with no key and no payment.
What tools does jangbogi have?
2 tools: get_plan, list_options.
Is jangbogi 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
797ms

last good check

priced tools
0

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

    고를 수 있는 인원·예산 단계·끼니 수 범위, 예산 단계 규칙, 파일 주소 규칙, 현재 발행본 정보(회차·주차·묶음 수), 고지를 돌려준다.

    mcp-tool

    {
  "type": "object",
  "title": "list_optionsArguments",
  "properties": {}
}
    arguments 5 lines
  • get_plan unknown 1h ago

    미리 계산해 둔 이번 주 저녁 식단과 마켓컬리 장바구니(plan.json)를 돌려준다. 서버는 계산하지 않고 발행본 파일 하나를 읽는다. people = 인원(1~5), budget_per_meal = 1인 1끼 예산(원 — 3000·5000·7000 중 가까운 단계로 맞추고, 중간값은 낮은 단계), meals = 이번 주 끼니 수(1~7). 범위 밖 값은 고치지 않고 error 를 돌려준다. include_recipes = true 면 그 주 조리법을 함께 돌려준다(기본 false).

    mcp-tool

    {
  "type": "object",
  "title": "get_planArguments",
  "required": [
    "people",
    "budget_per_meal",
    "meals"
  ],
  "properties": {
    "meals": {
      "type": "integer",
      "title": "Meals"
    },
    "people": {
      "type": "integer",
      "title": "People"
    },
    "budget_per_meal": {
      "type": "integer",
      "title": "Budget Per Meal"
    },
    "include_recipes": {
      "type": "boolean",
      "title": "Include Recipes",
      "default": false
    }
  }
}
    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 211355770af18cca.

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

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.