reference

DE//AGENT currently lists 3 resources under reference: 2 mcp servers, 1 tutorial. Everything below is derived from the live registry — counts, capabilities, verification state and security posture come from the curated records, never from marketing copy.

Documented learning objectives across these resources:

• Decompose a reference architecture into ingest, store, process, and serve — via Read reference architectures like an engineer — AWS as precedent
• Connect each architectural choice to a Well-Architected pillar — via Read reference architectures like an engineer — AWS as precedent
• Re-state a vendor diagram in mechanism vocabulary to test real understanding — via Read reference architectures like an engineer — AWS as precedent

These resources map to stages: System Design (1), Agentic Data Engineering (2). Follow the four-phase roadmap to place this topic inside a progression instead of learning it in isolation.

Every entry, its shape and its trust state — sorted by the registry's composite score. This table is the honest version of a marketing comparison: no sponsored placements, no unverifiable claims.

How scores are computed: source quality score.

Highest composite score first:

1. Filesystem MCP Server score 47.5 — beginner
2. Fetch MCP Server score 46 — beginner
3. Read reference architectures like an engineer — AWS as precedent score 34.15 — intermediate

Scores rank provenance, completeness and trust — read how verification works before adopting anything.

Start here if you're new: Filesystem MCP Server, Fetch MCP Server.

Security-flagged entries: Filesystem MCP Server (1 flag), Fetch MCP Server (2 flags). Flags mean the record declares capabilities like credential use or write access — read the security posture on each page before connecting.

• Filesystem MCP Server — Reference server that exposes a sandboxed set of directories as readable and (optionally) writable tools. Useful for pipelines that operate on local files. details
• Fetch MCP Server — Retrieves a URL and converts it to markdown for the model. Commonly used to read documentation during a task. details
• Read reference architectures like an engineer — AWS as precedent — Reference architectures are precedent, not homework. This lesson teaches a reading method: name the moving parts, find the pillar each choice defends, spot the serverless data lake… details

Real install commands from the registry — read the source before running any of them:

npx -y @modelcontextprotocol/server-filesystem /path/to/allowed/dir

Filesystem MCP Server — review first

uvx mcp-server-fetch

Fetch MCP Server — review first

Adjacent topics: mcp (2 shared).

Study path: the roadmap places this topic in a progression · the scoring model explains the numbers · the trust rule catalog shows every security check these entries passed through.