原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

MCP Foundry — Build, Test & Publish MCP Servers

作者:Noetfield-Systems版本 0.1.0i★ 0i在云端运行代码仓库 ↗
注册名称io.github.Noetfield-Systems/mcp-foundry

安装方法

What it does

Build, test, publish and manage real MCP servers from APIs with a live developer studio.

  • Connects 在云端运行
  • Account or key No key needed
  • Category 其他

为什么排在这里

列表按使用分(满分 100)排序,由以下部分组成

热度0/80GitHub 星标或每周下载量:较大的计 60,较小的计 20
新鲜度12/1230 天内有发布或代码更新得满分
仍在响应8/8上次检查时云端端点有响应
使用分20/100

质量: 基础检查通过 4/5 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)

安装

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

用一句话让 AI 帮你安装

请帮我安装 MCP Foundry — Build, Test & Publish MCP Servers。按照 https://mcp.popnx.com/i/noetfield-systems-mcp-foundry.md 操作,先把命令给我看,等我同意后再运行。

粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文

通过 4/5 项检查 · 你的提问会经过开发者的服务器(mcp-foundry-web-production.up.railway.app) · ✓ 命令已检查 2026年11月18日

第一步:你用哪个 AI?

选择你用的应用,步骤会显示在下方。

可连接 Claude · 约 2 分钟

不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加

  1. 打开 Claude 的 Connectors 页面

    CustomizeConnectors

    CustomizeConnectors1Add2https://…3Add4
  2. 点击“Add” → “Custom” → “Web”,填写这 2 项

    把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue

    Name · 名称MCP Foundry — Build, Test & Publish MCP Servers
    Remote MCP server URL · 地址https://mcp-foundry-web-production.up.railway.app/mcp/foundry

    在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add

  3. 在聊天中开启

    +ConnectorsMCP Foundry — Build, Test & Publish MCP Servers

  4. 试一试

    用 MCP Foundry — Build, Test & Publish MCP Servers 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude 说正在使用 MCP Foundry — Build, Test & Publish MCP Servers,或回答中出现 MCP Foundry — Build, Test & Publish MCP Servers 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

能否连接 ChatGPT 取决于方案

完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页

  1. 在网页版 ChatGPT 打开添加 MCP 的页面

    Plugins+Add custom MCP server

    ChatGPTPlugins1+2https://…3Create4
  2. 填写名称和地址

    输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin

    Name · 名称MCP Foundry — Build, Test & Publish MCP Servers
    Connection · 地址https://mcp-foundry-web-production.up.railway.app/mcp/foundry
  3. 在聊天中选择 MCP Foundry — Build, Test & Publish MCP Servers

    开启新聊天,输入前先从插件列表中选择 MCP Foundry — Build, Test & Publish MCP Servers

  4. 试一试

    用 MCP Foundry — Build, Test & Publish MCP Servers 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 ChatGPT 说正在使用 MCP Foundry — Build, Test & Publish MCP Servers,或回答中出现 MCP Foundry — Build, Test & Publish MCP Servers 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同

可连接 Claude Code · 约 2 分钟

不需要密钥,不用安装程序

  1. 打开终端

    Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell

  2. 粘贴这条命令并按 Enter

    claude mcp add --transport http --scope user foundry https://mcp-foundry-web-production.up.railway.app/mcp/foundry
  3. 在 Claude Code 中输入 /mcp

    应能看到 MCP Foundry — Build, Test & Publish MCP Servers 在列表中并显示已连接

  4. 试一试

    用 MCP Foundry — Build, Test & Publish MCP Servers 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude Code 说正在使用 MCP Foundry — Build, Test & Publish MCP Servers,或回答中出现 MCP Foundry — Build, Test & Publish MCP Servers 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

可连接 Cursor · 约 2 分钟

不需要密钥,不用安装程序

  1. 点击这个按钮打开 Cursor

    在 Cursor 中打开

    Cursor 会请你确认安装,点击 Install

  2. 在 Cursor 中以 Agent 模式打开 AI 聊天

  3. 试一试

    用 MCP Foundry — Build, Test & Publish MCP Servers 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Cursor 说正在使用 MCP Foundry — Build, Test & Publish MCP Servers,或回答中出现 MCP Foundry — Build, Test & Publish MCP Servers 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同

可连接 VS Code · 约 2 分钟

不需要密钥,不用安装程序

  1. 点击这个按钮打开 VS Code

    在 VS Code 中打开

    VS Code 会请你确认安装,点击 Install

  2. 在 VS Code 中以 Agent 模式打开 AI 聊天

  3. 试一试

    用 MCP Foundry — Build, Test & Publish MCP Servers 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 VS Code 说正在使用 MCP Foundry — Build, Test & Publish MCP Servers,或回答中出现 MCP Foundry — Build, Test & Publish MCP Servers 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同

其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看

查看所有支持 MCP 的应用 →

通过网页连接的应用使用的地址

地址https://mcp-foundry-web-production.up.railway.app/mcp/foundry

JSON 设置在下方“开发者专用”中

卡住了?问问正在用 MCP Foundry — Build, Test & Publish MCP Servers 的人💬 讨论 →
开发者专用:终端命令和 JSON 设置

通过网页连接

Claude Code

claude mcp add --transport http --scope user foundry https://mcp-foundry-web-production.up.railway.app/mcp/foundry

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "foundry": {
      "url": "https://mcp-foundry-web-production.up.railway.app/mcp/foundry"
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "foundry": {
      "type": "http",
      "url": "https://mcp-foundry-web-production.up.railway.app/mcp/foundry"
    }
  }
}

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

一览

每周下载量i
不在 npm/PyPI 上
许可证i
未注明许可证
连接方式
在云端运行
传输方式
streamable-http
最新版本i
0.1.0
分类i
其他
发布到注册中心i
2026年11月18日
代码最后更新i
2026年11月18日
最近检查
2026年11月18日
作者
Noetfield-Systems
注册状态
活跃

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。

通过互联网连接,适用于

ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

全部应用及其优缺点 →

它能做什么

工具名称和描述与服务器在 2026年11月18日 报告的完全一致。这些内容由作者撰写,不是我们写的;我们以纯文本形式显示。

  • search_servers

    Search published public MCP servers in MCP Foundry

  • get_server_tools

    List tools published by one MCP Foundry server

基础检查i

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

  • ✓ 通过

    作者与仓库一致

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

  • ✓ 通过

    仍在维护

    代码最后更新于昨天

  • ✕ 未通过

    有许可证

    仓库中没有找到许可证文件

  • ✓ 通过

    端点有响应

    在 318 毫秒内响应(HTTP 200)

  • – 不适用

    使用 OAuth 登录

    无需登录

  • ✓ 通过

    工具描述中没有隐藏指令

    已读取 2 个工具描述,未发现针对 AI 的隐藏指令

我们检查什么 → · JSON

作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章

如果你是作者,可把这段代码贴到 README。徽章会链接回本页。

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/noetfield-systems-mcp-foundry.svg)](https://mcp.popnx.com/en/servers/noetfield-systems-mcp-foundry)

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

用户评价

还没有评价

登录后写评价

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

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

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

常见问题

MCP Foundry — Build, Test & Publish MCP Servers 安全吗?

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

它需要哪些密钥或代码?

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

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

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

它还在维护吗?

GitHub 仓库最后更新于昨天,最新版本(0.1.0)于昨天进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。

有什么可以替代它?

同一分类中有:World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu

功能相近的其他选择

同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。

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

World Monitor

Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.

作者:koala73广泛使用★ 9.1万3天前更新

在云端运行✓ 服务方 · worldmonitor.app

openstatus

Manage monitors, status pages, incidents and maintenances in your openstatus workspace.

作者:openstatusHQ广泛使用★ 92742个月前更新

在云端运行✓ 服务方 · openstatus.dev

Strata

MCP server for progressive tool usage at any scale (see https://klavis.ai)

作者:Klavis-AI正在增长★ 582514个月前更新

在云端运行仓库已归档✓ klavis.ai

Jitsu

Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.

作者:jitsucom广泛使用★ 51364个月前更新

在云端运行✓ 服务方 · jitsu.com
与相似项目对比
本项
MCP Foundry — Build, Test & Publish MCP Servers
World MonitoropenstatusOh My Posh ValidatorStrataJitsu
运行位置在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装
需要密钥否否否否否否
可在 Claude 中按 + 添加否否否否否否
基础检查4/54/44/44/41/44/4
许可证–AGPL-3.0AGPL-3.0MITApache-2.0MIT
价格登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用

作者的 README

打开 README

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

MCP FOUNDRY

Your API. Everywhere AI Works. An independent commercial developer platform for building, hosting, testing, publishing, operating, and ultimately selling real Model Context Protocol integrations.

Production application · Public directory MCP · Product strategy · Architecture · Strategy V3: commercial and execution priorities · legacy 100-initiative backlog

Active publication vs draft editing (18 November 2026)

Published MCP servers now serve an immutable tool snapshot. New tools, edits, OpenAPI imports and revision restores change the editable draft without removing the live server. An explicit Publish transaction creates the next version and switches it atomically; Unpublish still disables an endpoint. API responses expose published_revision and has_unpublished_changes; the Marketplace and public directory display only published definitions.

Limited private upstream API key (BYOK)

In the existing Connections settings workspace, owners can configure one AES-256-GCM encrypted upstream bearer key for an exact public HTTPS API origin. All draft tools for that server must use that host; only private, owner-authenticated MCP calls may inject the key. There are no redirects or secret-bearing public documentation links. Set FOUNDRY_UPSTREAM_ENCRYPTION_KEY to a long random 64-character hex secret in the actual Railway service to enable; until then the UI stays disabled. Save/rotate/revoke deliberately unpublishes that server for retesting before republish. This is not arbitrary OAuth, private-network access or shared end-user auth.

Orders and pricing

V3 routes the public Launch proposal, CA$199 Quickstart, private API request and agency/care enquiry into separately classified buyer records. Operator Desk can use scoped quote presets to create actual, buyer-specific order URLs. An offered quote is not a paid sale; per-quote Checkout requires Foundry Stripe secret plus signed webhook configuration. Existing CA$199 hosted Stripe Payment Link remains independent and active per its merchant record. Do not count unverified transactions as collected revenue.

Strategy V3 — API Agent Launch and customer distribution (18 Nov 2026)

Our commercial wedge is the working AI integration delivered to an API business and its users, not OpenAPI conversion alone. The live CA$199 Public API Quickstart remains available as-is. API Agent Launch is an experimental from CA$799 individually scoped service proposal (not an enabled fixed checkout), covering supported public GET tools, two agreed use cases, a tested client handoff and an optional customer-docs "Use with AI" installation link. The authenticated MCP-native Builder is already available at /mcp/foundry; don't duplicate it. See the complete advisor V3 / 100-action mapping and its English decision summary.

Commercial Clinic V4 — buyer outcomes, reliability and distribution (18 Nov 2026)

The current product is an independent AI-access integration service, not a generic promise to convert every website. The Commercial Clinic strategic blueprint documents 10 hypothetical buyer scenarios, competitor patterns, bounded offers, honest current limits and a revenue-first operating scorecard. The Sales Clinic Playbook defines diagnostic selling, qualification, negotiation and service acceptance. The Reliability and Delivery Contract separates stored PostgreSQL state from MCP transport sessions, third-party source uptime and unverified backup/SLA promises.

New customer acquisition asset: Free API Agent Readiness Assessment (route added on this branch; only call it live once deployed): no registration needed, six-step browser-only self-assessment, 12-point printable checklist and an optional consented enquiry through the existing pilot lead pipeline. This does not automatically create a paid order. Existing CA$199 Quickstart and scoped from CA$799 Launch stay unchanged.

ICP Research CRM & Solution Blueprints (18 Nov 2026)

  • Ten real researched API business accounts with public API docs, contact channels, native MCP position and individual outreach drafts. Research records are not customer endorsements, active leads, messages sent, or paid contracts.
  • Private Operator Desk now has an operator-protected prospect CRM backed by the existing Foundry PostgreSQL service. Research rows are upserted only once and never overwrite manual outreach stages. CSV export is operator-protected; marking contacted requires a recorded real contact receipt.
  • Ten industry Solution Blueprints (route introduced in this release) explain candidate tools, customer task and acceptance, without pretending client projects exist.
  • MCP Doctor engineering and commercial manual converts study into a reusable codebase inspection, tool-curation, evaluation and buyer-discovery practice.

What is real now?

  • Public premium website, developer copy/config, directory backed by PostgreSQL rather than fake listings.
  • Authenticated customer workspace: create/read servers, add GET tool, OpenAPI JSON/YAML import (paste, upload or public HTTPS spec URL with preview before writes), real upstream test, publish private/public endpoint, create/revoke API keys, observed execution usage.
  • Official MCP SDK v2, stateless Streamable HTTP and protocol 2026-07-28.
  • Own public discovery server /mcp/foundry with anonymous read-only search_servers, get_server_tools.
  • With Authorization: Bearer fdy_...: Foundry itself is a builder MCP with list_my_servers, create_server, add_readonly_tool, import_openapi, test_readonly_tool, publish_server, get_server_usage. Every management tool uses the authenticated account's tenant only. No anonymous write permissions.
  • Published managed servers under /mcp/:slug; private servers require owner key.
  • Dedicated PostgreSQL and Railway service; independent GitHub Actions live acceptance for health, API catalog, official SDK read-only discovery, plus full native builder and actual managed tool execution.
  • A live one-time CA$199 public API Quickstart is available through a dedicated Stripe-hosted Payment Link; Foundry's separate custom-order Checkout and recurring subscriptions require merchant credentials/webhook setup. A live purchase link is not evidence of a successful charge, customer or revenue. See Commercial Launch.

Commercial and builder growth surfaces

Foundry now has focused, English-only paths for business API owners, Web3 and onchain data builders, and developers, agencies and community partners. These pages use the same isolated Foundry product and authenticated Studio—no other Noetfield venture is merged.

Two additional source-backed onboarding templates use DEX Screener's public read-only API and the World Bank public country metadata API. Provider rate limits and terms apply; these are examples, not a claim of API-provider sponsorship or a customer deployment.

A first-party opportunity pipeline stores consented, role-specific enquiries in PostgreSQL; only the private Operator Desk can read or qualify them. Partner interest is separate from pilot implementation enquiries, Stripe-paid orders, and verified active developers. See Commercial growth playbook.

Starting locally

Use Node.js 22 and PostgreSQL.

cp .env.example .env

npm install npm run check npm test DATABASE_URL='postgresql://...' PORT=3000 npm start

The backend never silently uses an in-memory customer database. /healthz checks real PostgreSQL connectivity. For production deployment see docs/DEPLOY.md. Secrets belong in infrastructure, not Git.

Build in two ways

Browser — open Studio, register, create server, import or add GET tool, test and publish.

From an MCP client — register in Studio and generate an API key in the API keys tab; then attach https://mcp-foundry-web-production.up.railway.app/mcp/foundry with Bearer authentication. The authenticated tool list enables natural-language server creation, importing and publishing. Public discovery requires no key.

Fastest path to a working MCP server

  1. Create a free account in Studio.
  2. Choose one real-source GitHub / Hacker News starter template. This atomically creates an owned draft server with the appropriate tool and schema.
  3. Open Test, run the example input against the live upstream API, then Publish and copy your own remote MCP URL.
  4. For a custom API integration, use the public implementation enquiry. It stores the requested scope and permission to contact; it is not a checkout or an invented paid order.

See Commercial Launch Contract for the qualified lead workflow and the verified-payment boundary. Privacy notice.

Official MCP Registry distribution

The canonical remote-only manifest is server.json, also served unchanged from the live manifest and well-known discovery. The workflow publish-registry.yml uses the official publisher pinned to v1.8.1, Sigstore artifact verification, GitHub Actions OIDC and an exact official Registry API readback. No long-lived GitHub PAT or fictional npm package is required. An unsuccessful Registry action does not affect the existing production MCP endpoint or customer tools. Verify a listed release only via the real Registry API record for io.github.Noetfield-Systems/mcp-foundry (version 0.1.0). A GitHub manifest, passing unit tests or a CI run that never reached the readback stage are not proof of registry publication.

Manage the full lifecycle

Your Studio can now rename and describe servers, edit/remove tools, unpublish a public or private endpoint instantly, and delete no-longer-needed MCP servers. Changing a tool stages an editable draft while the last published revision stays live. Explicit republish swaps to the tested draft; Unpublish and Delete deliberately revoke access. The directory lists only published tool snapshots.

Private commercial operations

Operator Desk shows genuine account/server usage counts and consented implementation enquiry records. Configure a long random FOUNDRY_ADMIN_TOKEN in the Railway service (never in GitHub), then enter it once into the Desk. The token stays in page memory and is not stored in browser storage. Lead status is an operator classification, not a paid receipt. Without the secret the endpoint fails closed.

OAuth connections and MCP Apps\n\nA constrained GitHub OAuth authorization-code PKCE connector exists for explicitly private MCP servers with encrypted server-side tokens. It remains disabled until a dedicated Foundry GitHub OAuth App client ID/secret

只显示了开头部分;其余内容请在仓库中阅读