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

baedang

https://baedang.info

Registry code: 30f5f41beb1cdcf9

api record

baedang.info의 한국·미국 배당 데이터를 조회합니다. 배당률은 최근 12개월 정기 분배금 합계 / 최신 가격(%) 기준입니다.

endpoint
https://baedang.info/api/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 baedang live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is baedang free to use?
Yes — the hub reached it with no key and no payment.
What tools does baedang have?
3 tools: get_security_detail, rank_securities, search_securities.
Is baedang 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
1,093ms

last good check

priced tools
0

of 3 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 3 tools
2 open 1 never probed 2 of 3 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.

  • rank_securities open 1h ago

    조건으로 걸러 배당률·배당 성장률·연속 증가 연수·규모 순으로 종목 순위를 냅니다.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "number",
          "description": "최대 결과 수 (기본 20, 최대 100)"
        },
        "market": {
          "enum": [
            "US",
            "KR"
          ],
          "type": "string"
        },
        "sortBy": {
          "enum": [
            "currentYield",
            "avgYield5Y",
            "dividendCagr5Y",
            "dividendCagr10Y",
            "growthStreakYears",
            "assetSize"
          ],
          "type": "string",
          "description": "정렬 기준 (기본 currentYield)"
        },
        "maxYield": {
          "type": "number",
          "description": "최대 현재 배당률(%)"
        },
        "minYield": {
          "type": "number",
          "description": "최소 현재 배당률(%)"
        },
        "securityType": {
          "type": "string",
          "description": "STOCK, ETF, REIT 등"
        },
        "maxCutCount10Y": {
          "type": "number",
          "description": "10년 내 최대 배당 삭감 횟수"
        },
        "paymentFrequency": {
          "enum": [
            "MONTHLY",
            "QUARTERLY",
            "SEMI_ANNUAL",
            "ANNUAL"
          ],
          "type": "string"
        },
        "minGrowthStreakYears": {
          "type": "number",
          "description": "최소 연속 배당 증가 연수"
        }
      }
    }
    arguments 57 lines
  • search_securities open 1h ago

    한국·미국 배당 종목을 티커, 영문명, 한글명으로 검색합니다. 대소문자를 구분하지 않습니다.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "number",
          "description": "최대 결과 수 (기본 10, 최대 50)"
        },
        "query": {
          "type": "string",
          "description": "티커 또는 종목명 일부 (예: SCHD, 리얼티인컴, 삼성전자)"
        },
        "market": {
          "enum": [
            "US",
            "KR"
          ],
          "type": "string",
          "description": "시장 필터 (생략하면 전체)"
        }
      }
    }
    arguments 24 lines
  • get_security_detail unknown 1h ago

    종목 하나의 상세 배당 정보(연도별 배당 이력, 배당 지급 내역, 총수익률 등)를 가져옵니다.

    mcp-tool

    {
      "type": "object",
      "required": [
        "market",
        "ticker"
      ],
      "properties": {
        "market": {
          "enum": [
            "US",
            "KR"
          ],
          "type": "string"
        },
        "ticker": {
          "type": "string",
          "description": "티커 (예: O, SCHD, 005930)"
        }
      }
    }
    arguments 20 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 30f5f41beb1cdcf9.

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

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.