World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 104 tools.
AI integrity standards, benchmarks, and EU AI Act-aligned Tier 0 model certification
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
검사 3/5 통과 · 내가 묻는 내용은 제작자 서버(aioq.org)를 거쳐요 · ✓ 명령 확인 2026년 11월 13일
먼저: 어떤 AI를 쓰시나요?
쓰는 앱을 고르면 아래에 단계가 나옵니다.
Claude에 연결할 수 있어요 · 약 2분
키 필요 없음, 설치 필요 없음 · claude.ai나 데스크톱 앱에서 한 번 설정하면 채팅에서 쓸 수 있어요 · 무료 계정은 1개까지 · Team/Enterprise는 소유자(Owner)가 추가
CustomizeConnectors
여기서 복사해 Claude의 같은 이름 칸에 붙여 넣고 Continue를 누르세요
Aiohttps://aioq.org/mcpClaude가 찾은 로그인 설정 화면에서 Continue를 누르고 · Authentication은 제작자 안내대로(Sign in now, Sign in when needed, No sign in) 고른 뒤 Add를 누르세요
+ConnectorsAio
Aio을 써서 나에게 무엇을 해 줄 수 있는지 알려 주고, 하나 해 봐✓ Claude가 Aio을 쓰고 있다고 하거나 답에 Aio 도구 이름이 나오면 연결된 거예요
메뉴 이름은 2026년 11월 11일에 Anthropic 도움말에서 확인 · 앱 버전에 따라 화면이 조금 다를 수 있어요
ChatGPT 연결은 요금제에 따라 달라요
전체 MCP: 웹 ChatGPT Business, Enterprise, Edu · Pro: 읽기/가져오기 권한으로 연결, 데이터를 바꾸는 도구는 안 될 수 있어요 · Plus: 공식 문서 미확인, 플러그인 화면에 사용자 지정 MCP 추가 항목이 보이면 시도해 볼 수 있어요 · 웹만
Plugins+Add custom MCP server
이름을 넣고 Connection에 주소를 붙여 넣은 뒤 경고에 체크하고 Create as a plugin을 누르세요
Aiohttps://aioq.org/mcp새 채팅을 열고 입력 전에 플러그인 목록에서 Aio을 고르세요
Aio을 써서 나에게 무엇을 해 줄 수 있는지 알려 주고, 하나 해 봐✓ ChatGPT가 Aio을 쓰고 있다고 하거나 답에 Aio 도구 이름이 나오면 연결된 거예요
메뉴 이름은 2026년 11월 11일에 OpenAI 도움말에서 확인 · 앱 버전에 따라 화면이 조금 다를 수 있어요
Claude Code에 연결할 수 있어요 · 약 2분
키 필요 없음, 설치 필요 없음
Mac: Command+스페이스를 누르고 Terminal 입력 · Windows: PowerShell 열기
claude mcp add --transport http --scope user aio https://aioq.org/mcpAio이 목록에 있고 연결됨으로 보이면 돼요
Aio을 써서 나에게 무엇을 해 줄 수 있는지 알려 주고, 하나 해 봐✓ Claude Code가 Aio을 쓰고 있다고 하거나 답에 Aio 도구 이름이 나오면 연결된 거예요
메뉴 이름은 2026년 11월 11일에 Anthropic 도움말에서 확인 · 앱 버전에 따라 화면이 조금 다를 수 있어요
Cursor에 연결할 수 있어요 · 약 2분
키 필요 없음, 설치 필요 없음
Aio을 써서 나에게 무엇을 해 줄 수 있는지 알려 주고, 하나 해 봐✓ Cursor가 Aio을 쓰고 있다고 하거나 답에 Aio 도구 이름이 나오면 연결된 거예요
메뉴 이름은 2026년 11월 11일에 Cursor 도움말에서 확인 · 앱 버전에 따라 화면이 조금 다를 수 있어요
VS Code에 연결할 수 있어요 · 약 2분
키 필요 없음, 설치 필요 없음
Aio을 써서 나에게 무엇을 해 줄 수 있는지 알려 주고, 하나 해 봐✓ VS Code가 Aio을 쓰고 있다고 하거나 답에 Aio 도구 이름이 나오면 연결된 거예요
메뉴 이름은 2026년 11월 11일에 VS Code 도움말에서 확인 · 앱 버전에 따라 화면이 조금 다를 수 있어요
Windsurf, Zed, Gemini CLI 같은 다른 MCP 앱은 추가 방법이 저마다 달라요. 앱 목록에서 확인하세요
웹으로 연결하는 앱용 주소
https://aioq.org/mcpJSON 설정은 아래 “개발자용”에 있어요
Claude Code
claude mcp add --transport http --scope user aio https://aioq.org/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"aio": {
"url": "https://aioq.org/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"aio": {
"type": "http",
"url": "https://aioq.org/mcp"
}
}
}이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
이 서버의 연결 방식과 각 앱의 공식 문서를 바탕으로 했어요. 2026년 11월 10일 확인.
인터넷으로 연결하는 앱
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
도구 이름과 설명은 서버가 2026년 11월 11일에 알려 준 그대로예요. 우리가 아니라 제작자가 쓴 글이고, 일반 텍스트로만 보여 드려요.
list_papersList every paper published by AIO — id, track, year, bilingual (en/ko) title and abstract, and an absolute PDF URL. All papers are CC BY 4.0; cite as "AIO — AI Integrity Organization, https://aioq.org, CC BY 4.0".
get_paperFetch one AIO paper by id (e.g. "paper-h"), with its bilingual abstract, absolute PDF URL, and a ready-to-paste citation. CC BY 4.0.
get_benchmark_distributionJudgment distributions from the AIO 20003 benchmark: per model, the value (L4), evidence (L3), and source (L2) win-rate hierarchies, reliability figures (TRR, PCS), and links to the raw JSON. Omit "model" to get every measured model. CC BY 4.0.
get_bench_itemsFetch the public forced-choice item set of the agent-submitted benchmark track: 105 items per layer (L4 values, L3 evidence, L2 sources), each a scenario in which two variables lead to opposite conclusions. There is no answer key — the measurement is which variable a system choos
submit_bench_runSubmit answers to the agent-track item set from get_bench_items. Requires an AIO agent key with the `bench:submit` scope — the run is attributed to the model, version, and operator the key was issued to, not to anything declared here. A layer must be answered in full (105 items)
get_framework_vocabularyThe machine-readable AIO Framework vocabulary: 19 value codes, 10 evidence codes, 10 source codes, the context axes (domain, scope, reversibility, time horizon), the AIO 20002 record grammar, and a JSON Schema for one record line. Use this to emit or validate AIO 20002 records. C
list_standards_packsList the standards packs — versioned formalizations of external reference norms (e.g. the EU AI Act) into AIO Framework hierarchy values. A pack is AIO's own formalization of a norm; a Tier 0 measurement against it yields a score report, not certification, and nothing is endorsed
get_standards_packFetch one standards pack by id, including the full per-provision V/E/S mapping. Pass "version" to pin a specific pack version; score reports always reference {id}@{version}. CC BY 4.0.
register_for_certificationRegister a model for AIO Tier 0 measurement. Tier 0 is free of charge, but registration of the model (name and version) and the operator (name and email) is required — a measurement whose model version and accountable operator do not appear in the public registry carries no weigh
get_eval_itemsFetch the public item set for a standards pack — the Gate A half of AIO Tier 0. Each item carries a bilingual scenario and question, the provision of the reference norm it is derived from, a response format (ves-code / ves-ranking / choice), and a weight. Expected hierarchies are
start_eval_attemptStart one AIO Tier 0 attempt and receive the exam paper: the public Gate A items plus the Gate B items drawn for this attempt from a private, rotating variant pool (3 per mapped provision, expected answers, provenance, and — since methodology v2-draft — the provision label withhe
submit_evalSubmit Tier 0 answers for automatic scoring. Pass the `attemptId` from start_eval_attempt together with the answers to BOTH gates in one `answers` array, each keyed by the `id` exactly as it was served (Gate B ids are opaque per-attempt handles) — that is the only path to a score
verify_certificationVerify an AIO registry record by id. Two kinds exist and both verify here: a SCORE REPORT (id "AIO-S0-…"), which is what Tier 0 issues today — the Gate A and Gate B scores, the per-provision breakdown, the measurement conditions, and a descriptive reference band, with no pass or
list_rfcsList the AIO public RFCs — the public comment periods in which a contested standards-pack or methodology decision is put out for comment before it is treated as settled. Each entry carries its status, its comment window, what it is about, and where to comment. Review windows foll
get_rfcFetch one public RFC by id (e.g. "rfc-2026-001"), including every agenda item in full, the reference documents, the decision if one has been recorded, and how to submit a comment. Use this before submit_rfc_comment so the comment answers an agenda item that is actually open. CC B
submit_rfc_commentSubmit a comment on an open AIO public RFC. Requires a real name and a working email address: the comment becomes part of a public review record, so an unattributable comment carries no weight. The email address is stored so AIO can reach the commenter about this RFC and is never
aio_lookup_referenceAsk the AIO Commons reference dataset kr-lnpd@0.9 (Korea Legal Normative Priority Dataset) which of two AIO values Korean statutes put first in a given domain. kr-lnpd@0.9 is the legacy September 2026 statute edition: it is grounded in statutes only, not court decisions. The curr
aio_lookup_org_priorityAsk one organization’s own norm file which of two AIO values it declared first, with the workshop record behind it (rule id, strength, declaration date, declared condition) and how that declaration lines up with the national legal norms (aligned_with / departs_from). A declaratio
list_contribution_tasksList the first contribution tasks of the AIO shared project on conditional value priorities: each task's id, type (check a case summary against its original, propose a missing condition, point out what a value code cannot express), question, status, and the observed cases it uses
get_contribution_taskFetch one contribution task in full — question, materials, a format example (not an actual finding), completion criteria, public scope — together with the evidence for each case it uses, kept in separate layers: the data observation (one stored model response to one hypothetical
submit_contributionSubmit one contribution to an AIO shared-project task. Call this ONLY when the user has asked you to submit, and only with text the user wrote or explicitly approved for this task — never upload the user's private conversations, documents, or model responses on your own, and set
get_contribution_statusCheck one contribution with the contributionId and receiptToken returned by submit_contribution: its status (pending, in_review, needs_revision, accepted = reflected, not_accepted = not reflected), the reviewer's response — a request for changes or the reason it was or was not re
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 13일 점검
질문하고, 팁을 나누고, 안 되는 점을 알려 주세요. "도움이 됨"이 많은 순서예요.
아직 리뷰가 없어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 5개 중 3개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.
제작자의 클라우드에서 실행돼요. 설치 없이 인터넷으로 연결하지만, 보내는 내용은 제작자의 서버를 거쳐요.
GitHub 저장소는 마지막으로 27일 전 변경됐고, 최신 버전(0.2.0)은 3개월 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. URL로 연결되므로 원격 MCP를 받는 앱에서도 쓸 수 있어요. 예: 웹 ChatGPT(Business 이상은 전체 MCP, Pro는 읽기 전용).
같은 카테고리에는: World Monitor, Claude Flow, Windmill
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:↓ 주간 다운로드i★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 104 tools.
AI orchestration with hive-mind swarms, neural networks, and 87 MCP tools for enterprise dev.
Run Windmill scripts and flows and manage jobs, schedules, resources and variables.
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
Machine-readable mirror of the open standards published by AIO — AI Integrity Organization, an international standards body established as a Swiss association in Geneva (UID CHE-469.997.903).
Everything here is also served live from https://aioq.org. This repository exists so the same files can be read, diffed, cited, and vendored without depending on an HTTP endpoint staying up.
License: [CC BY 4.0](LICENSE). Attribution string: AIO — AI Integrity Organization, https://aioq.org, CC BY 4.0
AI integrity, in AIO's framing, has three distinct failure modes, and AIO works on the first:
The AIO Framework encodes one judgment as one line:
C:MED/IXi | V:Bec<Sda | E:Exp<Gui | S:Usr<Pro
Context, then the value (V), evidence (E), and source (S) hierarchies behind that judgment, where < reads "outranked by". No user content is carried — the line records *why*, not *what*.
| Path | What it is |
|---|---|
vocabulary/aio-00011.json | The AIO 00011 common vocabulary: 39 V/E/S codes, the context axes, and the AIO 20002 record grammar with its JSON Schema. Snapshot of GET https://aioq.org/api/framework/vocabulary. |
standards-packs/*.json (×15 + EU) | Waves 1-3 formalization drafts (draft-unverified — single-pass seed, dual verification pending): NIST AI RMF, the Korean AI Framework Act (current consolidation 법률 제21311호), the CoE Framework Convention (not yet in force — EU sole ratification), the China Generative AI Interim Measures, the EU GPAI Code of Practice, the OECD AI Principles (2024 consolidation), California TFAIA (SB 53), the China AI-content labeling Measures, the G7 Hiroshima Code of Conduct, and the UNESCO Recommendation on the Ethics of AI (license-constrained: short-quote footprint only). Each entry carries verbatim, machine-checked provenance quotes. |
standards-packs/eu-ai-act-v0.2.json | The AIO formalization of the EU AI Act: per-provision V/E/S mapping, each entry carrying a verbatim quote from the official text, a rationale, a retrieval date, and its own verification status. |
standards-packs/schema.json | JSON Schema for a standards pack. A new norm is a data file, not code. |
standards-packs/FORMALIZATION_METHODOLOGY.md | How a legal text becomes a pack, and what the status ladder means. |
item-banks/eu-ai-act.public.json | The Tier 0 public item bank — 12 items, including their expected answers. See the note below; this is deliberate. |
item-banks/agent-track-v0.public.json | The agent-submitted benchmark track item bank v0.2 — 315 forced-choice dilemmas (105 per layer: L2 sources, L3 evidence, L4 values). There is no answer key by design: each item is a forced choice between two variables, and the measurement is the choice distribution itself. The review block records the six-round quality review that produced v0.2; one item carries an explicit reviewNote. |
item-banks/eu-ai-act.gateb-commitment.json | Commitment hashes for the private Tier 0 Gate B item pool (96 items): per-item sha256 plus an Ed25519-signed snapshot hash. The items themselves are private by design (seeded-random serving); this file lets anyone verify post hoc that served items existed before their test. Retired items are disclosed at /content/bench-items/eu-ai-act.gateb-retired.json on aioq.org as the pool rotates. |
verify/verify-certificate.mjs | Standalone Ed25519 verifier for an issued certificate. No npm dependencies. |
Tier 0 is self-assessment on a fully public item set. Publishing the expected hierarchies is not a leak — it is the design. A Tier 0 score is a floor, not a gaming-resistant measurement: it records that a model *could* answer by the criteria it declared. Hiding the key would buy a false sense of rigour while making the measurement unreproducible by anyone but AIO. Gaming resistance is what higher, proctored tiers with private item banks are for.
The live API serves the same bank with the answer key stripped, so that a submission flow cannot trivially read it back: GET https://aioq.org/api/eval/items?pack=eu-ai-act.
A standards pack is AIO's own formalization of an external reference norm — a reading of a legal text expressed in the AIO vocabulary, so that it can be measured. It is not the norm, not an official reading of it, and not produced with the involvement of the body that issued it.
Every pack carries a status on a fixed ladder:
draft-unverified → draft-verified → rfc → active
The EU AI Act pack is currently draft-verified: every mapping entry has a verbatim quote from the official text and a recorded retrieval date, but the pack has not yet been through the public RFC process. Certificates issued on a pack that is not active carry that fact — the field basisStatus sits inside the signed payload, so it cannot be reconstructed after the fact.
Certificates issued by AIO are signed with Ed25519. The public key is published at https://aioq.org/.well-known/aio-cert-key.json, so verification never requires trusting — or even reaching — an AIO server beyond fetching the record itself.
node verify/verify-certificate.mjs AIO-C0-XXXXXXXX
node verify/verify-certificate.mjs AIO-C0-XXXXXXXX --json node verify/verify-certificate.mjs --file ./saved-response.json --key ./pinned-key.json
Exit codes: 0 verified and currently valid · 1 verified but expired or revoked · 2 signature missing or mismatched · 3 usage or network error.
The one rule that matters: take verification.canonicalPayload from the API response verbatim as the signed message. Do not re-serialize it. It is already canonical — signed fields only, keys sorted by code point, no whitespace — and re-serializing it is the usual cause of a false negative. The script also rebuilds that payload from the certificate's own fields and compares, which catches a server that shows you one thing and signs another.
A verified signature proves only that AIO issued that exact record. It says nothing about whether the model is safe to deploy.
No authentication, CORS open, JSON, all CC BY 4.0.
| Endpoint | |||
|---|---|---|---|
| https://aioq.org/api/openapi.json | OpenAPI 3.1 description of everything below | ||
GET /api/framework/vocabulary | the vocabulary in this repo, live · `?layer=V\ | E\ | S · ?format=schema` |
GET /api/standards-packs · /{id} | packs with their full per-provision mapping | ||
GET /api/eval/items?pack=eu-ai-act | Tier 0 items, answer key stripped, plus the scoring methodology | ||
POST /api/eval/submit | submit answers; deterministic scoring, signed certificate on a pass | ||
GET /api/certifications/registry | every certificate issued | ||
GET /api/certifications/{certId} | one certificate, with its signature check and offline instructions | ||
GET /api/certifications/{certId}/badge.svg | badge, drawn live so it cannot outlive its own truth | ||
GET /api/benchmarks/agent-track/items | the agent-track item bank in this repo, live · `?layer=L2\ | L3\ | L4` |
POST /api/benchmarks/agent-track/submit | submit a run (requires an agent key with the bench:submit scope) | ||
GET /.well-known/aio-cert-key.json | Ed25519 public keys | ||
GET /.well-known/mcp/server.json | MCP server metadata |
MCP server — https://aioq.org/mcp, Streamable HTTP, protocol 2025-06-18, stateless, no auth.
{ "mcpServers": { "aio": { "type": "http", "url": "https://aioq.org/mcp" } } }
13 tools: search_atlas, list_papers, get_paper, get_benchmark_distribution, get_framework_vocabulary, list_standards_packs, get_standards_pack, register_for_certification, get_eval_items, submit_eval, verify_certification, get_bench_items, submit_bench_run.
Index for crawlers and agents: https://aioq.org/llms.txt
| Repository | |
|---|---|
AI-Integrity/AIO20002 | The full specification of AIO 20002, the reasoning record standard — prose spec, examples, tests. The machine-readable grammar in vocabulary/aio-00011.json here implements it. |
AI-Integrity/aio-prism-benchmark | The PRISM benchmark — multi-layer win-rate rankings across frontier models. |
Naming convention: AIO repositories hold the specification of a single numbered standard; kebab-case repositories hold data, tools, and benchmarks.
Errors in a standard, a mapping, or a benchmark result are handled through the public RFC process, not private correction: https://aioq.org/en/rfc. That is the point of publishing the provenance alongside every mapping entry — a disagreement should be arguable against a quote and a date, not against an assertion.
Issues and pull requests here are welcome for the mirror itself (broken files, stale snapshots, verifier bugs). Substantive changes to a standard go through the RFC process.
AIO certifies conformance to AIO's own formalization of a reference norm. A certificate is not an endorsement by the body that issued that norm (the European Union does not endorse, review, or participate in the EU AI Act pack), is not a legal conformity assessment, and creates no presumption of conformity under any regulation.
Contact: info@aioq.org · Site: https://aioq.org