# DATA/AGENT FOUNDRY (remote · foundry-api-production-95ae.up.railway.app)

Free catalogue; paid historical software/security evidence. No current-risk assessment.

- Trust score: 61/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `foundry-api-production-95ae.up.railway.app`: 61/100 (this document), [markdown](https://verifymcp.io/servers/reztek-creator-data-agent-foundry/foundry-api-production-95ae.md), [page](https://verifymcp.io/servers/reztek-creator-data-agent-foundry/foundry-api-production-95ae)

## Channel facts

- Endpoint: `https://foundry-api-production-95ae.up.railway.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1-mcp-proposal`

## 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-05.

- **Endpoint Security**: 11/100
  - TLS not yet verified: we couldn't open a connection to check the certificate.
  - 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 DATA/AGENT FOUNDRY MCP server?

DATA/AGENT FOUNDRY is a hosted endpoint at https://foundry-api-production-95ae.up.railway.app/mcp, 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 reztek-creator-data-agent-foundry 'https://foundry-api-production-95ae.up.railway.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "reztek-creator-data-agent-foundry": {
      "url": "https://foundry-api-production-95ae.up.railway.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "reztek-creator-data-agent-foundry": {
      "type": "http",
      "url": "https://foundry-api-production-95ae.up.railway.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.reztek-creator-data-agent-foundry]
url = "https://foundry-api-production-95ae.up.railway.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "reztek-creator-data-agent-foundry": {
      "type": "remote",
      "url": "https://foundry-api-production-95ae.up.railway.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add reztek-creator-data-agent-foundry --url 'https://foundry-api-production-95ae.up.railway.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  reztek-creator-data-agent-foundry:
    url: "https://foundry-api-production-95ae.up.railway.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "reztek-creator-data-agent-foundry": {
      "Transport": "http",
      "Url": "https://foundry-api-production-95ae.up.railway.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add reztek-creator-data-agent-foundry -t streamable-http -u 'https://foundry-api-production-95ae.up.railway.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "reztek-creator-data-agent-foundry": {
      "type": "http",
      "url": "https://foundry-api-production-95ae.up.railway.app/mcp"
    }
  }
}
```

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-04 (score 61, 0)

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

### 2026-11-03 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 60, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 59, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 58, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 57, 0)

- [security] Tool “foundry_products” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 67 → 94
- [functional improvement] Stability: unverified → 0.03
- [cosmetic] “foundry_products” added an optional parameter “product_id”
- [cosmetic] “foundry_products” added an optional parameter “subject”
- [cosmetic] “foundry_products” added an optional parameter “task”
- [cosmetic] “foundry_products” added an optional parameter “view”

### 2026-10-26 (score 57)

First indexed and scored.

## MCP tools (4)

### `foundry_products` (~164 tokens)

Free public discovery. Use {"view":"tasks","task":"exact_historical_evidence","subject":"postgresql"} to choose by historical task and held output, or {"view":"summary","limit":64} for the short offer index. Read {"product_id":"<exact listed ID>"} alone for the public contract before advertised selectors or a quote. Omitting view/product_id preserves the full catalogue, default3 and limit1..64/next_cursor. Zero task cards is not zero vulnerabilities; a summary or schema enum is not MATCH or current applicability.

Input parameters:

- `cursor` (string)
- `limit` (integer)
- `product_id` (string)
- `subject` (string)
- `task` (string)
- `view` (string)

### `foundry_selectors` (~72 tokens)

Discover exact held historical request parameters for a currently configured listed product. Free, no payment or purchased evidence; use next_cursor and exact filters. Currentness remains UNKNOWN.

Input parameters:

- `cursor` (string)
- `filters` (object)
- `limit` (integer)
- `product_id` (string, required)

### `foundry_purchase` (~52 tokens)

Buy a configured public product by product_id and its exact business body. Generic clients receive a payment challenge; paying requires an external authorized client.

Input parameters:

- `body` (object, required)
- `product_id` (string, required)

### `foundry_purchase_read` (~59 tokens)

Read/recover this exact original purchase through existing HTTP READ authentication. Never signs or settles. Supply cursor for an existing result page.

Input parameters:

- `authorization_id` (string, required)
- `cursor` (string)
- `original_request` (object, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/reztek-creator-data-agent-foundry/foundry-api-production-95ae#diagnostics

## Score history

- 2026-11-05: 61
- 2026-11-04: 61
- 2026-11-03: 61
- 2026-11-02: 60
- 2026-11-01: 60
- 2026-10-31: 59
- 2026-10-30: 59
- 2026-10-29: 58
- 2026-10-28: 58
- 2026-10-27: 57
- 2026-10-26: 57

## Common questions

### What is the DATA/AGENT FOUNDRY MCP server?

DATA/AGENT FOUNDRY is an MCP server listed in the public MCP registry as io.github.Reztek-creator/data-agent-foundry. Free catalogue; paid historical software/security evidence. No current-risk assessment. This page covers its hosted endpoint (https://foundry-api-production-95ae.up.railway.app/mcp).

### Is the DATA/AGENT FOUNDRY MCP server safe to use?

DATA/AGENT FOUNDRY scores 61 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 DATA/AGENT FOUNDRY MCP server expose?

DATA/AGENT FOUNDRY exposes 4 tools: foundry_products, foundry_selectors, foundry_purchase, foundry_purchase_read. Their descriptions and schemas cost roughly 347 tokens of context every time the server is loaded.

### Does the DATA/AGENT FOUNDRY MCP server require authentication?

Its publisher declares no required credentials for DATA/AGENT FOUNDRY. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### Is the DATA/AGENT FOUNDRY MCP server still maintained?

DATA/AGENT FOUNDRY is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 3 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://foundry-api-production-95ae.up.railway.app/mcp
- Website: https://foundry-api-production-95ae.up.railway.app/agents/
- Changelog RSS feed: https://verifymcp.io/servers/reztek-creator-data-agent-foundry/foundry-api-production-95ae.xml
- Changelog JSON feed: https://verifymcp.io/servers/reztek-creator-data-agent-foundry/foundry-api-production-95ae.json
- HTML version of this page: https://verifymcp.io/servers/reztek-creator-data-agent-foundry/foundry-api-production-95ae