266 posts tagged with "Model Context Protocol"
Content about the Model Context Protocol (MCP)
MCP Memory Servers: What Persistent Memory-as-a-Tool Means for a Deploy Agent That Forgets Every Session
MCP memory servers give deploy agents persistent memory any client can share — last good deploys, environment preferences, and incident fixes recalled by retrieval instead of replayed history. The catch: multi-tenant isolation and poisoned-memory attacks that turn one bad fact into a standing prompt injection.
10,000+ MCP Servers in Production: What the 2026 Numbers Say About Treating MCP as Infrastructure, Not a Toy
MCP has crossed 10,000 public servers and 97 million monthly SDK downloads — but benchmarks show the stdio transport collapsing at 20 concurrent connections while Streamable HTTP holds 100% success. This breakdown turns the 2026 numbers into a production checklist: stateless transport, backpressure, real-path health checks, OAuth, and a load-test recipe for deploy and rollback tools.
Railway's Dotenv Diff Review: What Confirm-Before-Apply Env Changes Teach Agent-Driven Deploy Pipelines
Railway's variable edit flow batches env changes, shows a redacted diff, and applies only on confirm. That shape is the governance primitive agent-driven deploy pipelines need before AI agents get write access to production config.
Your Read-Only Tool Is the Sandbox Escape: What Claude Code's /proc/self/environ API-Key Leak Teaches About Agent Deploy Pipelines
Microsoft researchers hid instructions in a GitHub issue comment, steered Claude Code's Action to its unsandboxed Read tool, and walked out with a live API key. Here is the full four-step chain plus a 7-point audit for your own agent deploy pipeline.
CVE-2026-61560: How an Unauthenticated MCP Default Turned a File-Upload Tool Into Full GitLab Account Takeover
A CVSS 9.8 flaw in @zereight/mcp-gitlab chains an unauthenticated SSE transport, an unsanitized file path, and a credential in process memory into full GitLab account takeover. The exploit chain, why the default was the real bug, and a six-item hardening checklist for every MCP server you self-host.
Every Deploy Surface Is Shipping an MCP Server: What a PaaS's Agent Interface Must Expose (and What Keeps It Safe)
TeamCity, Dooor OS, and the PaaS scoreboard all converged on the same contract: a typed MCP tool surface over deploy, rollback, logs, and status. The minimum inventory a git-push PaaS must expose, and the four controls that make it production-safe.
10,000 MCP Servers and 97M Downloads Later, the Bottleneck Is Discovery
MCP passed 10,000 public servers and 97M monthly SDK downloads, so the hard problem is no longer the protocol — it is discovery and trust. What Arcade's brokered runtime and the Coolify agent bridges teach a self-hosted PaaS about shipping a deploy, rollback, and logs server that agents can find and be trusted with.
Half a Billion Downloads Get a Diploma: What MCP's First Certification (MCPA) Signals for Platform Teams
The Agentic AI Foundation's MCPA exam arrives as MCP SDK downloads near half a billion a month. What the blueprint's 50% ops-and-security weighting tells platform teams, what the credential doesn't prove, and three moves to make this quarter.
1 Million Agents in 3 Months: What Notion's Enterprise Agent Surge Means for a PaaS Whose Deploy API Is the Agent's Next Tool Call
Notion customers built 1 million AI agents in three months, yet 69% of enterprises still share credentials across agents. This is the five-item checklist — per-agent identity, scoped tokens, agent-aware quotas, audit attribution, MCP deploy tools — a PaaS deploy API needs before agents become its callers.