266 posts tagged with "Model Context Protocol"
Content about the Model Context Protocol (MCP)
One Shared Quota Took Down Every Connector: What a 402 on MCP Initialize Teaches About Self-Hosting Agent Tools
On September 9, 2026, one exhausted shared quota answered MCP initialize with HTTP 402 and took every OptimNow connector down at once. The 14-file move to Fly.io scale-to-zero is a complete template for self-hosting production agent tools — here is the incident anatomy and the checklist.
CI Gets an MCP Server: What TeamCity's and Dooor OS's Deploy-via-MCP Tools Mean for a PaaS API That Agents Still Have to Scrape
TeamCity and Dooor OS now expose builds, deploys, and logs as MCP tools. Here is what they expose, why agents will operate your platform with or without you, and the checklist for a versioned, scoped, auditable agent interface.
Detectify Turned Its Scanner Into an Agent Tool: What 'Call the Scanner Like a Test Runner' Means for Your Deploy Pipeline
Detectify's May 2026 MCP Server hands security findings to coding agents as structured tasks with validation scans. How the Find & Fix loop works, what a scan phase between build and promote looks like for a git-push PaaS, and what stays human.
Google Just Normalized the Governed Agent Endpoint: What Its Home and UN Data Commons MCP Servers Mean for Your Self-Hosted PaaS Roadmap
Google shipped first-party MCP servers for Home and UN data in a single week. Here is the six-part governance bar they normalized, and what it demands from any self-hosted platform shipping an agent endpoint.
Someone Already Wrote the Hetzner MCP Server: What a Live Changelog Audit Teaches Deploy-From-Chat
A community MCP server mapping the Hetzner Cloud, Storage Box, and Robot APIs survived six provider changelog deltas in three months with zero broken tools — thanks to a published endpoint audit, pass-through writes, and an eval that expects deprecation. Here is what that discipline teaches any deploy-from-chat roadmap, and the tenant-scoping and audit-logging layer a PaaS still has to build itself.
Laravel MCP 1.0 Ships: Your Laravel App Is Now an Agent Tool — What Changes on the Deploy Surface
Laravel MCP 1.0 adopts the stateless MCP 2026-07-28 spec with searchable tool catalogs, cache hints, and mandatory OAuth PKCE — plus header validation that 400s old clients. Here is the upgrade checklist and what per-app MCP servers mean for anyone operating Laravel apps.
Your MCP Deploy Tool's dry_run Flag Is a Suggestion, Not a Lock
MCP tool annotations like readOnlyHint are advisory hints for the client, not enforcement — nothing in the protocol stops a caller from overriding dry_run, tenant_id, or target_environment. A three-line server-side pattern (derive from the session, reject client values, log the attempt) and where host-authority receipts belong.
MCP Just Got Its Biggest Update Ever: What Stateless Servers Mean for Self-Hosting Deploy-from-Chat
The 2026-07-28 MCP spec killed sessions, sticky routing, and handshake affinity — September coverage calls it the biggest update since launch. For self-hosters, that means an infrastructure MCP server is now an ordinary HTTP service behind the same load balancer as everything else.
454 MCP Servers Catalogued and Quality-Scored Daily: Finding a Production-Grade Server in a Flood of Demos
A daily automated scan catalogues 455 MCP servers and scores them on hygiene — average 16 out of 100. What the data reveals about supply, churn, and how to vet servers before your agents call them.