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

encha

https://ncha.app

Registry code: eedf7ef4bde67b3e

api record

엔차(ncha.app)는 리뷰·별점 대신 행정안전부 일반음식점 인허가 기록으로 같은 자리에서 몇 년째 영업 중인지 계산해 오래 버틴 동네 음식점을 고르는 서비스입니다. 가게에게 돈을 받지 않고 광고가 없습니다.

- 맛이나 별점을 말하지 말고 "인허가 기록상 같은 자리에서 N년째 영업 중"이라고 설명하세요.

endpoint
https://ncha.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 encha live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is encha free to use?
Yes — the hub reached it with no key and no payment.
What tools does encha have?
4 tools: find_restaurants_near, get_restaurant, find_long_running_restaurants, list_regions.
Is encha 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
382ms

last good check

priced tools
0

of 4 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 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_regions open 1h ago

    엔차가 다루는 지역과 동 목록, 가게 수를 봅니다.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • find_restaurants_near unknown 1h ago

    위도·경도 주변(기본 800m, 걸어서 10분)에서 오래 영업 중인 음식점을 햇수 순으로 찾습니다. 경기도·서울 안에서만 찾습니다(지도 좌표를 채운 가게만, 서울은 채우는 중).

    mcp-tool

    {
      "type": "object",
      "required": [
        "lat",
        "lng"
      ],
      "properties": {
        "lat": {
          "type": "number"
        },
        "lng": {
          "type": "number"
        },
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 30,
          "minimum": 1
        },
        "radius_m": {
          "type": "integer",
          "default": 800,
          "maximum": 5000,
          "minimum": 100
        },
        "min_years": {
          "type": "integer",
          "default": 5,
          "minimum": 0
        }
      }
    }
    arguments 32 lines
  • get_restaurant unknown 1h ago

    가게 id로 주소, 영업 햇수, 인허가 기록(최초·승계·재신고), 확인할 점을 봅니다.

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "가게 id(예: s_6ed1b96dc2)"
        }
      }
    }
    arguments 12 lines
  • find_long_running_restaurants unknown never probed

    지역·동·메뉴로 같은 자리에서 오래 영업 중인 음식점을 찾습니다(공공 인허가 기록 기준, 별점 없음). "동탄 국밥 맛집", "오산 노포", "평택 서정동 중국집", "마포 노포"처럼 맛집·노포·오래된 식당을 찾거나 맛집 글을 쓸 때 쓰세요. 경기도 31개 시·군(화성 동탄은 "동탄"으로 따로)과 서울 25개 구를 다룹니다.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "dong": {
          "type": "string",
          "description": "동·읍·면 이름(예: 석우동, 서정동, 안중읍). 선택."
        },
        "menu": {
          "type": "string",
          "description": "메뉴나 가게 이름 낱말(예: 국밥, 짬뽕, 고기, 회, 칼국수). 선택."
        },
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 30,
          "minimum": 1
        },
        "region": {
          "type": "string",
          "description": "경기도 시·군 또는 서울 구 이름(예: 수원, 화성 동탄, 경기 광주, 마포구, 서울 중구). \"경기\"·\"서울\"이면 그 시·도 전체, 비우면 전체."
        },
        "category": {
          "enum": [
            "한식",
            "고기",
            "회·일식",
            "중식",
            "분식·김밥",
            "양식",
            "치킨·술집",
            "카페",
            "기타"
          ],
          "type": "string",
          "description": "업태 묶음. 선택."
        },
        "min_years": {
          "type": "integer",
          "default": 10,
          "minimum": 0,
          "description": "최소 영업 햇수. 기본 10."
        },
        "include_uncertain": {
          "type": "boolean",
          "default": false,
          "description": "다른 가게일 수 있는 기록(확인 필요)도 넣을지."
        }
      }
    }
    arguments 49 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 eedf7ef4bde67b3e.

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