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

mcpmoa

https://mcpmoa.com

Registry code: e0365dbf409c941d

api record

MCP모아(mcpmoa.com)의 한국 MCP 서버 디렉토리를 조회하는 읽기 전용 서버입니다. 사용자가 한국 서비스·데이터(공공데이터, DART, 법령, 카카오·네이버, 지도, 날씨, 커머스, 협업툴)용 MCP를 찾거나 설치하려 할 때 search_servers로 후보를 찾고 get_server로 설치 설정과 보안 점검 결과를 확인하세요. 설치를 권할 때는 보안 점검 status와 notes를 함께 안내하세요.

endpoint
https://mcpmoa.com/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 mcpmoa live?
Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
Is mcpmoa free to use?
Yes — the hub reached it with no key and no payment.
What tools does mcpmoa have?
4 tools: get_server, list_global_official, list_categories, search_servers.
Is mcpmoa 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
600ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 3 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
3 open 1 never probed 3 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_global_official open 3h ago

    노션·깃허브·피그마 등 해외 서비스가 직접 운영하는 공식 MCP의 연결 방법과 주의점을 한국어로 돌려줍니다(한국 MCP 목록과 별도).

    mcp-tool

    {
      "type": "object",
      "properties": {
        "query": {
          "type": "string",
          "description": "서비스 이름(예: notion, github)"
        }
      },
      "additionalProperties": false
    }
    arguments 10 lines
  • list_categories open 3h ago

    MCP모아 분야(공공데이터·금융·법률 등)와 분야별 서버 수, 전체 보안 점검 요약을 돌려줍니다.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • search_servers open 3h ago

    MCP모아에 등록된 한국 MCP 서버를 검색합니다. 검색어는 이름·설명·태그·연동 API(DART, data.go.kr, 기상청 등)에 대해 찾습니다.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 50,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "description": "검색어(예: 법령, DART, 카카오, 부동산, hwp). 비우면 전체"
        },
        "category": {
          "enum": [
            "public-data",
            "finance",
            "law",
            "kakao-naver",
            "map-location",
            "weather",
            "commerce",
            "collaboration",
            "devtools"
          ],
          "type": "string",
          "description": "분야 slug로 거르기"
        },
        "safe_only": {
          "type": "boolean",
          "description": "보안 점검 '안전' 판정만"
        },
        "official_only": {
          "type": "boolean",
          "description": "운영사 공식 서버만"
        }
      },
      "additionalProperties": false
    }
    arguments 39 lines
  • get_server unknown never probed

    서버 한 개의 설명, 설치 설정(Claude Desktop 형식), 필요한 API 키, 보안 점검 결과(판정·데이터 흐름·유의사항)를 돌려줍니다.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "search_servers 결과의 slug"
        }
      },
      "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 e0365dbf409c941d.

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