266 posts tagged with "Model Context Protocol"
Content about the Model Context Protocol (MCP)
Coolify vs Dokploy on a $5 Hetzner Box: 7-Day Benchmark Numbers — and What Breaks When You Outgrow the Box
A 7-day head-to-head on a $5 Hetzner VPS puts Dokploy idle RAM at 0.8 GB against Coolify v4.0's 1.2 GB, with build times tied — then the numbers stop mattering. The 1–3 vs 4+ app decision rule, what Coolify's MCP server changed, and the second-server ceiling neither panel crosses.
Fly.io Sprites Speak MCP: What $0.07/CPU-Hour With Zero Idle Charge Really Costs Against Owned Hetzner Hardware
A line-by-line recompute of 200 agent sandboxes on Fly Sprites' idle-free meter versus E2B, Daytona, Modal, and owned Hetzner hardware — with the duty-cycle crossover points where each option wins.
100 MCP Servers in Production: What a Fortune 500 Deployment Teaches Self-Hosted Agent Ops
A Fortune 500 bank went from failing AI coding assistants to 100 governed MCP servers in three months. Five practices from that deployment — registry gates, gateway auth, tool consolidation, token budgets, gateway observability — that self-hosted teams should adopt on day one.
What the MCP 2026-07-28 Spec Broke: Your Server's Auth Fix Checklist
The MCP 2026-07-28 spec turned every remote server into a formal OAuth 2.1 resource server, and working servers now fail closed. Here is the six-item fix checklist: metadata endpoint, 401 pointer, audience enforcement, issuer validation, and the DCR-to-CIMD plan.
MCP Went Stateless: What the 2026-07-28 Rewrite Changes for Self-Hosting Agent Tool Servers
MCP's July 2026 spec revision deletes sessions, the initialize handshake, and sticky-routing requirements. A before/after guide to what self-hosted agent tool servers can delete, what replaces sessions, and how to migrate.
12,520 Exposed MCP Servers: A 7-Point Auth Checklist for Shipping a Deploy-Capable MCP Server
Censys found 12,520 MCP servers on the public internet and independent studies put 40% of remote servers at no authentication at all. Here is the seven-default auth checklist that keeps a deploy-capable MCP server out of the next scan.
Railway Runs Your Agents Now: What Cloud Agents on 24/7 VMs Cost vs a Self-Hosted Sandbox
Railway's Cloud Agents put Claude Code and Codex on metered 24/7 VMs with deploy tools built into every session. An always-on agent costs about $245 a month on Railway versus $19 on owned hardware — but utilization, the phone-resume UX, and the lock-in shape matter more than the meter.
Railway Put Postgres HA, PITR, and PgBouncer in the Terminal — and Gave Agents the Keys
Railway's September 2026 CLI release brings Postgres HA, point-in-time recovery, and connection pooling to the terminal with JSON output. Here is how each operation compares to its CloudNativePG equivalent on infrastructure you own, and what it means now that database lifecycles are APIs agents call.
Sprites Meet MCP: How Fly.io Built Agent-Safe Sandboxed Deployment Environments
Fly.io's Sprites now speak MCP: agents get persistent Firecracker microVMs with 300ms checkpoints through sprites.dev/mcp. Here is the six-primitive checklist for agent-safe sandboxes, how E2B, Daytona, Modal, and Vercel compare, and what it takes to build the same on owned hardware.