# aio **Category:** ๐Ÿ’ป Developer Tools **Repository:** https://github.com/AI-Integrity/aio-standards **Views:** 0 **Installs:** 0 **Upvotes:** 0 **Directory Page:** https://allmcps.com/mcp/aio ## Description AI integrity standards, benchmarks, and EU AI Act-aligned Tier 0 model certification ## Claude Desktop Quick Installation Heuristic fallback โ€” verify the package name and runner against the repository README before running it. Uses `npx` (confidence: low): ```json "mcpServers": { "aio": { "command": "npx", "args": ["-y","aio"] } } ``` ## Documentation & README # aio-standards 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 . 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](https://github.com/AI-Integrity/aio-standards/blob/HEAD/LICENSE).** Attribution string: `AIO โ€” AI Integrity Organization, https://aioq.org, CC BY 4.0` --- ## What AIO measures AI integrity, in AIO's framing, has three distinct failure modes, and AIO works on the first: 1. **The compromise problem** โ€” the deliberate or structural compromise of training data and judgment criteria in pursuit of particular outcomes, at the stage where a response is produced. 2. **The use problem** โ€” misinterpretation or irresponsible application of a response after it enters society. 3. **The error problem** โ€” the system failing to work as intended. The AIO Framework encodes one judgment as one line: ``` C:MED/IXi | V:Bec, so verification never requires trusting โ€” or even reaching โ€” an AIO server beyond fetching the record itself. ```bash 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. --- ## Live endpoints No authentication, CORS open, JSON, all CC BY 4.0. | Endpoint | | |---|---| | | 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. ```json { "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: --- ## Related repositories | Repository | | |---|---| | [`AI-Integrity/AIO20002`](https://github.com/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`](https://github.com/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. --- ## Corrections Errors in a standard, a mapping, or a benchmark result are handled through the **public RFC process**, not private correction: . 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. --- ## Legal note 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: