Stork MCP Directory
Server Details
Find an MCP server for a task. See if its endpoint answers and what its tools cost in context.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-06-18
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 5 tools
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.
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.
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.
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 toolsstork_compareARead-onlyIdempotentInspect
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_configARead-onlyIdempotentInspect
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_searchARead-onlyIdempotentInspect
Find an MCP server for a task. Say the task or product in plain words, for example: query Stripe payments, or browser automation. Results are ranked for an agent: the vendor's own server first, then servers you can connect to that answered Stork's last check. Each result is short: connect (remote URL or npm command, and whether sign-in is needed; null when Stork holds no install method), publisherDomainVerified, toolNames, and check: what Stork's own scheduled request to the endpoint last saw (result: answered | sign_in_required | stream_only | no_answer, lastCheckedAt, toolCount, toolDefinitionTokens = estimated tokens the tool definitions add to your context, toolsLastChangedAt, toolsChangedWithoutVersionChange). check is null for local stdio servers, which Stork cannot run. confidence: weak means nothing listed is a close match. A check is one initialize and one tools/list without an account: it does not prove a tool call works or that the server is safe. Listings that are duplicates of another listing, or that have not answered three checks in a row, are left out.
Inputs: query (required), limit, category, live_only, +2 more.
stork_server_detailsBRead-onlyIdempotentInspect
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_replacementARead-onlyIdempotentInspect
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
Find MCP servers for the work you need to do.
Find MCP servers for the work you need to do.
Search, vet & assemble MCP servers from your agent: verified tools, risk labels, and trust scores.
Lets your agent find the right MCP server, tool or service for a task, in one call. Ads labelled.
Related MCP Servers
AlicenseNot gradedqualityCmaintenanceEnables agents to discover and route tasks to public MCP tools, check live reliability, find working alternatives, audit server agent-readiness, and scan tool definitions for poisoning.MIT- AlicenseAqualityCmaintenanceMCP server that scores tool descriptions, estimates token costs, simulates agent tool selection, and generates reliability reports to help AI agents choose the right tools and reduce wasted tokens.59 npmMIT
- FlicenseNot gradedqualityCmaintenanceRank MCP servers/APIs for a job. Lexical ranking, 36 curated tools, no Stripe. Not measured quality.-
- AlicenseNot gradedqualityDmaintenanceTool search engine for AI agents. One API call to discover the best MCP server for any task. 900+ services indexed with 4-dimensional value ranking.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.