DEVELOPER DOCUMENTATION VERSION 0.1.0 · MCP 2026-07-28
OFFICIAL REGISTRY LISTED · REMOTE STREAMABLE HTTP

Connect once.
Build for agents.

MCP Foundry publishes real HTTPS tools from your APIs. Start without payment, test an actual upstream response, then attach the resulting MCP endpoint to a compatible AI client.

PUBLIC CONNECTIONhttps://mcp-foundry-web-production.up.railway.app/mcp/foundryOfficial Registry v0.1.0

The public directory works without a key. Add a personal Foundry API key to unlock authenticated creation, import, test and publication tools.

01 / QUICKSTART

From zero to a working endpoint.

01

Register in Studio. Create an account, then select a live-source starter: Hacker News, GitHub public profile or public repository. The starter creates a draft MCP server and its first GET tool.

02

Verify the tool. Open your server’s Test tab and run a real upstream API request. A failed upstream status is reported as a failure rather than a synthetic success.

03

Publish and copy. Publish public or private, then copy the unique HTTPS endpoint at /mcp/your-server. Private endpoints require an account-issued bearer key.

04

Connect an AI client. Use a compatible MCP client with Streamable HTTP. When invoked, real tool-call usage is recorded in your own workspace.

Open the builder ↗
02 / CONNECT

Remote MCP configuration.

Client configuration formats vary. The following is an illustrative generic HTTP MCP configuration; refer to your client’s current documentation for exact fields and authentication support.

PUBLIC DIRECTORY EXAMPLE
{
  "mcpServers": {
    "foundry": {
      "type": "http",
      "url": "https://mcp-foundry-web-production.up.railway.app/mcp/foundry"
    }
  }
}

For private server access and builder tools, create a personal API key in Studio → API keys. Add its Authorization header through the client’s supported credentials configuration. Never put real tokens into public screenshots, GitHub commits or GET URLs.

AUTHENTICATED CLIENT EXAMPLE
{
  "mcpServers": {
    "foundry": {
      "type": "http",
      "url": "https://mcp-foundry-web-production.up.railway.app/mcp/foundry",
      "headers": {
        "Authorization": "Bearer YOUR_PERSONAL_FOUNDRY_API_KEY"
      }
    }
  }
}
03 / NATIVE BUILDER

Foundry is an MCP server itself.

Use a client with the personal Foundry API key and the same remote directory endpoint. Public tools remain open; authenticated tools are restricted to your own workspace.

search_serversPublic directory search
get_server_toolsPublic published tools
create_serverMake a draft server
add_readonly_toolRegister a GET tool
import_openapiImport JSON GET operations
test_readonly_toolCall the real upstream API
publish_serverActivate public/private endpoint
get_server_usageRead observed tool executions

Tool creation and publishing do not automatically issue tokens, move funds or perform customer API write actions. Unpublish and lifecycle controls are also available in Studio.

04 / OFFICIAL CLIENT SDK

Connect directly from Node.js.

Use the published official MCP client package and a Node.js 22+ environment. This example discovers the anonymous directory tools. For private access, provide a bearer header using your application’s secret handling.

NODE.JS · STREAMABLE HTTP
import {Client, StreamableHTTPClientTransport}
  from '@modelcontextprotocol/client';

const client = new Client({
  name: 'my-foundry-client',
  version: '1.0.0'
});
const transport = new StreamableHTTPClientTransport(
  new URL('https://mcp-foundry-web-production.up.railway.app/mcp/foundry')
);

try {
  await client.connect(transport);
  const {tools} = await client.listTools();
  console.log(tools.map(tool => tool.name));
} finally {
  await client.close();
}
05 / OFFICIAL DISCOVERY

Find us in the MCP Registry.

Foundry is registered under io.github.Noetfield-Systems/mcp-foundry, with source-verified GitHub identity and an HTTPS remote transport. This is a listing of real metadata, not a certification of security or evidence of customers.

06 / EXECUTION BOUNDARIES

Real execution. Explicit limits.

HTTPS GET onlyNo writes or payments by tool proxy
Public IP onlySSRF-resistant pinned IPv4 lookup
8 secondsUpstream timeout
256 KiBMaximum response body
Private scopesOwner-specific keys and tools
Observed usageTool call ≠ unique customer

Some public upstream APIs, including GitHub, impose anonymous request limits. A 403 or rate limit from an upstream API is reported as an error and must not be interpreted as a successful tool call.

07 / IMPLEMENTATION

Need a custom MCP integration?

We also offer scoped development proposals for existing APIs. You can request an implementation assessment through the form; no payment is charged merely for submitting the request. The current paid subscription checkout is not enabled without completed production billing configuration.

Request implementation ↗

For product source, CI evidence and public issues see GitHub.