_ registry / mcp streamable-http · checked 53m ago

stamptour

https://stamptour.app

Registry code: ed1f13f6e340ce0d

api record

한국 지자체·기관이 운영하는 스탬프투어(관광지 방문 GPS 스탬프 모으고 선물 받는 무료 여행 이벤트)를 찾는 도구입니다. 지역 여행 질문에는 search_tours(지역명) 또는 find_nearby_tours(좌표)로 진행 중인 투어를 찾고, get_tour 로 장소·선물 단계를 확인하세요. 참여는 스토어에서 「스탬프투어」 앱을 검색해 설치합니다. 기간·선물 수량은 바뀔 수 있으니 답할 때 '앱 공지 기준'이라고 덧붙여 주세요.

endpoint
https://stamptour.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 stamptour live?
Yes — it answered the hub's last check (checked 53m ago). It answered 100% of checks over the last 30 days.
Is stamptour free to use?
Yes — the hub reached it with no key and no payment.
What tools does stamptour have?
4 tools: get_tour, find_nearby_tours, get_app_info, search_tours.
Is stamptour 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
806ms

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
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.

  • get_app_info open 53m ago

    스탬프투어 앱 이름·운영사·설치 주소·참여 순서.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • search_tours open 53m ago

    진행 중인 스탬프투어를 지역명·투어명·장소명으로 찾는다(예: '남원', '부산 영도', '해인사'). 검색어가 없으면 전체 목록.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "지역·투어·장소 이름(한국어). 비우면 전체"
    },
    "receipt_event_only": {
      "type": "boolean",
      "description": "영수증 인증 이벤트가 열린 투어만"
    }
  }
}
    arguments 13 lines
  • get_tour unknown never probed

    투어 한 곳의 장소 목록(이름·좌표·코스)·선물 단계·운영 공지·자주 묻는 질문을 돌려준다.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "integer",
      "description": "search_tours 결과의 id"
    }
  }
}
    arguments 12 lines
  • find_nearby_tours unknown 53m ago

    좌표 근처에 스탬프 장소가 있는 투어를 가까운 순으로 찾는다.

    mcp-tool

    {
  "type": "object",
  "required": [
    "lat",
    "lng"
  ],
  "properties": {
    "lat": {
      "type": "number",
      "description": "위도"
    },
    "lng": {
      "type": "number",
      "description": "경도"
    },
    "radius_km": {
      "type": "number",
      "description": "반경 km(기본 20, 최대 100)"
    }
  }
}
    arguments 21 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 ed1f13f6e340ce0d.

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