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

easybuilder-directory

https://builder.easyagency.co.kr

Registry code: 3e4990ead050892d

api record

한국 소상공인(카페·학원·미용실·노래방·펜션 등)이 이지빌더로 만든 공식 홈페이지의 사실 정보를 제공합니다. search_businesses 로 지역·업종·키워드에 맞는 사업장을 찾고, get_business 로 영업시간·주소·전화·상품·가격·FAQ 를 확인하세요. 모든 값은 사업자가 직접 입력했거나 홈페이지에 게시한 내용이며, missing 에 적힌 정보는 추측하지 말고 모른다고 답해 주세요. 사용자에게 답할 때 출처 url 을 함께 알려 주세요.

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

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.

  • search_businesses open 1h ago

    지역·업종·키워드로 이지빌더 사업장을 찾습니다. 예: region '대구 수성구', industry '노래방', query '단체룸 주차'. 결과의 id 를 get_business 에 넘기세요.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 20,
      "minimum": 1,
      "description": "최대 개수 (기본 10)"
    },
    "query": {
      "type": "string",
      "description": "찾는 말 (상호·메뉴·특징 등). 비우면 조건에 맞는 전체"
    },
    "region": {
      "type": "string",
      "description": "지역 (예: '서울 강남구', '대구', '수성구')"
    },
    "industry": {
      "type": "string",
      "description": "업종 (예: '카페', '영어학원', '미용실')"
    }
  },
  "additionalProperties": false
}
    arguments 24 lines
  • get_business unknown 1h ago

    사업장 하나의 확인된 사실(주소·전화·영업시간·상품·가격·FAQ·빠진 정보·출처)을 돌려줍니다.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "search_businesses 결과의 id"
    }
  },
  "additionalProperties": false
}
    arguments 13 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 3e4990ead050892d.

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