Skip to main content
Glama

Stork MCP Directory

Server Details

Find an MCP server for a task. See if its endpoint answers and what its tools cost in context.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-06-18
URL
ChatGPT
–
Claude
–

TDQS

A3.8/5.0

Scored across 5 tools

Disambiguation4/5

Search (discover by task), details (full metadata for one server), compare (2-5 servers), and install config (paste-ready client config) each target a distinct action on a distinct granularity. The only mild overlaps are details vs. install config (both single-server lookups) and smithery_replacement vs. search (both return listings), but the descriptions make the boundary clear.

Naming Consistency4/5

All five tools share the `stork_` prefix and snake_case, giving a predictable, readable pattern. Two deviate from verb_noun (stork_server_details and stork_smithery_replacement are noun phrases), a minor inconsistency in an otherwise uniform set.

Tool Count5/5

Five tools is well within the healthy range and each maps to a real directory workflow: discover, inspect, compare, install, and migrate. The niche smithery_replacement tool is justified by a specific, documented endpoint shutdown rather than being filler.

Completeness4/5

The discovery-to-install lifecycle is covered: search → details → compare → install config, plus a migration path. Minor gaps exist — no browse/list-by-category operation, and no way to retrieve a server's full tool schemas (only names and token estimates) — but agents can work around these via search and details.

Available Tools

5 tools
stork_compareA
Read-onlyIdempotent
Inspect

Compare 2 to 5 MCP servers side by side by slug: how each connects, licence, tool list, and what Stork's last check of each endpoint saw.

Inputs: slugs (required).

stork_get_install_configA
Read-onlyIdempotent
Inspect

Ready-to-paste client config for one MCP server. Check installKnown first: when it is false, config is null because Stork holds no verified install method, and instructions links the publisher's own setup guide. Do not invent a command in that case. installMethod is 'remote' (connect by URL) or 'npm' (local stdio). authSummary says when the user must sign in.

Inputs: slug (required), client.

stork_server_detailsB
Read-onlyIdempotent
Inspect

Get full details about a specific MCP server, including check (what Stork's last request to its endpoint saw, with the estimated token size of its tool definitions) and toolChanges (each time a check found different tool definitions than the check before, and whether the server's version changed with them).

Inputs: slug (required).

stork_smithery_replacementA
Read-onlyIdempotent
Inspect

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.

Inputs: reference (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources