Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.sw-woo/everyone-builder

REMOTE · EVERYONE-BUILDER.VERCEL.APP

Korean IT/AI news, contests, free courses, and how Korean outlets framed the same story differently

66 Trust /100

Last scanned (15 hours ago)

Scores higher than 51% of remote servers

Reachable. Last reached 21 Nov 2026.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability68
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1149 tokens (~191/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
  • Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 19 Nov 26 65

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://everyone-builder.vercel.app/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.vercel.app CN=WR1,O=Google Trust Services,C=US 31 Oct 2026 29 Jan 2027 RSA 2048 SHA256-RSA 9c5f0e6a35c955e113044c86848e4cd5
SANs: *.vercel.app
CN=WR1,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7fd9e2c2d2048a0474b627a26d0868a7
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of everyone-builder.vercel.app. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
app. DS published 23684 8 Verified
vercel.app. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=(), usb=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://everyone-builder.vercel.app/api/mcp Verified 200
http (plaintext) http://everyone-builder.vercel.app/api/mcp HTTPS enforced 308 https://everyone-builder.vercel.app/api/mcp
MCP tools · 6 exposed · ~960 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
draft_post ~307

에브리원 빌더 광장에 올릴 글의 **초안**을 만듭니다. 이 도구만으로는 공개되지 않습니다 — 돌려받은 주소를 사용자가 브라우저에서 열어 내용을 확인하고 직접 [게시] 를 눌러야 합니다. **반드시 사용자에게 그 주소를 그대로 보여 주고, 열어서 확인해 달라고 전해 주세요.** 사용자가 쓰려는 내용을 대신 정리하는 용도이며, 사용자 동의 없이 호출하지 마세요.

NameTypeReqDescription
authorNamestringyes화면에 보일 이름(닉네임 또는 기관명)
authorTypestring–기관이면 org (홈페이지 주소 필수, 광고로 표시됨)
authorUrlstring–기관 홈페이지 (org 일 때 필수)
bodystringyes본문. 사용자가 하려는 말을 그대로 담으세요
categorystringyesshow=만든 것 자랑 · team=팀원 구하기 · event=행사 알림 · hiring=채용 · talk=질문·토론
contactUrlstring–오픈채팅·신청폼 등 연락 주소
emailstringyes작성자 통보용. 공개되지 않습니다
linkUrlstring–소개할 제품·행사 주소
tagsarray–태그 최대 5개
titlestringyes제목

No output schema declared.

No examples provided.

free_courses ~148

지금 수강 신청할 수 있는 무료·국비 지원 온라인 강좌를 마감일 순으로 돌려줍니다 (K-MOOC 등 공공 API, 1,800여 개 중 모집 중인 것). 날짜는 **모집 마감일**이며 개강일과 다릅니다. query 로 주제를 좁힐 수 있습니다 (예: '파이썬', '데이터 분석').

NameTypeReqDescription
limitinteger–돌려받을 개수 (1~30, 기본 15). 넘기면 30에서 잘립니다
querystring–찾을 주제. 비우면 마감 임박순

No output schema declared.

No examples provided.

korea_it_news ~157

한국 IT·AI 뉴스의 최신 제목을 매체·링크와 함께 돌려줍니다. 20여 개 한국 IT 매체의 공개 RSS 를 모은 것으로, 한 매체가 목록을 독점하지 않게 섞어 줍니다. 본문은 제공하지 않습니다 — 반드시 원문 링크를 함께 보여 주세요. query 를 주면 그 말이 든 기사를 찾습니다 (예: '엔비디아', '오픈소스 LLM').

NameTypeReqDescription
limitinteger–돌려받을 개수 (1~30, 기본 15). 넘기면 30에서 잘립니다
querystring–찾을 말. 비우면 최신순

No output schema declared.

No examples provided.

media_comparison ~138

**같은 사건을 한국 매체들이 어떻게 다르게 썼는지** 비교해 줍니다. 여러 매체가 함께 다룬 사건을 묶고(우리 계산), 매체별 제목을 나란히 놓고, 제목들이 무엇을 앞세웠는지 분석한 한국어 글을 함께 줍니다(우리가 쓴 글이라 전문을 제공합니다). '이 뉴스 매체별로 어떻게 다르게 보도했어?' 같은 질문에 쓰세요. 다른 곳에서는 얻을 수 없는 자료입니다.

NameTypeReqDescription
limitinteger–사건 수 (1~10, 기본 5)

No output schema declared.

No examples provided.

open_competitions ~125

마감 전인 AI·개발 대회와 해커톤을 마감일·상금과 함께 돌려줍니다 (Kaggle · Devpost · K-Startup 등 공개 API). 국내 해커톤은 모아 주는 공개 API 가 없어 수집하지 못하므로, 대신 국내 해커톤·공모전을 모아 둔 사이트 12곳을 함께 안내합니다.

NameTypeReqDescription
limitinteger–돌려받을 개수 (1~30, 기본 15). 넘기면 30에서 잘립니다

No output schema declared.

No examples provided.

today_digest ~85

오늘 한국 IT 업계에 무슨 일이 있었는지 한국어로 정리한 글을 돌려줍니다. 우리가 모은 자료의 집계를 근거로 쓴 글이라 전문을 제공합니다. 오늘 글이 아직 없으면 어제 것을 주고 `isToday: false` 로 밝힙니다 — 그때는 날짜를 그대로 전해 주세요.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the io.github.sw-woo/everyone-builder MCP server?

io.github.sw-woo/everyone-builder is a hosted endpoint at https://everyone-builder.vercel.app/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · everyone-builder.vercel.app

# add to Claude Code
claude mcp add --transport http sw-woo-everyone-builder 'https://everyone-builder.vercel.app/api/mcp'
Common questions

What is the io.github.sw-woo/everyone-builder MCP server?

io.github.sw-woo/everyone-builder is an MCP server listed in the public MCP registry as io.github.sw-woo/everyone-builder. Korean IT/AI news, contests, free courses, and how Korean outlets framed the same story differently. This page covers its hosted endpoint (https://everyone-builder.vercel.app/api/mcp).

Is the io.github.sw-woo/everyone-builder MCP server safe to use?

io.github.sw-woo/everyone-builder scores 66 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.sw-woo/everyone-builder MCP server expose?

io.github.sw-woo/everyone-builder exposes 6 tools: korea_it_news, media_comparison, open_competitions, free_courses, today_digest, draft_post. Their descriptions and schemas cost roughly 960 tokens of context every time the server is loaded.

Does the io.github.sw-woo/everyone-builder MCP server require authentication?

No. We connected to io.github.sw-woo/everyone-builder without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.sw-woo/everyone-builder MCP server still maintained?

io.github.sw-woo/everyone-builder is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the io.github.sw-woo/everyone-builder MCP server?

VerifyMCP ran 12 checks on io.github.sw-woo/everyone-builder, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about io.github.sw-woo/everyone-builder: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.