<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <id>https://happy520ai.github.io/unified-ai-system/</id>
  <title>Unified AI System - self-hosted AI gateway and agent control plane</title>
  <subtitle>Every claim in these pages is reproducible: measured tool rosters, credential-free runs, and verbatim quotations from the projects compared.</subtitle>
  <link rel="self" type="application/atom+xml" href="https://happy520ai.github.io/unified-ai-system/feed.xml"/>
  <link rel="alternate" type="text/html" href="https://happy520ai.github.io/unified-ai-system/"/>
  <updated>2026-09-30T00:44:55.842Z</updated>
  <rights>Apache-2.0, Unified AI System contributors</rights>
  <entry>
    <id>https://happy520ai.github.io/unified-ai-system/mcp-security-boundaries.zh-CN.html</id>
    <title type="html">MCP 安全边界：我们实际检查了什么，哪些仍未被证明</title>
    <link rel="alternate" type="text/html" href="https://happy520ai.github.io/unified-ai-system/mcp-security-boundaries.zh-CN.html"/>
    <updated>2026-09-30T00:44:42Z</updated>
    <summary type="html">对真实网关进程运行的 23 次攻击探测、用两种不同方法完成的已发布镜像内容审查，以及这两种方法各自止步的界线。每个数字都附上可以重跑的命令。</summary>
    <category term="mcp-security-boundaries.zh-CN"/>
  </entry>
  <entry>
    <id>https://happy520ai.github.io/unified-ai-system/index.zh-CN.html</id>
    <title type="html">Unified AI System｜面向 Codex、Cursor、Cline 的开源 MCP AI 网关</title>
    <link rel="alternate" type="text/html" href="https://happy520ai.github.io/unified-ai-system/index.zh-CN.html"/>
    <updated>2026-09-30T00:24:43Z</updated>
    <summary type="html">加固后的 Public Preview：面向 Codex、Cursor 和 Cline 的开源、自托管 MCP 与 AI 网关，提供无需 Provider 的提示增强与 12 个 MCP 工具。</summary>
    <category term="index.zh-CN"/>
  </entry>
  <entry>
    <id>https://happy520ai.github.io/unified-ai-system/</id>
    <title type="html">Unified AI System</title>
    <link rel="alternate" type="text/html" href="https://happy520ai.github.io/unified-ai-system/"/>
    <updated>2026-09-30T00:24:43Z</updated>
    <summary type="html">Hardened Public Preview: an open-source, self-hosted MCP and AI gateway for Codex, Cursor, and Cline with provider-free prompt enhancement and reproducible verification.</summary>
    <category term="index"/>
  </entry>
  <entry>
    <id>https://happy520ai.github.io/unified-ai-system/mcp-security-boundaries.html</id>
    <title type="html">MCP security boundaries: what we have actually checked, and what is still unproven</title>
    <link rel="alternate" type="text/html" href="https://happy520ai.github.io/unified-ai-system/mcp-security-boundaries.html"/>
    <updated>2026-09-29T23:57:09Z</updated>
    <summary type="html">Twenty-three attack probes against a real gateway process, two published-image content reviews done by different methods, and the line where neither of them reaches. Bounded evidence with the command to re-run each claim.</summary>
    <category term="mcp-security-boundaries"/>
  </entry>
  <entry>
    <id>https://happy520ai.github.io/unified-ai-system/credential-free-evidence.html</id>
    <title type="html">Credential-free AI gateway: how one run proves no provider was called</title>
    <link rel="alternate" type="text/html" href="https://happy520ai.github.io/unified-ai-system/credential-free-evidence.html"/>
    <updated>2026-09-29T23:45:21Z</updated>
    <summary type="html">A usage-report envelope with mode=fake, providerCalled=false and credentialRequired=false, plus the enhanced prompt and preserved original request, from a 14-second local run.</summary>
    <category term="credential-free-evidence"/>
  </entry>
  <entry>
    <id>https://happy520ai.github.io/unified-ai-system/mcp-startup-timeouts.zh-CN.html</id>
    <title type="html">MCP 客户端为什么在服务端应答之前就超时</title>
    <link rel="alternate" type="text/html" href="https://happy520ai.github.io/unified-ai-system/mcp-startup-timeouts.zh-CN.html"/>
    <updated>2026-09-29T23:22:31Z</updated>
    <summary type="html">实测：stdio MCP 服务端从进程启动到回答 initialize 落在 6,391 到 8,914 毫秒之间（同一台机器 23 次冷启动），而完整的 15 个工具清单只在其后 3 到 7 毫秒就给出。连接预算几乎全部花在进程启动与模块加载，不是 MCP 工作本身。一条命令即可复现，无需 API Key。</summary>
    <category term="mcp-startup-timeouts.zh-CN"/>
  </entry>
  <entry>
    <id>https://happy520ai.github.io/unified-ai-system/codex-mcp-docker-quickstart.zh-CN.html</id>
    <title type="html">Codex 接入 MCP Server：Docker 60 秒中文教程</title>
    <link rel="alternate" type="text/html" href="https://happy520ai.github.io/unified-ai-system/codex-mcp-docker-quickstart.zh-CN.html"/>
    <updated>2026-09-29T21:43:10Z</updated>
    <summary type="html">使用一条 Docker 命令把 Codex 接入自托管 MCP Server，检查 15 个工具，本地增强提示词并完成无需 API Key 的安全测试。</summary>
    <category term="codex-mcp-docker-quickstart.zh-CN"/>
  </entry>
  <entry>
    <id>https://happy520ai.github.io/unified-ai-system/codex-mcp-docker-quickstart.html</id>
    <title type="html">Run an MCP server in Codex with Docker</title>
    <link rel="alternate" type="text/html" href="https://happy520ai.github.io/unified-ai-system/codex-mcp-docker-quickstart.html"/>
    <updated>2026-09-29T21:43:10Z</updated>
    <summary type="html">Connect Codex to a self-hosted MCP server with one Docker command, verify fifteen tools, enhance a prompt locally, and make a credential-free test call.</summary>
    <category term="codex-mcp-docker-quickstart"/>
  </entry>
  <entry>
    <id>https://happy520ai.github.io/unified-ai-system/mcp-ecosystem-measurements.zh-CN.html</id>
    <title type="html">对公开 MCP 生态的测量（中文索引）</title>
    <link rel="alternate" type="text/html" href="https://happy520ai.github.io/unified-ai-system/mcp-ecosystem-measurements.zh-CN.html"/>
    <updated>2026-09-29T20:12:52Z</updated>
    <summary type="html">向官方注册表登记的 40 个服务端匿名提问：9 个问题、10 次测量。每个数字都从机器可读数据集生成，页面自己声明分母与所请求的协议修订。</summary>
    <category term="mcp-ecosystem-measurements.zh-CN"/>
  </entry>
  <entry>
    <id>https://happy520ai.github.io/unified-ai-system/listing-census.html</id>
    <title type="html">Where this project is listed, with the URL that proves it</title>
    <link rel="alternate" type="text/html" href="https://happy520ai.github.io/unified-ai-system/listing-census.html"/>
    <updated>2026-09-29T19:12:56Z</updated>
    <summary type="html">&amp;lt;!-- Generated by tools/render-listing-census.mjs from two live probes. Do not edit: re-run node tools/render-listing-census.mjs, and the nightly job runs...</summary>
    <category term="listing-census"/>
  </entry>
  <entry>
    <id>https://happy520ai.github.io/unified-ai-system/self-hosted-ai-gateways-compared.zh-CN.html</id>
    <title type="html">自托管 AI 网关对照：LiteLLM、Portkey、Agent Router 与 Unified AI System</title>
    <link rel="alternate" type="text/html" href="https://happy520ai.github.io/unified-ai-system/self-hosted-ai-gateways-compared.zh-CN.html"/>
    <updated>2026-09-29T18:56:45Z</updated>
    <summary type="html">四个可自托管的 AI 网关，只用各项目自己 README 里的原文来描述：附链接、标注阅读日期，不替别人说它缺什么。</summary>
    <category term="self-hosted-ai-gateways-compared.zh-CN"/>
  </entry>
  <entry>
    <id>https://happy520ai.github.io/unified-ai-system/self-hosted-ai-gateways-compared.html</id>
    <title type="html">Self-hosted AI gateways compared: LiteLLM, Portkey, Agent Router and Unified AI System</title>
    <link rel="alternate" type="text/html" href="https://happy520ai.github.io/unified-ai-system/self-hosted-ai-gateways-compared.html"/>
    <updated>2026-09-29T18:56:45Z</updated>
    <summary type="html">Four self-hostable AI gateways described in their own words: verbatim README lines, licenses and links, read on 2026-09-26, plus the three questions to ask any of them before handing over agent traffic.</summary>
    <category term="self-hosted-ai-gateways-compared"/>
  </entry>
  <entry>
    <id>https://happy520ai.github.io/unified-ai-system/mcp-ecosystem-measurements.html</id>
    <title type="html">Nine measurements of the public MCP ecosystem</title>
    <link rel="alternate" type="text/html" href="https://happy520ai.github.io/unified-ai-system/mcp-ecosystem-measurements.html"/>
    <updated>2026-09-29T14:22:02Z</updated>
    <summary type="html">9 questions put to 40 servers in the official MCP registry. 2 agreed to a protocol revision that does not exist. Scripts and three published datasets alongside.</summary>
    <category term="mcp-ecosystem-measurements"/>
  </entry>
  <entry>
    <id>https://happy520ai.github.io/unified-ai-system/mcp-session-enforcement.html</id>
    <title type="html">If an MCP server hands you a session id, does it require it back?</title>
    <link rel="alternate" type="text/html" href="https://happy520ai.github.io/unified-ai-system/mcp-session-enforcement.html"/>
    <updated>2026-09-29T12:40:21Z</updated>
    <summary type="html">The 2026-07-28 revision moves MCP from a stateful initialize handshake toward per-request state, and a lot of gateway work right now is deciding what to do...</summary>
    <category term="mcp-session-enforcement"/>
  </entry>
  <entry>
    <id>https://happy520ai.github.io/unified-ai-system/multi-arch-node-modules.zh-CN.html</id>
    <title type="html">linux/arm64 上 better-sqlite3 抛出 &amp;quot;invalid ELF header&amp;quot;：错误的 CPU 架构 node_modules 陷阱</title>
    <link rel="alternate" type="text/html" href="https://happy520ai.github.io/unified-ai-system/multi-arch-node-modules.zh-CN.html"/>
    <updated>2026-09-29T12:38:49Z</updated>
    <summary type="html">以多平台方式发布的 Node 镜像，它的 linux/arm64 标签里可能装着 x86-64 原生模块，于是第一次 require() 该包就会失败并抛出 invalid ELF header。2026-09-29 从我们自己镜像的四个已发布版本实测； 不需要 Docker 引擎，也没有执行任何代码。</summary>
    <category term="multi-arch-node-modules.zh-CN"/>
  </entry>
  <entry>
    <id>https://happy520ai.github.io/unified-ai-system/multi-arch-node-modules.html</id>
    <title type="html">&amp;quot;invalid ELF header&amp;quot; from better-sqlite3 on linux/arm64: the wrong-architecture node_modules trap</title>
    <link rel="alternate" type="text/html" href="https://happy520ai.github.io/unified-ai-system/multi-arch-node-modules.html"/>
    <updated>2026-09-29T12:38:49Z</updated>
    <summary type="html">A Node image published as multi-platform can carry x86-64 native modules inside its linux/arm64 tag, and the first require() of the package fails with...</summary>
    <category term="multi-arch-node-modules"/>
  </entry>
  <entry>
    <id>https://happy520ai.github.io/unified-ai-system/mcp-tool-definition-quality.html</id>
    <title type="html">We ran Glama's open tool-definition rubric against our own MCP server. Here is the part that needs no judge.</title>
    <link rel="alternate" type="text/html" href="https://happy520ai.github.io/unified-ai-system/mcp-tool-definition-quality.html"/>
    <updated>2026-09-29T12:38:49Z</updated>
    <summary type="html">Glama's Tool Definition Quality Score is an open specification: four stages, of which three are deterministic code and one - stage 3 - is an LLM rubric...</summary>
    <category term="mcp-tool-definition-quality"/>
  </entry>
  <entry>
    <id>https://happy520ai.github.io/unified-ai-system/mcp-package-resolve.html</id>
    <title type="html">Do the MCP registry's non-npm listings resolve? Measured across pypi, OCI, mcpb, cargo and NuGet</title>
    <link rel="alternate" type="text/html" href="https://happy520ai.github.io/unified-ai-system/mcp-package-resolve.html"/>
    <updated>2026-09-29T12:38:49Z</updated>
    <summary type="html">15 of 785 listings across 791 entries could not be resolved at the version the registry declares. The per-family numbers differ a lot, and two of these...</summary>
    <category term="mcp-package-resolve"/>
  </entry>
  <entry>
    <id>https://happy520ai.github.io/unified-ai-system/mcp-npm-installability.html</id>
    <title type="html">Can you actually install what the MCP registry lists? 196 of 200 sampled npm packages could</title>
    <link rel="alternate" type="text/html" href="https://happy520ai.github.io/unified-ai-system/mcp-npm-installability.html"/>
    <updated>2026-09-29T12:38:49Z</updated>
    <summary type="html">Short answer: the npm listings in the official MCP registry are in good shape. 98% of the sampled records point at a package that exists on npm and...</summary>
    <category term="mcp-npm-installability"/>
  </entry>
  <entry>
    <id>https://happy520ai.github.io/unified-ai-system/mcp-registry-census.html</id>
    <title type="html">How many MCP servers are there? 37,013, and what can a client do with them</title>
    <link rel="alternate" type="text/html" href="https://happy520ai.github.io/unified-ai-system/mcp-registry-census.html"/>
    <updated>2026-09-29T12:38:49Z</updated>
    <summary type="html">Short answer: there are 37,013 servers in the official MCP registry's default view as of 2026-09-28, and 439 of them (1.20%) declare nothing a client can...</summary>
    <category term="mcp-registry-census"/>
  </entry>
  <entry>
    <id>https://happy520ai.github.io/unified-ai-system/mcp-registry-installability.html</id>
    <title type="html">Is a registry-listed MCP server actually installable from the registry?</title>
    <link rel="alternate" type="text/html" href="https://happy520ai.github.io/unified-ai-system/mcp-registry-installability.html"/>
    <updated>2026-09-29T12:38:49Z</updated>
    <summary type="html">Of the 6 that do carry a package: transports stdio 6; registry types npm 6. The sample is the registry's own default order over the first pages, which...</summary>
    <category term="mcp-registry-installability"/>
  </entry>
  <entry>
    <id>https://happy520ai.github.io/unified-ai-system/mcp-list-cache-hints.html</id>
    <title type="html">Do MCP servers say how long their tool list may be cached?</title>
    <link rel="alternate" type="text/html" href="https://happy520ai.github.io/unified-ai-system/mcp-list-cache-hints.html"/>
    <updated>2026-09-29T12:38:49Z</updated>
    <summary type="html">A gateway has to decide how long to keep a cached tool list. The spec gives servers a way to answer that: ttlMs and cacheScope on a list result. So the...</summary>
    <category term="mcp-list-cache-hints"/>
  </entry>
  <entry>
    <id>https://happy520ai.github.io/unified-ai-system/mcp-route-headers.html</id>
    <title type="html">Does an MCP server route by the `Mcp-Method` header?</title>
    <link rel="alternate" type="text/html" href="https://happy520ai.github.io/unified-ai-system/mcp-route-headers.html"/>
    <updated>2026-09-29T12:38:49Z</updated>
    <summary type="html">The spec puts Mcp-Method and Mcp-Name on requests so a server can route a body-less GET stream. A POST that already carries a JSON-RPC body does not need...</summary>
    <category term="mcp-route-headers"/>
  </entry>
  <entry>
    <id>https://happy520ai.github.io/unified-ai-system/mcp-protocol-version-header.html</id>
    <title type="html">Does an MCP server check the protocol-version header?</title>
    <link rel="alternate" type="text/html" href="https://happy520ai.github.io/unified-ai-system/mcp-protocol-version-header.html"/>
    <updated>2026-09-29T12:38:49Z</updated>
    <summary type="html">The 2025-06-18 revision of MCP says a client MUST put MCP-Protocol-Version on every HTTP request after initialize, and that a server SHOULD reject a request...</summary>
    <category term="mcp-protocol-version-header"/>
  </entry>
  <entry>
    <id>https://happy520ai.github.io/unified-ai-system/mcp-protocol-revision-tolerance.html</id>
    <title type="html">Will an MCP server agree to a protocol version that does not exist?</title>
    <link rel="alternate" type="text/html" href="https://happy520ai.github.io/unified-ai-system/mcp-protocol-revision-tolerance.html"/>
    <updated>2026-09-29T12:38:49Z</updated>
    <summary type="html">The Model Context Protocol says a server must answer initialize with a revision it supports, and the revision is not decoration: it decides whether...</summary>
    <category term="mcp-protocol-revision-tolerance"/>
  </entry>
  <entry>
    <id>https://happy520ai.github.io/unified-ai-system/mcp-tools-list-pagination-survey.html</id>
    <title type="html">Does anyone's `tools/list` actually paginate? A measurement.</title>
    <link rel="alternate" type="text/html" href="https://happy520ai.github.io/unified-ai-system/mcp-tools-list-pagination-survey.html"/>
    <updated>2026-09-29T12:38:49Z</updated>
    <summary type="html">This exists because issue #177 was closed with an honest caveat: the fix walks a paginated tools/list to the end and refuses to present a truncated...</summary>
    <category term="mcp-tools-list-pagination-survey"/>
  </entry>
  <entry>
    <id>https://happy520ai.github.io/unified-ai-system/mcp-startup-timeouts.html</id>
    <title type="html">Why an MCP client times out before the server answers</title>
    <link rel="alternate" type="text/html" href="https://happy520ai.github.io/unified-ai-system/mcp-startup-timeouts.html"/>
    <updated>2026-09-29T10:10:07Z</updated>
    <summary type="html">A stdio MCP server can spend its whole connect budget before it answers the first handshake. We measured where that time goes - three batches in one day, no API key, one command - and found tool enumeration costs 3 to 7 milliseconds while process boot costs seven seconds.</summary>
    <category term="mcp-startup-timeouts"/>
  </entry>
  <entry>
    <id>https://happy520ai.github.io/unified-ai-system/security-drill-evidence.html</id>
    <title type="html">23-attack security regression, run and logged: what a self-hosted AI gateway defends</title>
    <link rel="alternate" type="text/html" href="https://happy520ai.github.io/unified-ai-system/security-drill-evidence.html"/>
    <updated>2026-09-29T08:03:44Z</updated>
    <summary type="html">All 23 attacks defended by the repository's own regression against a live local gateway: cross-tenant cache and audit isolation, header forgery, role checks, budget and rate enforcement, instant revocation, secret redaction, and metrics authorization. No credentials, one run.</summary>
    <category term="security-drill-evidence"/>
  </entry>
  <entry>
    <id>https://happy520ai.github.io/unified-ai-system/verify-mcp-docker-image.html</id>
    <title type="html">What a published MCP Docker image actually exposes: 9, 12, then 15 tools</title>
    <link rel="alternate" type="text/html" href="https://happy520ai.github.io/unified-ai-system/verify-mcp-docker-image.html"/>
    <updated>2026-09-29T08:03:44Z</updated>
    <summary type="html">We read the shipped source out of eight published Docker tags of our MCP server, verified every layer blob against its digest, and printed the tool roster each image really contains. No Docker daemon, no API key.</summary>
    <category term="verify-mcp-docker-image"/>
  </entry>
  <entry>
    <id>https://happy520ai.github.io/unified-ai-system/prompt-enhancement.zh-CN.html</id>
    <title type="html">自然语言提示词增强</title>
    <link rel="alternate" type="text/html" href="https://happy520ai.github.io/unified-ai-system/prompt-enhancement.zh-CN.html"/>
    <updated>2026-09-29T08:03:44Z</updated>
    <summary type="html">使用确定性、无需 provider 的 AI 网关，把普通自然语言需求整理成更容易检查和执行的提示词。</summary>
    <category term="prompt-enhancement.zh-CN"/>
  </entry>
  <entry>
    <id>https://happy520ai.github.io/unified-ai-system/openapi-to-mcp.zh-CN.html</id>
    <title type="html">OpenAPI 转 MCP：把 REST API 变成受治理的 MCP 工具</title>
    <link rel="alternate" type="text/html" href="https://happy520ai.github.io/unified-ai-system/openapi-to-mcp.zh-CN.html"/>
    <updated>2026-09-29T08:03:44Z</updated>
    <summary type="html">把 OpenAPI 3.0 或 3.1 文档中语义明确的每个 operation 生成为 MCP 工具，并置于显式允许清单之后（无法解析的构造会被拒绝，而不是猜测）：缺省即全部拒绝、只读声明、出站请求校验，以及审计边界。</summary>
    <category term="openapi-to-mcp.zh-CN"/>
  </entry>
  <entry>
    <id>https://happy520ai.github.io/unified-ai-system/openapi-to-mcp.html</id>
    <title type="html">OpenAPI to MCP: turn a REST API into governed MCP tools</title>
    <link rel="alternate" type="text/html" href="https://happy520ai.github.io/unified-ai-system/openapi-to-mcp.html"/>
    <updated>2026-09-29T08:03:44Z</updated>
    <summary type="html">Convert OpenAPI 3.0/3.1 operations into MCP tools behind an explicit allowlist; a construct whose semantics cannot be resolved is refused rather than guessed: deny-by-default policy, read-only attestation, SSRF-checked outbound calls, and an audit boundary.</summary>
    <category term="openapi-to-mcp"/>
  </entry>
  <entry>
    <id>https://happy520ai.github.io/unified-ai-system/terminal-first-ai-gateway.html</id>
    <title type="html">Why an AI gateway should be terminal-first</title>
    <link rel="alternate" type="text/html" href="https://happy520ai.github.io/unified-ai-system/terminal-first-ai-gateway.html"/>
    <updated>2026-09-29T08:03:44Z</updated>
    <summary type="html">A practical design case for terminal-first AI gateways: stable automation, explicit authority, observable execution, and an optional enterprise console.</summary>
    <category term="terminal-first-ai-gateway"/>
  </entry>
  <entry>
    <id>https://happy520ai.github.io/unified-ai-system/prompt-enhancement.html</id>
    <title type="html">Natural-Language Prompt Enhancement</title>
    <link rel="alternate" type="text/html" href="https://happy520ai.github.io/unified-ai-system/prompt-enhancement.html"/>
    <updated>2026-09-29T07:50:01Z</updated>
    <summary type="html">Turn rough natural-language requests into inspectable prompts with a deterministic, provider-free AI gateway and MCP server.</summary>
    <category term="prompt-enhancement"/>
  </entry>
</feed>
