Skip to main content
Glama

Stork MCP Directory

stork_smithery_replacement

Read-onlyIdempotent

Find where an MCP server lives now that Smithery's hosted URLs are gone. Smithery's run.tools and server.smithery.ai URLs, its API, CLI and SDKs stopped on 2026-10-31. Pass the old URL (e.g. https://server.smithery.ai/@org/name/mcp or https://name.run.tools) or just the server name; returns listings that hold the server's own endpoint or npm package, with what Stork's last check of each endpoint saw. Matches are by name: confirm the publisher before connecting.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "reference": "<reference>"
    },
    "name": "stork_smithery_replacement"
  }
}

Input Schema

NameRequiredDescriptionDefault
referenceYesOld Smithery URL, @org/name, or a server name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly, idempotent, and open-world, so safety is covered; the description adds meaningful context beyond that, notably that matches are made by name and therefore may be unreliable, plus that results carry the timestamped state of Stork's last endpoint check. That name-matching warning is exactly the kind of behavioral trait an agent needs before trusting a result. It stops short of saying what happens on zero matches or how many listings come back.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, purpose front-loaded, with the deprecation date and the input formats following in logical order. The clause enumerating 'its API, CLI and SDKs' is slightly tangential but supports why legacy references exist. Little waste overall.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description compensates by describing the return shape — listings containing the server's own endpoint or npm package plus last-check observations. For a one-parameter lookup tool this is nearly sufficient. It omits behavior on empty results and result ordering, which would matter when the name match is ambiguous.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single parameter is already documented as accepting an old URL, @org/name, or a bare server name. The description still earns credit by supplying concrete accepted URL shapes (https://server.smithery.ai/@org/name/mcp and https://name.run.tools), which reduces format guesswork. This is a modest but genuine addition over the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb and resource: find where an MCP server now lives after Smithery's hosted URLs shut down, returning listings with the server's own endpoint or npm package. That is far more specific than the opaque name 'replacement'. It does not explicitly contrast itself with the sibling stork_search, so an agent must infer the distinction between a legacy-URL migration lookup and a general search.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear triggering condition (old Smithery URLs, API, CLI, SDKs stopped on 2026-10-31) and tells the agent what to pass — an old URL or just a server name. It also adds an operational caveat, 'confirm the publisher before connecting,' which is real usage guidance. The gap is that no alternative tool is named for the case where the agent has no legacy reference at all.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources