Skip to content

DATA/AGENT FOUNDRY MCP server

io.github.Reztek-creator/data-agent-foundryReztek-creatorstreamable-httpv1.0.1-mcp-proposalScanned

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

4 tools: 2 do something that can't be undone and 2 change things.

Tools: 0 delete, 2 irreversible, 2 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here do something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the DATA/AGENT FOUNDRY MCP server can do

The DATA/AGENT FOUNDRY MCP server is published by the GitHub account Reztek-creator. It has 4 tools. It can do things that cannot be undone, such as sending, paying or publishing (foundry_purchase and foundry_purchase_read) and create or change data (2 tools: foundry_products and foundry_selectors), but cannot delete data. None of its tools only reads.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 9, 2026, version 1.0.1-mcp-proposal.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Can't be undone 2Claude Code: ask
  • foundry_purchaseBuy a configured public product by product_id and its exact business body.No findings

    Why it is in this group

    • The name "foundry_purchase" says "purchase": a word that usually means money moves, which cannot be taken back.
    Description, as the server wrote it
    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.
  • foundry_purchase_readRead/recover this exact original purchase through existing HTTP READ authentication.No findings

    Why it is in this group

    • The name "foundry_purchase_read" says "purchase": a word that usually means money moves, which cannot be taken back.
    Description, as the server wrote it
    Read/recover this exact original purchase through existing HTTP READ authentication. Never signs or settles. Supply cursor for an existing result page.
Changes things 2Claude Code: ask
  • foundry_productsFree public discovery.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • foundry_selectorsDiscover exact held historical request parameters for a currently configured listed product.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 18, 2026, 16:24 UTC, unchanged since Oct 27, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
4
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (2 irreversible, 2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://foundry-api-production-95ae.up.railway.app/mcp: tools/list returned 4 tools to an anonymous client, including foundry_purchase (irreversible), foundry_purchase_read (irreversible), foundry_products (write), foundry_selectors (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 changed.~1 changedView diff

Install

Pinned to version 1.0.1-mcp-proposal. Values in angle brackets are yours to fill in.

claude mcp add --transport http data-agent-foundry https://foundry-api-production-95ae.up.railway.app/mcp
claude mcp add --transport http data-agent-foundry https://foundry-api-production-95ae.up.railway.app/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__data-agent-foundry__foundry_products",
      "mcp__data-agent-foundry__foundry_selectors",
      "mcp__data-agent-foundry__foundry_purchase",
      "mcp__data-agent-foundry__foundry_purchase_read"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as data-agent-foundry. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.Reztek-creator/data-agent-foundry/verify?hash=7a70eafcb01d92c4101028bd254cfcf2b8792a4c7d0785c25b3ef1477a9e6c95" | jq -e '.changed == false'

Pinned hash 7a70eafcb01d, from Nov 9, 2026, 12:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.Reztek-creator/data-agent-foundry/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.Reztek-creator/data-agent-foundry
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.Reztek-creator/data-agent-foundry.svg)](https://radar.anlyon.com/servers/io.github.Reztek-creator/data-agent-foundry)

Source: MCP Registry. Synced Oct 26, 2026, 19:19 UTC.

DATA/AGENT FOUNDRY MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the DATA/AGENT FOUNDRY MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the DATA/AGENT FOUNDRY MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the DATA/AGENT FOUNDRY MCP server do things that cannot be undone?

Yes. 2 tools can send, pay, publish or merge: foundry_purchase and foundry_purchase_read.

What tools does the DATA/AGENT FOUNDRY MCP server have?

4 tools: 2 irreversible, 2 write. foundry_purchase, foundry_purchase_read, foundry_products and foundry_selectors.

Does the DATA/AGENT FOUNDRY MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the DATA/AGENT FOUNDRY MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the DATA/AGENT FOUNDRY MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 9, 2026. Every change is on this page and in its Atom feed.