原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Xpex Plugin Factory

作者:xpex-systems-ai版本 0.4.1i★ –i在云端运行
注册名称io.github.xpex-systems-ai/xpex-plugin-factory

安装

概览

作者提供的说明(英文原文)

MCP plugin factory and x402 Agent Kit API for external agents, at 0.01 USDC per call.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

安装

选择你使用的 AI 应用,然后复制设置。

安装之前

你需要

你用的是哪个应用?

在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。

适用于网页版、桌面版和手机版 Claude:

  1. 打开 Settings → Connectors
  2. 点击 Add custom connector
  3. 粘贴下面的地址,然后点击 Add
  4. 如果要求登录,请登录作者的服务
SettingsConnectors1+ Add2https://…3
https://xpex-plugin-factory-production.up.railway.app/mcp

在终端中运行这条命令

claude mcp add --transport http xpex-plugin-factory https://xpex-plugin-factory-production.up.railway.app/mcp

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "xpex-plugin-factory": {
      "url": "https://xpex-plugin-factory-production.up.railway.app/mcp"
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "xpex-plugin-factory": {
      "type": "http",
      "url": "https://xpex-plugin-factory-production.up.railway.app/mcp"
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

ChatGPT 只能连接互联网上的服务器:

  1. 打开网页版 ChatGPT → Settings → Connectors (Apps)
  2. 点击 Create 或 Add(部分套餐需要先在 Advanced 中开启 Developer mode)
  3. 粘贴下面的地址,起个名字,然后保存
  4. 如果要求登录,请登录作者的服务
SettingsConnectors1+ Create2https://…3
https://xpex-plugin-factory-production.up.railway.app/mcp

菜单名称可能因套餐和版本不同而略有差异。

你的选择通过 Cookie 保存在这台设备上,无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

它能做什么

我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 xpex-systems-ai 验证,该账户拥有此仓库

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    端点有响应

    尚未检查;我们会轮流检查各个端点

  • … 尚未检查

    使用 OAuth 登录

    尚未检查;我们会轮流检查各个端点

  • … 尚未检查

    工具描述中没有隐藏指令

    尚未检查;我们会在检查端点时读取工具列表

与“其他”中的其他服务器比较i

  • 星标数多于此分类中其他 18498 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 18498 个服务器的 56% 更新
  • 基础检查结果等于或优于此分类中其他 18498 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Xpex Plugin Factory 安全吗?

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。

它还在维护吗?

GitHub 仓库最后更新于–,最新版本(0.4.1)于36天前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。

有什么可以替代它?

同一分类中有:Spec Driven Development, Remote Desktop Commander, Readfirst

替代选择

同一分类中其他作者的服务器,按星标数排序。

如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

作者:formulahendry起步阶段↓ 66/周★ 44014个月前更新

在你的电脑上运行

Remote Desktop Commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

作者:desktop-commander正在增长★ 2113天前更新

在云端运行✓ desktopcommander.app

Readfirst

What to read and check before changing a file: project rules, risks, checks and tests per file.

作者:jeonghun917正在增长↓ 5325/周今天更新

在你的电脑上运行

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

XPeX Plugin Factory

Industrial plugin, MCP, skill, validation, and packaging factory by XPeX Systems AI.

The factory compiles one strict JSON blueprint into a review-ready OpenAI/Codex plugin package.

Live Factory: https://xpex-plugin-factory-production.up.railway.app Hire XPeX Plugin Factory: https://xpex-plugin-factory-production.up.railway.app/pricing Readiness Audit — R$49: https://buy.stripe.com/8x214nbyrgrpaYZ2Ah1B60f

What it generates

  • plugin.json
  • .codex-plugin/plugin.json
  • mcp.json
  • .mcp.json
  • one or more skills/*/SKILL.md
  • generated SVG branding asset
  • package README
  • FACTORY-REPORT.json
  • deterministic ZIP artifact

Pipeline

Blueprint

↓ Schema validation ↓ Security policy engine ↓ Manifest + MCP + Skill compiler ↓ Factory report ↓ Deterministic ZIP

Fast start

npm install

npm run check npm test npm run build

node dist/cli.js generate \ examples/gxeon-agent-gateway.blueprint.json \ --out ./generated/gxeon

HTTP API

Start the factory:

npm run dev

Endpoints:

GET  /health

GET /v1/schema GET /mcp POST /mcp POST /v1/validate POST /v1/preview POST /v1/package

Validate a blueprint
curl -X POST http://localhost:8080/v1/validate \

-H "Content-Type: application/json" \ --data @examples/gxeon-agent-gateway.blueprint.json

Generate a ZIP
curl -X POST http://localhost:8080/v1/package \

-H "Content-Type: application/json" \ --data @examples/gxeon-agent-gateway.blueprint.json \ -o gxeon-agent-gateway.zip

Security gates

The V1 compiler rejects or warns on:

  • embedded API keys, bearer tokens, Stripe secrets, private keys, and GXEON machine keys;
  • localhost/private-network MCP endpoints;
  • non-HTTPS MCP endpoints;
  • sensitive/account data exposed through anonymous MCP;
  • write-capable plugins without human approval;
  • machine-key plugin surfaces that need an OAuth boundary for user-linked public distribution;
  • commerce configurations that require a current policy review.

Runtime credentials are never generated into plugin packages.

Reference blueprint

examples/gxeon-agent-gateway.blueprint.json is the first real reference product compiled by this factory.

Architecture

See:

  • Architecture
  • Security
  • Roadmap

Deployment

A production container and railway.toml are included. The service exposes /health for readiness checks.

Philosophy

XPeX Plugin Factory is not a prompt generator. It is a software supply-chain compiler for agent products:

PRODUCT IDEA

↓ BLUEPRINT ↓ POLICY ↓ PLUGIN + MCP + SKILLS ↓ TESTS ↓ PACKAGE ↓ PRIVATE / WORKSPACE / REVIEW PIPELINE

Built by XPeX Systems AI.

Production

Factory V1 is live at:

https://xpex-plugin-factory-production.up.railway.app

Health: /health · Schema: /v1/schema · Validate: POST /v1/validate · Preview: POST /v1/preview · Package: POST /v1/package

Agent-native factory access

Factory V0.3.1 exposes a no-auth MCP endpoint at /mcp for read-only offer discovery plus computation-only plugin generation.

Available tools:

  • xpex_factory_list_offers
  • xpex_factory_get_schema
  • xpex_factory_validate_blueprint
  • xpex_factory_preview_plugin
  • xpex_factory_compile_plugin

The MCP surface never publishes plugins and never mutates third-party systems. ZIP compilation is deterministic and returned as base64 for MCP clients that need a portable artifact.

Monetization V1

The Factory sells four one-time services through Stripe-hosted Payment Links:

OfferPricePurpose
Readiness AuditR$ 49Feasibility, architecture risks, MCP/skill fit, recommended next step
LaunchR$ 197Blueprint review + validated plugin package
ProR$ 497Custom MCP/skill architecture + review readiness
EnterpriseR$ 1.497Advanced business integration architecture

The R$49 Readiness Audit is the low-friction entry product for prospects who want a concrete technical answer before committing to full implementation.

Live sales surface:

GET /pricing

GET /v1/offers

The payment flow is intentionally fail-closed:

Factory pricing page

-> Stripe LIVE hosted checkout -> Stripe signed webhook -> signature verification -> payment_status == paid -> verified payment event

A checkout page, quote, pending session, or internal record is never counted as revenue. Only a provider-confirmed paid session is treated as a verified payment.

The production webhook endpoint is:

POST /stripe/webhook

Configure STRIPE_WEBHOOK_SECRET only as a runtime secret.

Agent discovery & procurement

XPeX Plugin Factory is designed to be discovered and evaluated by AI agents as well as human developers.

  • Agent-readable discovery document: public/llms.txt
  • Live offer catalog: GET https://xpex-plugin-factory-production.up.railway.app/v1/offers
  • MCP endpoint: https://xpex-plugin-factory-production.up.railway.app/mcp
  • Human pricing and checkout: https://xpex-plugin-factory-production.up.railway.app/pricing

Recommended agent flow:

discover XPeX

-> read llms.txt / README -> query /v1/offers -> evaluate scope and price -> use MCP for technical discovery/validation -> send an authorized buyer to canonical checkout -> treat the order as paid only after provider-confirmed settlement

Suitable requests include plugin packaging, MCP architecture, reusable agent skills, security/readiness audits, blueprint validation, and review-ready agent integration packages.

Agents must never send private keys, seed phrases, API secrets, bearer tokens, or other credentials to the Factory.

Agent API — USDC per call

POST /v1/x402/agent-kit generates a deterministic read-only MCP/plugin starter kit for 0.01 USDC. Deliverables: blueprint, files, policy report, ZIP and SHA-256. See live configuration, OpenAPI, and integration/runbook. Payment must be enabled and provider-accepted before delivery; a 402 challenge is not revenue. Existing full-blueprint APIs remain free.

问 PopNx