Urgent.News

What's breaking now, across thousands of outlets.

Tech

mcp-drift-monitor: continuous detection of unauthorized changes in MCP servers

mcp-drift-monitor detecta cambios no autorizados en servidores MCP (Model Context Protocol). Implementa el control primario faltante descrito en arXiv:2608.00997 : un barrido completo periódico del catálogo que re-descarga todos los servidores y recomputa hashes. Problema arXiv:2608.00997 ( MCP Registry Drift: A 88.6-Day Measurement of 19,099 Servers ) reporta un punto ciego crítico: los enfoques…

Translated from Spanish Read in Spanish

A new tool called mcp-drift-monitor has been developed to detect unauthorized changes in MCP servers. The tool addresses a critical blind spot identified in a research paper on arXiv:2608.00997, which found that traditional change detection approaches fail to identify silent changes and new additions to the MCP registry. The monitor implements a periodic full catalog sweep to re-download all servers and recompute hashes.

It was calibrated and verified using a panel of 19,099 servers observed over 88.6 days, and is available as a Docker image or library on GitHub.

Written by urgent.news from Dev.to's report — not a translation of it. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Web APIs and Batch Jobs Communicate Failure Differently

Long Story Short Web APIs can communicate failure through HTTP status codes, but batch jobs need to terminate in a way that allows the execution environment to recognize that the process has failed.

  • Web APIs communicate failure via HTTP status codes like HTTP 500.
  • Batch jobs need a different failure handling approach than HTTP codes.
  • Lambda functions don't treat return values like false or { status: 500 } as failures.

Opinion: Your Tests Can't See What a Migration Destroys — Dry-Run It on a Clone

Opinion: Your Tests Can't See What a Migration Destroys — Dry-Run It on a Clone A green test suite is the wrong tool for judging an AI-generated migration, because tests run against the post-migration…

  • Traditional testing methods insufficient for verifying database migration safety
  • Dry-run workflow using clone of production schema with representative data sample
  • Monitor table count, constraint count, and not-null attribute count during migrations

How to Make an HTML5 Game (Browser Loop, 2026)

Originally published on the Sorceress blog . TL;DR: an HTML5 game is four things — an index.html host page, a JS module that owns the loop, a folder of sprites and audio, and a static zip anyone can…

More from Sunday 23 August →