Three places. Choose an agent. Read what changed. Check the evidence behind a skill or MCP server. The rest of the site supports those three jobs.
Registry stats loading…
We separate release-note language from the behavior, policy, price, limit, or compatibility change that matters in practice.
We look for pricing changes, migration risk, reliability regressions, security exposure, and hidden operational limits before recommending an update.
Each report ends with a practical verdict: update, wait, test first, pin a version, change configuration, or ignore the announcement.
MCP TypeScript SDK v2.3.1 brings expectedResource to the deprecated server-legacy package. It compares verifier-returned AuthInfo.resource, so validated JWTs and introspected opaque tokens can both work when audience and expiry metadata are populated correctly. The same-day v1.32.1 release is documentation and a version bump, not another auth fix.
We have been writing about agents. This is the map, so you do not have to guess which page does which job.
A short list of agents people actually run. Each dossier says when to pick it, when to skip it, and what it writes. Not a tools dump.
Releases, prices, limits, outages, and compatibility. Each report should say what changed, what could break, and what to do next.
Skills and MCP records, with scan states and gaps. This is not a product catalog and not a safety certificate.
We do not rewrite launch posts. We connect primary sources, reproducible tests, scanner evidence, Registry records, and technical guides to the decision in front of you.
Pricing, policy, security, compatibility, and incident claims start with official documentation, repositories, advisories, or status pages. Community reports are labeled as experience, not proof.
Field reports name the version, environment, method, inputs, and limitations. If we only compared documentation, we say so.
The skills and MCP Registry remains free. Its source links, scan states, provenance, and explicit evidence gaps help test whether an ecosystem claim survives contact with real artifacts.
Durable technical guides and inspectable workflow manifests turn a news event into implementation work you can adapt and validate in your own environment.
Anthropic's coding agent CLI. Reads project instructions, calls tools, and stays human-gated per session.
OpenAI's coding agent CLI. Tool-using and session-gated. Not the hosted Agents API.
Self-hosted agent gateway with channels, cron, and write-tools. Failure has an operator.
A landing page that says "AI agent" is not a listing. The directory covers coding, ops, voice, research, and go-to-market runtimes. Autonomy is a tested facet, not a slogan.
Weekday impact reports, a weekly Before You Update brief, and tested comparisons when the evidence supports them. No quota filler.
The change log is the news. Agent dossiers are the catalog.
Open the change log