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.

codeitso (코드잇소)

REMOTE · CODEITSO.YOORRARD.WORKERS.DEV

Read-only catalog of app-building materials: fonts, APIs, MCP servers, libraries, templates, data.

+3 this week 72 Trust /100

Last scanned (22 hours ago)

Scores higher than 57% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Developer Tools

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
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability76
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1432 tokens (~204/item across 7 items; 7 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 Management40
  • Stability observed for 12 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 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
  • Authorization
  • 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.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

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.

  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 9 Nov 26 67

    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://codeitso.yoorrard.workers.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=yoorrard.workers.dev CN=YE1,O=Let's Encrypt,C=US 14 Oct 2026 12 Jan 2027 ECDSA 256 ECDSA-SHA384 668e63292295606790c355b8f66ee0a656f
SANs: *.yoorrard.workers.dev, yoorrard.workers.dev
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of codeitso.yoorrard.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
workers.dev. 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
x-content-type-options nosniff

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://codeitso.yoorrard.workers.dev/mcp Verified 200
http (plaintext) http://codeitso.yoorrard.workers.dev/mcp Inconclusive 405
MCP tools · 7 exposed · ~1,205 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
codeitso_browse ~124

Browse the catalog tree: no arguments lists the 6 categories and subcategories with counts; category lists its subcategories; subcategory lists its materials by popularity (default), name or recent update.

NameTypeReqDescription
categorystring–Top-level category id.
limitinteger–Materials per page.
offsetinteger–Materials to skip (next page).
response_formatstring–'json' for structured output; default compact markdown.
sortstring–Order of materials.
subcategorystring–Subcategory id to list.

No output schema declared.

No examples provided.

codeitso_find_models ~401

Find and compare AI models (LLMs) by price per 1M tokens, context window, input/output types and features, from models.dev data refreshed daily. Default: major model makers (OpenAI, Anthropic, Google, xAI, DeepSeek, Mistral and others); scope=direct: every model maker; provider: one provider incl. hosts and routers such as openrouter. Returns model ids, prices, context, release date, the provider material id, and a link to the comparison page on the codeitso website.

NameTypeReqDescription
include_deprecatedboolean–Include models whose support has ended.
inputsarray–Input types every result must accept besides text.
limitinteger–Models per page.
max_input_pricenumber–Max input price, USD per 1M tokens.
max_output_pricenumber–Max output price, USD per 1M tokens.
min_contextinteger–Min context window in tokens.
offsetinteger–Models to skip (next page).
open_weightsboolean–Only open-weight models.
outputsarray–Output types every result must produce, e.g. image.
providerstring–One provider id, e.g. 'anthropic', 'openai', 'openrouter'.
querystring–Words in the model name or id, e.g. 'claude sonnet', 'gemini flash'.
reasoningboolean–Only reasoning models.
response_formatstring–'json' for structured output; default compact markdown.
scopestring–Without provider: 'major' or 'direct' (every company that makes its own models).
sortstring–'newest', cheapest first by 'input_price' or 'output_price', or largest 'context'.
tool_callingboolean–Only models with tool calling.

No output schema declared.

No examples provided.

codeitso_get_kits ~82

List codeitso starter kits (curated material sets for app types such as school info apps, games, office tools) or, with kit_id, one kit's materials and suggested build outline.

NameTypeReqDescription
kit_idstring–Kit id from the kit list.
response_formatstring–'json' for structured output; default compact markdown.

No output schema declared.

No examples provided.

codeitso_get_materials ~137

Full details for 1-5 materials by id: official URL, license, source description, install command and snippet from the source, required auth, popularity, related materials, plus how to connect an MCP server (remote URLs, packages), API facts (base URL, env var names, OpenAPI spec, free tier) and font facts (weights, Korean subset). AI API providers include current models with prices per 1M tokens.

NameTypeReqDescription
idsarrayyesMaterial ids, e.g. "google-fonts:roboto".
response_formatstring–'json' for structured output; default compact markdown.

No output schema declared.

No examples provided.

codeitso_make_cart_link ~132

Make a codeitso cart link (https://codeitso.yoorrard.workers.dev/cart#s=…) from chosen material ids, optionally with a chosen AI model per AI API provider. Opening it puts the materials in the person's cart on the website, with previews, licenses, install commands and a prompt builder. Ids are not looked up; unknown ones show as missing there.

NameTypeReqDescription
itemsarrayyesMaterials in order: id from other codeitso tools, optional model id for AI API providers.
response_formatstring–'json' for structured output; default compact markdown.

No output schema declared.

No examples provided.

codeitso_open_cart ~128

Read a codeitso cart share link a person made on the website (https://codeitso.yoorrard.workers.dev/cart#s=…): its materials with chosen AI model, official URL, install command, MCP remote URL and required auth. Only the part after # is read.

NameTypeReqDescription
limitinteger–Materials per page.
offsetinteger–Materials to skip (next page).
response_formatstring–'json' for structured output; default compact markdown.
sharestringyesThe share link, or its fragment starting with s=.

No output schema declared.

No examples provided.

codeitso_search ~201

Search codeitso's catalog of public app-building materials (fonts, colors, icons, UI kits, MCP servers, agent skills, public APIs incl. Korean public data, open-source libraries, templates, datasets) by keywords in Korean or English, e.g. '급식 API', 'chart library'. Returns ranked materials with id, one-line summary, license, popularity and key facts, plus matching subcategories. Install commands and full details: codeitso_get_materials.

NameTypeReqDescription
categorystring–Only this top-level category.
limitinteger–Results per page.
offsetinteger–Results to skip (next page).
querystringyesKeywords in Korean or English.
response_formatstring–'json' for structured output; default compact markdown.
subcategorystring–Only this subcategory id from codeitso_browse, e.g. fonts-ko, icons, mcp, kr-public.

No output schema declared.

No examples provided.

Install

How do I install the codeitso (코드잇소) MCP server?

codeitso (코드잇소) is a hosted endpoint at https://codeitso.yoorrard.workers.dev/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 · codeitso.yoorrard.workers.dev

# add to Claude Code
claude mcp add --transport http yoorrard-codeitso 'https://codeitso.yoorrard.workers.dev/mcp'
Common questions

What is the codeitso (코드잇소) MCP server?

codeitso (코드잇소) is an MCP server listed in the public MCP registry as io.github.yoorrard/codeitso. Read-only catalog of app-building materials: fonts, APIs, MCP servers, libraries, templates, data. This page covers its hosted endpoint (https://codeitso.yoorrard.workers.dev/mcp).

Is the codeitso (코드잇소) MCP server safe to use?

codeitso (코드잇소) scores 72 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 codeitso (코드잇소) MCP server expose?

codeitso (코드잇소) exposes 7 tools: codeitso_search, codeitso_get_materials, codeitso_browse, codeitso_get_kits, codeitso_open_cart, and 2 more. Their descriptions and schemas cost roughly 1,205 tokens of context every time the server is loaded.

Does the codeitso (코드잇소) MCP server require authentication?

No. We connected to codeitso (코드잇소) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the codeitso (코드잇소) MCP server still maintained?

codeitso (코드잇소) 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 codeitso (코드잇소) MCP server?

VerifyMCP ran 12 checks on codeitso (코드잇소), covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about codeitso (코드잇소): HTTPS. 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.