{
  "schema_version": "1.1",
  "id": "atlas-mcp",
  "slug": "mcp",
  "title": "MCP",
  "url": "https://feed7.dev/atlas/mcp",
  "current_answer": "Model Context Protocol — the open standard for connecting agents to tools, data, and memory.",
  "implementation_consequence": "MCP is how context stops being copy-paste. Working servers matter more than spec debates.",
  "agent_context": "Prefer working MCP servers with auditable schemas. Memory servers should have eviction policies before you trust them on large projects.",
  "confidence": "editorial",
  "last_verified": null,
  "last_updated": "2026-06-30T00:00:00.000Z",
  "evidence": [
    {
      "schema_version": "1.1",
      "id": "p3",
      "slug": "mcp-memory-server",
      "url": "https://feed7.dev/p/mcp-memory-server",
      "title": "mcp-memory: a working memory server for agent sessions",
      "why_included": "Persists agent memory across sessions with a small, auditable schema.",
      "summary": "Drop-in MCP server that stores per-project facts an agent can recall next session. Small JSON schema, local-first, no cloud dependency.",
      "practical_implication": "Your agent stops re-learning the project every session. Worth the 4-minute setup on any repo you touch weekly.",
      "agent_context": "mcp-memory stores per-project facts an agent can recall next session. Tested on macOS + Cursor: setup ~4 min, recall reliable for <500 facts. Limitation: no eviction policy yet.",
      "source": {
        "name": "GitHub",
        "url": "https://github.com/f7-labs/mcp-memory",
        "published_at": "2026-06-30T00:00:00.000Z"
      },
      "source_class": "tool",
      "content_type": "GitHub Repo",
      "layer": "context",
      "domains": [
        "coding"
      ],
      "topics": [
        "mcp",
        "agent-memory"
      ],
      "verification": {
        "status": "founder_tested",
        "label": "Founder Tested",
        "method": "founder_test",
        "verified_at": "2026-06-28T00:00:00.000Z"
      },
      "uncertainty": [
        "No eviction policy; unbounded growth on large projects."
      ],
      "connected_context": null,
      "lifecycle": "New",
      "published_at": "2026-06-30T00:00:00.000Z",
      "modified_at": "2026-06-30T00:00:00.000Z",
      "supersedes": [],
      "expires_at": null,
      "formats": {
        "html": "https://feed7.dev/p/mcp-memory-server",
        "json": "https://feed7.dev/p/mcp-memory-server.json",
        "markdown": "https://feed7.dev/p/mcp-memory-server.md"
      }
    },
    {
      "schema_version": "1.1",
      "id": "p11",
      "slug": "ctxlint-repo",
      "url": "https://feed7.dev/p/ctxlint-repo",
      "title": "ctxlint: a linter for agent context files",
      "why_included": "Lints CLAUDE.md / AGENTS.md / rules files for staleness, contradiction, and dead links.",
      "summary": "CLI that checks agent context files: flags stale dates, contradicting rules, dead links, and files over a token budget. CI-ready. Repo builds and tests pass.",
      "practical_implication": "Context files rot silently. Run ctxlint in CI so your agent instructions stay as maintained as your code.",
      "agent_context": "ctxlint lints agent context files (CLAUDE.md, AGENTS.md): staleness, contradictions, dead links, token budget. Add to CI beside your linter.",
      "source": {
        "name": "GitHub",
        "url": "https://github.com/ctxtools/ctxlint",
        "published_at": "2026-06-23T00:00:00.000Z"
      },
      "source_class": "tool",
      "content_type": "GitHub Repo",
      "layer": "context",
      "domains": [
        "coding"
      ],
      "topics": [
        "context-engineering"
      ],
      "verification": {
        "status": "repo_verified",
        "label": "Repo Verified",
        "method": "repo_review",
        "verified_at": null
      },
      "uncertainty": [
        "Maintained by a single author; bus factor 1."
      ],
      "connected_context": null,
      "lifecycle": "New",
      "published_at": "2026-06-23T00:00:00.000Z",
      "modified_at": "2026-06-23T00:00:00.000Z",
      "supersedes": [],
      "expires_at": null,
      "formats": {
        "html": "https://feed7.dev/p/ctxlint-repo",
        "json": "https://feed7.dev/p/ctxlint-repo.json",
        "markdown": "https://feed7.dev/p/ctxlint-repo.md"
      }
    },
    {
      "schema_version": "1.1",
      "id": "auto-f834153d50",
      "slug": "vercel-mcp-can-now-deploy-code-f834153d50",
      "url": "https://feed7.dev/p/vercel-mcp-can-now-deploy-code-f834153d50",
      "title": "Vercel MCP can now deploy code",
      "why_included": "Make deployment an explicit reviewed final step, and verify the background build rather than treating a returned URL as completion.",
      "summary": "Vercel’s MCP server can deploy agent-built code to new or existing projects and return a shareable URL, extending chat-based coding workflows through delivery.",
      "practical_implication": "Builders using Claude, Cursor, or another MCP client can make deployment an explicit final agent step, but should preserve review and permission boundaries before shipping generated changes.",
      "agent_context": "The Vercel MCP server now exposes **deploy_to_vercel** for deployment to **new or existing projects**. It detects the framework, installs dependencies, builds the code, and returns a shareable URL while the build continues.\n\nBuilders using Claude, Cursor, or another MCP client can make deployment an explicit final agent step, but should preserve review and permission boundaries before shipping generated changes.\n\nThe material does not describe approval controls, rollback behavior, failure handling, or which project settings the tool may change. A returned URL can precede completion of the background build.",
      "source": {
        "name": "Vercel",
        "url": "https://vercel.com/changelog/vercel-mcp-can-now-deploy-code",
        "published_at": "2026-07-23T00:00:00.000Z"
      },
      "source_class": "blog_post",
      "content_type": "Engineering Post",
      "layer": "infra",
      "domains": [
        "coding"
      ],
      "topics": [
        "mcp",
        "tool-use",
        "cloud-agents"
      ],
      "verification": {
        "status": "official_source",
        "label": "Official Source",
        "method": "source_feed",
        "verified_at": null
      },
      "uncertainty": [],
      "connected_context": null,
      "lifecycle": "New",
      "published_at": "2026-07-23T00:00:00.000Z",
      "modified_at": "2026-07-23T00:00:00.000Z",
      "supersedes": [],
      "expires_at": null,
      "formats": {
        "html": "https://feed7.dev/p/vercel-mcp-can-now-deploy-code-f834153d50",
        "json": "https://feed7.dev/p/vercel-mcp-can-now-deploy-code-f834153d50.json",
        "markdown": "https://feed7.dev/p/vercel-mcp-can-now-deploy-code-f834153d50.md"
      }
    }
  ],
  "conflicting_sources": [],
  "superseded_claims": [],
  "corpus_evidence": [
    {
      "title": "MCP Apps: Extending the Frontier — Ido Salomon & Liad Yosef",
      "url": "https://www.youtube.com/watch?v=-jY2T2PiJBE",
      "source_name": "AI Engineer",
      "published_at": "2026-08-02T23:30:06+00:00",
      "summary": "MCP Apps let servers return sandboxed, interactive UI instead of text alone while the host retains control of prompts and tool calls—a useful pattern for agent workflows needing charts or controls."
    },
    {
      "title": "MCP Tasks (async): Why Aren't Any Agents Supporting Them? — Cornelia Davis, Temporal",
      "url": "https://www.youtube.com/watch?v=s4r6nk5WsZw",
      "source_name": "AI Engineer",
      "published_at": "2026-08-02T20:00:06+00:00",
      "summary": "MCP Tasks aim to make long-running tool calls durable across disconnects and crashes. The proposed V2 removes session-heavy state, but polling scale and implementation complexity remain unresolved."
    },
    {
      "title": "Vercel MCP now supports the 2026-07-28 MCP specification",
      "url": "https://vercel.com/changelog/vercel-mcp-now-supports-the-2026-07-28-mcp-specification",
      "source_name": "Vercel",
      "published_at": "2026-07-31T00:00:00+00:00",
      "summary": "Vercel MCP now serves the 2026-07-28 and 2025 protocols from one endpoint, letting newer clients adopt stateless requests and revised authorization without breaking older setups."
    },
    {
      "title": "Latest MCP spec now supported in mcp-handler",
      "url": "https://vercel.com/changelog/latest-mcp-spec-now-supported-in-mcp-handler",
      "source_name": "Vercel",
      "published_at": "2026-07-30T00:00:00+00:00",
      "summary": "mcp-handler 2.0 adds the stateless 2026 MCP protocol and SDK v2 while keeping 2025 Streamable HTTP clients working, but drops HTTP+SSE and raises upgrade requirements."
    },
    {
      "title": "We Vetted 2000 AI Skills Before They Reached Developers — Lucas Palma, Nubank",
      "url": "https://www.youtube.com/watch?v=iKQ78wyJEXU",
      "source_name": "AI Engineer",
      "published_at": "2026-07-29T22:00:06+00:00",
      "summary": "Treat agent skills as supply-chain dependencies. Nubank scans them locally and in CI with deterministic rules plus LLM review, then gates marketplace distribution and feeds findings into vulnerability management."
    },
    {
      "title": "AI on Your Lakehouse: Context Comes in Shapes, Not Queries — Zach Blumenfeld, Neo4j",
      "url": "https://www.youtube.com/watch?v=kRkcNOsRyYg",
      "source_name": "AI Engineer",
      "published_at": "2026-07-23T07:00:23+00:00",
      "summary": "Graph-shaped context can expose relationships and document structure that vector search or Text-to-SQL misses. Treat it as an additional retrieval surface, then benchmark it against your own data."
    },
    {
      "title": "Vercel MCP now supports purchases",
      "url": "https://vercel.com/changelog/vercel-mcp-now-supports-purchases",
      "source_name": "Vercel",
      "published_at": "2026-07-21T00:00:00+00:00",
      "summary": "Vercel MCP can now buy plans, credits, add-ons, and domains from an AI assistant, but it must disclose pricing and obtain confirmation before completing a charge."
    },
    {
      "title": "Panniantong/Agent-Reach",
      "url": "https://github.com/Panniantong/Agent-Reach",
      "source_name": "GitHub",
      "published_at": null,
      "summary": "Agent Reach installs, checks, and routes web-access tools for coding agents, reducing the setup work behind research across social platforms, video sites, GitHub, RSS, and the open web."
    },
    {
      "title": "Agent Runs now available in the Vercel MCP and CLI",
      "url": "https://vercel.com/changelog/agent-runs-vercel-mcp-cli",
      "source_name": null,
      "published_at": null,
      "summary": "Your coding agent can now pull its own Agent Runs traces—reasoning, tool calls, token usage—from Vercel via MCP or CLI, so it can debug its runs and refine skills from real production behavior."
    },
    {
      "title": "Gemini Spark updates: macOS launch, connected apps and more",
      "url": "https://blog.google/innovation-and-ai/products/gemini-app/gemini-spark-updates-june-2026/",
      "source_name": null,
      "published_at": null,
      "summary": "Gemini Spark lands on macOS (US, AI Ultra beta) and gains custom MCP support plus connectors for Tasks, Keep, Canva and Dropbox — Google's assistant now speaks the protocol your agent tooling already uses."
    },
    {
      "title": "Expanding Managed Agents in Gemini API: background tasks, remote MCP and more",
      "url": "https://blog.google/innovation-and-ai/technology/developers-tools/expanding-managed-agents-gemini-api/",
      "source_name": null,
      "published_at": null,
      "summary": "Gemini Managed Agents can now run asynchronously, connect to remote MCP servers, call client-side functions, and rotate credentials without losing sandbox state."
    },
    {
      "title": "Muse Spark 1.1 is now available on AI Gateway",
      "url": "https://vercel.com/changelog/muse-spark-1-1-is-now-available-on-ai-gateway",
      "source_name": null,
      "published_at": null,
      "summary": "Muse Spark 1.1 gives agent builders a 1M-token multimodal model with parallel tool calls, MCP support, and the option to run as a main agent or subagent."
    },
    {
      "title": "ChromeDevTools/chrome-devtools-mcp",
      "url": "https://github.com/ChromeDevTools/chrome-devtools-mcp",
      "source_name": "GitHub",
      "published_at": null,
      "summary": "Chrome DevTools MCP gives coding agents direct access to browser automation, network data, console errors, screenshots, and performance traces, with privacy controls worth setting explicitly."
    }
  ]
}