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.
Available components
Last scanned (13 hours ago)
Scores higher than 44% of remote servers
Unreachable for 2 days in a row. Last reached 19 Nov 2026.
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. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
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.
Checks we ran (4)
- TLS certificate
- HTTPS
- DNSSEC
- Transport
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HSTS header in Endpoint SecurityHSTS not yet verified: we couldn't read the response headers to check for it.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.03 → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Schema quality: 0 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 19 Nov 26 −4
- Schema quality: 25 → 21 ▲ functional
- 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” functional
- 18 Nov 26 58
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://mcp-foundry-web-production.up.railway.app/mcp/foundry
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.up.railway.app | CN=YE2,O=Let's Encrypt,C=US | 27 Sept 2026 | 26 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 618edc56941aa1165ddb080bf9f799eb7c1 |
| SANs: *.up.railway.app, up.railway.app | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp-foundry-web-production.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| app. | DS published | 23684 | 8 | Verified |
| railway.app. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp-foundry-web-production.up.railway.app/mcp/foundry | Unreachable | ||
| http (plaintext) | http://mcp-foundry-web-production.up.railway.app/mcp/foundry | HTTPS enforced | 301 | https://mcp-foundry-web-production.up.railway.app/mcp/foundry |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_server_tools ~26
List tools published by one MCP Foundry server
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
No output schema declared.
No examples provided.
open_foundry_app Open MCP Foundry Studio ~26
Open interactive Foundry directory and authenticated Builder workspace in a compatible MCP Apps host.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_servers ~25
Search published public MCP servers in MCP Foundry
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | – |
No output schema declared.
No examples provided.
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.
remote · mcp-foundry-web-production.up.railway.app
claude mcp add --transport http noetfield-systems-mcp-foundry 'https://mcp-foundry-web-production.up.railway.app/mcp/foundry'
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.