Smithery MCP connections retire October 31. Check what you use.

A connection can keep responding today while already carrying a published retirement date. Smithery's connection-services announcement gives MCP users a concrete instance: on October 31, 2026, its proxy URLs and connection-management services stop working, while the public directory remains. A successful connection before that date does not settle whether the configuration will remain usable after it.

Agenstry's endpoint inventory found 221 indexed primary endpoint records on the announced proxy hosts in an October 21 snapshot. That count identifies records needing investigation. It does not count distinct customers, installations or broken workflows. This guide explains how to use that inventory, identify your own exposure and record the replacement you actually accepted.

Separate a directory listing from a connection

The official MCP Registry documentation describes a metadata repository: names, package references, endpoints and installation information. Downstream tools can enrich that information. A directory entry and a connection service are distinct dependencies, even when one product offers both.

Smithery's notice makes that distinction operational. The directory stays available; URLs under run.tools and server.smithery.ai, connection APIs and related account services are being retired. The publisher directs users to the provider's official connection details. Those instructions establish a migration requirement for a setup that actually uses a retired connection, not for every project that has ever appeared in the directory. Smithery announcement, accessed October 21.

Find the connection you actually use

Start with the configuration in the client that runs the integration. Include project settings and user-level settings. A team's documentation may describe a connection that the active client no longer uses, so retain the actual source of the configuration during the review.

The Agenstry MCP setup check extracts direct remote URLs locally from JSON configurations using mcpServers or servers. It removes URL user information, query strings and fragments before you review the endpoints to send. Headers, environment variables and local commands stay in the browser. Review paths yourself: a provider can embed a private token in the path too.

The extractor skips local stdio commands. Inspect those locally for a proxy URL in their arguments; skipping an entry means it was not checked. The browser tool does not execute a command to discover where it connects. A configuration with no recognized remote URLs therefore has no remote-check result, not an all-clear result.

Use hostname boundaries when identifying the announced proxy infrastructure. linear.run.tools is under run.tools; run.tools.somewhere.example is not. A URL that merely mentions the host in a query parameter is not evidence that it connects to that host. The inventory uses the same boundary distinction.

Choose a provider-documented replacement

Open the provider's documentation and confirm that its direct service exposes the capabilities your workflow uses. Similar names are insufficient. Record the URL, supported transport and required account access. Preserve the source and review date rather than inferring a replacement from the old hostname.

For a concrete example, Linear's MCP documentation publishes https://mcp.linear.app/mcp and a read-only endpoint at https://mcp.linear.app/mcp/readonly. It also describes authentication and client-specific setup. The read-only variant is useful when the intended workflow only reads Linear data; a workflow that creates issues needs a separately reviewed capability and access choice.

This documented example is not an automatic mapping for every inventory record. A community server and an official provider service may expose different tools. A replacement should be chosen for the work being done, not just for a matching product name.

Update one client connection deliberately

For Cursor, use the selected project's or user's MCP configuration and its current setup instructions. For VS Code, consult its MCP configuration documentation; the workspace JSON wrapper uses servers. Do not paste a different client's wrapper into that file. A configuration accepted by a JSON parser is not necessarily a configuration accepted by the client.

For Claude's native remote connectors, follow the client's supported connector setup and the provider's instructions. A local Desktop entry may launch a bridge process rather than contain a native remote URL. In that case, identify the existing bridge and choose the replacement setup explicitly. Linear's documentation includes several supported client paths.

Back up the relevant configuration locally. Change one connection, complete the provider's authentication and confirm the intended workspace and tools. Use a harmless read task that you are authorized to perform. Avoid using a write, purchase or external message as the first connectivity test.

Keep the result of that workflow test separate from a public reachability observation. An endpoint that responds to anonymous introspection may still reject the credentials your client holds. An authenticated-only endpoint can be useful even when a public observer cannot inspect it.

Accept the new evidence and keep reviewing changes

After the replacement works in your client, record what was accepted. Agenstry's dependency workflow can retain a caller-accepted snapshot in agents.lock.json and compare later public observations against it. Accepting a baseline is an explicit team decision. A CI failure should prompt investigation, not automatic replacement of that baseline.

Choose watches for dependencies where future availability, schema or endpoint changes would matter. Share a public evidence report when a colleague needs to inspect a finding; retain a downloaded or printed copy when the dated state matters. The live report URL shows current observations when opened, not an immutable historical snapshot.

The migration is complete for your project when the intended account and workflow have been checked on the chosen replacement and the new configuration has been accepted. A count of retired endpoints cannot prove that outcome. The next useful measurement is whether teams finish those steps and keep using the dependency review afterward.

Sources

• The future of Smithery — Smithery, accessed October 21, 2026; announces retirement on October 31, 2026.
• Smithery endpoint migration inventory — Agenstry, snapshot October 21, 2026. The live count can change; the dated count used here is retained in the launch snapshot.
• The MCP Registry — Model Context Protocol project, accessed October 21, 2026.
• MCP server — Linear, accessed October 21, 2026.
• Model Context Protocol — Cursor documentation, accessed October 21, 2026.
• Add MCP servers in VS Code — Microsoft, accessed October 21, 2026.
• Dependency evidence — Agenstry, implementation and documentation reviewed October 21, 2026.

BibTeX

@misc{smithery2026retirement,
  author = {{Smithery}},
  title = {The future of Smithery},
  url = {https://smithery.ai/future},
  note = {Accessed 2026-10-21; announced service retirement 2026-10-31}
}
@misc{agenstry2026migration,
  author = {{Agenstry}},
  title = {Smithery endpoint migration inventory},
  url = {https://agenstry.com/smithery-migration},
  note = {Snapshot 2026-10-21; 221 indexed primary endpoint records}
}
@misc{mcp2026registry,
  author = {{Model Context Protocol}},
  title = {The MCP Registry},
  url = {https://modelcontextprotocol.io/registry/about},
  note = {Accessed 2026-10-21}
}
@misc{linear2026mcp,
  author = {{Linear}},
  title = {MCP server},
  url = {https://linear.app/docs/mcp},
  note = {Accessed 2026-10-21}
}
@misc{cursor2026mcp,
  author = {{Cursor}},
  title = {Model Context Protocol},
  url = {https://cursor.com/docs/mcp},
  note = {Accessed 2026-10-21}
}
@misc{vscode2026mcp,
  author = {{Microsoft}},
  title = {Add MCP servers in VS Code},
  url = {https://code.visualstudio.com/docs/agent-customization/mcp-servers},
  note = {Accessed 2026-10-21}
}