# MCP Foundry — Build, Test & Publish MCP Servers (remote · mcp-foundry-web-production.up.railway.app)

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

- Trust score: 54/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `mcp-foundry-web-production.up.railway.app`: 54/100 (this document), [markdown](https://verifymcp.io/servers/noetfield-systems-mcp-foundry/mcp-foundry.md), [page](https://verifymcp.io/servers/noetfield-systems-mcp-foundry/mcp-foundry)

## Channel facts

- Endpoint: `https://mcp-foundry-web-production.up.railway.app/mcp/foundry`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS not yet verified: we couldn't read the response headers to check for it.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but we couldn't connect to verify it.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the MCP Foundry — Build, Test & Publish MCP Servers server?

MCP Foundry — Build, Test & Publish MCP Servers is a hosted endpoint at https://mcp-foundry-web-production.up.railway.app/mcp/foundry, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http noetfield-systems-mcp-foundry 'https://mcp-foundry-web-production.up.railway.app/mcp/foundry'
```

### Cursor

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

### VS Code

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

### Codex

```toml
[mcp_servers.noetfield-systems-mcp-foundry]
url = "https://mcp-foundry-web-production.up.railway.app/mcp/foundry"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "noetfield-systems-mcp-foundry": {
      "type": "remote",
      "url": "https://mcp-foundry-web-production.up.railway.app/mcp/foundry",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add noetfield-systems-mcp-foundry --url 'https://mcp-foundry-web-production.up.railway.app/mcp/foundry' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  noetfield-systems-mcp-foundry:
    url: "https://mcp-foundry-web-production.up.railway.app/mcp/foundry"
```

### Netclaw

```json
{
  "McpServers": {
    "noetfield-systems-mcp-foundry": {
      "Transport": "http",
      "Url": "https://mcp-foundry-web-production.up.railway.app/mcp/foundry"
    }
  }
}
```

### Vellum

```bash
assistant mcp add noetfield-systems-mcp-foundry -t streamable-http -u 'https://mcp-foundry-web-production.up.railway.app/mcp/foundry'
```

### Other

```json
{
  "mcpServers": {
    "noetfield-systems-mcp-foundry": {
      "type": "http",
      "url": "https://mcp-foundry-web-production.up.railway.app/mcp/foundry"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 54, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] HSTS header: fail → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.03 → unverified
- [security regression] Transport: pass → fail
- [security] Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Schema quality: 0 → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-11-19 (score 54, −4)

- [functional improvement] Schema quality: 25 → 21
- [functional improvement] Stability: unverified → 0.03
- [functional] The server now declares the “resources” capability
- [functional] First check of Capabilities: pass
- [functional] First check of Schema quality: 0
- [functional] New resource “MCP Foundry Studio”
- [functional] New tool “open_foundry_app”

### 2026-11-18 (score 58)

First indexed and scored.

## MCP tools (3)

### `open_foundry_app` (~26 tokens)

Open MCP Foundry Studio

Open interactive Foundry directory and authenticated Builder workspace in a compatible MCP Apps host.

### `search_servers` (~25 tokens)

Search published public MCP servers in MCP Foundry

Input parameters:

- `query` (string)

### `get_server_tools` (~26 tokens)

List tools published by one MCP Foundry server

Input parameters:

- `slug` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/noetfield-systems-mcp-foundry/mcp-foundry#diagnostics

## Score history

- 2026-11-21: 54
- 2026-11-20: 54
- 2026-11-19: 54
- 2026-11-18: 58

## Common questions

### What is the MCP Foundry — Build, Test & Publish MCP Servers server?

MCP Foundry — Build, Test & Publish MCP Servers is listed in the public MCP registry as io.github.Noetfield-Systems/mcp-foundry. Build, test, publish and manage real MCP servers from APIs with a live developer studio. This page covers its hosted endpoint (https://mcp-foundry-web-production.up.railway.app/mcp/foundry).

### Is the MCP Foundry — Build, Test & Publish MCP Servers server safe to use?

MCP Foundry — Build, Test & Publish MCP Servers scores 54 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the MCP Foundry — Build, Test & Publish MCP Servers server expose?

MCP Foundry — Build, Test & Publish MCP Servers exposes 3 tools: open_foundry_app, search_servers, get_server_tools. Their descriptions and schemas cost roughly 77 tokens of context every time the server is loaded.

### Does the MCP Foundry — Build, Test & Publish MCP Servers server require authentication?

Its publisher declares no required credentials for MCP Foundry — Build, Test & Publish MCP Servers. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### Is the MCP Foundry — Build, Test & Publish MCP Servers server still maintained?

MCP Foundry — Build, Test & Publish MCP Servers is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 19 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the MCP Foundry — Build, Test & Publish MCP Servers server?

VerifyMCP ran 4 checks on MCP Foundry — Build, Test & Publish MCP Servers, covering TLS certificate, HTTPS, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about MCP Foundry — Build, Test & Publish MCP Servers: Authorization, HSTS header, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://mcp-foundry-web-production.up.railway.app/mcp/foundry
- Repository: https://github.com/Noetfield-Systems/MCP
- Changelog RSS feed: https://verifymcp.io/servers/noetfield-systems-mcp-foundry/mcp-foundry.xml
- Changelog JSON feed: https://verifymcp.io/servers/noetfield-systems-mcp-foundry/mcp-foundry/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/noetfield-systems-mcp-foundry/mcp-foundry.json
- HTML version of this page: https://verifymcp.io/servers/noetfield-systems-mcp-foundry/mcp-foundry
