3 declared MCP servers found in nuxt.com

The Nuxt framework's own website, and the report where the checks mostly say this is fine — which is the point. Its three declared MCP servers are all remote, so until charter could speak the HTTP transport there was nothing to say about any of them; they now enumerate to 24 real tools. Ebb finds ten current models and nothing to migrate.

MCP servers declared, all remote

server and tool capability records

enumerated, nothing elevated

models confirmed still supported

Repository: nuxt/nuxt.com
Commit: 63f19854173a1623ccc843b228405024195ba35c
Subject: fix(nuxi): use route-bound analytics scope (#2425)
Scanned: 2026-09-16 · 243 source files

This is an independent analysis of a public repository. Foretop is not affiliated with or endorsed by the repository owner.

Keep scan history in Foretop Hub — free for 3 repositories

What Ebb, telltale, charter and lading found

Ebb, telltale, charter and lading are the checks you can install and re-run yourself today. Each one's scope, its result, and — below — every source it matched.

Each installable check's scope and result for this repository
Check	Scope	Results	Outcome
ebb	whole repo	31	Model IDs matched against the bundled retirement registry.
telltale	repo root	—	No OpenAPI spec at the repo root (tried openapi.yaml/.yml/.json, swagger.yaml/.yml/.json). A content site declares no API contract to compare telemetry against.
charter	.mcp.json	29	Three declared MCP servers, all remote, all contacted over the network and asked for their real tools/list — nothing was launched locally. Unlike every other report here, this one is a live reading rather than a pure function of the pinned commit: these endpoints are third-party services and can change their tool list at any time, so the counts describe what they answered on the scan date.
lading	repo root	—	Only a pnpm-lock.yaml here. Lading reads Python lockfiles — uv, poetry and requirements files — so a Node-only dependency tree is out of scope, which is a documented gap in the tool rather than a clean bill of health.

Every result, grouped and filterable

Deduplicated into real issue groups, never one row per raw occurrence. Filter by check, deadline, provider or context, or search — every filter is reflected in the URL, so a filtered view is a link you can share.

Check Context Deadline Provider Search

4 issue groups · 60 scanned

Review gpt-5.4 not in the retirement registry 1 occurrence(s)

Every occurrence in this group, with its exact evidence link
Context	Evidence	Excerpt
unknown	layers/nuxi/agent/lib/gateway-attribution.ts:16:61	gpt-5.4

Review gpt-4.1-nano retires 2026-10-23 · usage context unclear 1 occurrence(s)

Every occurrence in this group, with its exact evidence link
Context	Evidence	Excerpt
unknown	layers/nuxi/server/utils/generate-chat-title.ts:7:44	gpt-4.1-nano

Review claude-fable-5.1 not in the retirement registry 2 occurrence(s)

Every occurrence in this group, with its exact evidence link
Context	Evidence	Excerpt
configuration	public/agent-results.json:16:17	claude-fable-5.1
configuration	public/agent-results.json:684:5	claude-fable-5.1

Review gpt-5.5-pro not in the retirement registry 2 occurrence(s)

Every occurrence in this group, with its exact evidence link
Context	Evidence	Excerpt
configuration	public/agent-results.json:166:17	gpt-5.5-pro
configuration	public/agent-results.json:7224:5	gpt-5.5-pro

And the 5 we could not answer

5 of ebb's 31 results are ?unknown — model strings that are real references but are not in the retirement registry, so no deadline can be claimed for them. They are reported as unknown, not quietly dropped and not counted as clear. They are visible in the Review tab above, not hidden below the fold.

If a tool showed you only the 26 it could resolve and said nothing about the other 5 strings it walked past, you would have no way to know the difference between "checked and fine" and "never looked".

The same five checks, elsewhere

What a suite is for: the answers come back in a different shape for every codebase, and which checks have nothing to say is itself information.

LangChain — 1 model migration found in LangChain · Langfuse — 117 API operations with no declared telemetry config found in Langfuse · AutoGPT — 286 dependencies found in AutoGPT · the CZI data portal — 4 MCP servers with elevated access found in the CZI data portal

Preview: what Undertow observed

Undertow is still in development. It is not publicly installable, and nothing below can be reproduced by a reader today — it is shown because a check that cannot see something has to say so, including here. Ebb, telltale, charter and lading, above, are all available now.

In-development checks and what each observed
Check	Scope	Observations	Outcome
undertow	—	—	Scans vendor subprocessor pages by URL, not repositories. Nothing in a source tree is in its scope by design.

Run it on yours

Same command, same registry, no account and no upload — detection is local and only results ever leave your machine.

Results above are a snapshot at commit 63f1985, taken 2026-09-16. Both projects move quickly; re-running it today may return something different, which is rather the point.