Think inside your AI world.

A watched package, against a release line that moved

A release watch is only as good as the package you point it at. Watch the wrong one and it reports six weeks of calm while the real line ships four betas next door — and the calm is indistinguishable from nothing happening, which is the most expensive kind of wrong: a hardened silence you trust.

Read the npm registry through Unl and the release feed arrives measured against the dependency you actually run — so a watch that has gone quiet is read against the line it was meant to track, and the frame tells you whether the quiet means ‘nothing shipped’ or ‘you are watching the wrong package’. The verdict, not the feed.

What the npm registry carries

The npm registry is a genuine public good, and around a single protocol there is already more than one moving line:

  • @modelcontextprotocol/sdk, the long-standing package, at dist-tag latest 1.29.0
  • @modelcontextprotocol/server, the 2.0 line, publishing beta after beta on its own core package
  • A client package on the same 2.0 line, split out from what used to be one dependency
  • No signal in a plain version watch that the release candidate ships under a package you may not be watching

The line the feed can't hold

Say you settled a sensible criterion months ago: watch the MCP SDK I depend on, and tell me when the 2026-07-28 release candidate lands on it. That is a reasonable line to draw — and it points at exactly the package that will never carry the new line, because the 2.0 revision ships under a different name.

The reason the line has to be yours is that only you know which package your server imports, and a topic watch cannot. A feed can report that a version was published; it cannot know that the package you are watching has stopped being where the action is, or that its silence is a property of your watch rather than of the world.

The frame judges the data it is given; it does not verify the source’s accuracy.

The one that crosses

So the measured read crosses where the plain watch stays flat: the package you are watching sits at 1.29.0 with no prerelease tag and has not moved in months, while the 2026-07-28 line ships under a separate package now several betas deep — so the quiet on your watch is not ‘nothing is happening’, it is ‘you are pointed at the wrong line’. The old package is not dead — it carries live conformance tooling and a documented support window — it is simply not where the revision ships. Same registry; a verdict about your watch instead of a feed you trust by default.

You didn't ask — it was already there

This one is honest because we made the mistake first. Our own release bar was pointed at the long-standing package and reported six weeks of calm as a finding — and the calm was a lie the instrument was telling, not a fact about the world. The fix was not more machinery: the criterion was rewritten to watch the new line, and the registry was re-read against it in a single call. A measured frame is only ever as good as its criterion; the difference from a feed is that the criterion is yours, and so is the correction — you rewrite the line, and the world is read again.

The answer comes back measured against what you already decided, and why.

The lane is live and open to this tool today: one box, paste anything. If it speaks MCP, Unl can reach it. Readings arrive unprompted, the data beside the criterion; Unl is a courier, not a warehouse, and keeps only your keys and the frame.

Questions people ask

Is @modelcontextprotocol/sdk deprecated or dead?

No, and a page that said so would be wrong. It sits at a current release with live conformance tooling, and a version line like it typically carries fixes for a long support window after a major successor appears. The narrow, true point is different: the 2026-07-28 revision ships under a separate package, so a version watch pointed at the old one reports nothing through the date — and that quiet is not evidence either way. The measured read is what tells the two silences apart.

How would a measured frame have caught this when a version alert did not?

A version alert fires on the package you named, by the source’s own rule. The measured read fires on your criterion — the dependency your server actually imports, read against the release line that carries the revision — so when your watch goes quiet, the frame reads the quiet against your line and returns a verdict on what it means, rather than passing the silence through as if it were an all-clear.

Does Unl publish, install or change anything on npm?

Unl reads the public npm registry and returns a verdict measured against your criterion; the registry read is a public GET, your criterion lives in Unl, and the read joins them and changes neither. Anything that would alter your project happens only on your explicit gesture, never as a side effect of a read.

What this is

Think inside your AI world — you stay in command

Unlimitless (Unl to friends) holds what you've settled, reads what your tools are showing, and catches what's changed out in the world — and hands your AI whatever bears on the work, the moment it's needed, without you asking. The right thing, in front of the model, unprompted, with you in command of the call. So you keep moving toward what you set out to build, on top of everything you've already decided.

It plugs into Claude, Claude Code, ChatGPT and Cursor as an MCP connector. Quick to connect, in a couple of steps.

Unlimitless is open now to invited Alpha. Apply for the Beta waitlist to come in ahead of the full launch:

Alpha is invite-only · free at launch.