dsh.sh valid
MCP Finder
Find an MCP server for any task: searches the official registry, Smithery and npm; remote-first. Remote MCP server over Streamable HTTP at `https://findanmcp.com/mcp`. Free, no API key. Tools: `find_mcp`, `mcp_details`. The tool list is fixed per version.
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-27T13:26:47.016Z. Cached copy · Source on dsh.sh
# MCP Finder
> Find an MCP server for any task: searches the official registry, Smithery and npm; remote-first. Remote MCP server over Streamable HTTP at `https://findanmcp.com/mcp`. Free, no API key. Tools: `find_mcp`, `mcp_details`. The tool list is fixed per version.
MCP Finder answers "is there an MCP server for X?" in one call. It federates the official MCP Registry (registry.modelcontextprotocol.io), the Smithery registry (with live use counts) and npm, dedupes the hits, ranks remote Streamable HTTP servers first, and returns the install snippet for the caller's own client. A second tool returns one server's tool list and connection details so an agent can decide before installing. Free, keyless, no account.
Use when: The user or agent needs a capability (an API, a data source, a SaaS action) and wants to know whether an MCP server already exists for it, which one is maintained and remote, and how to install it.
Not for: Calling the found server's tools (install it instead), or building a new MCP server.
Quick install (Claude Code): `claude mcp add --transport http mcpfinder https://findanmcp.com/mcp -s user`
Live server: https://findanmcp.com
## Docs
- [Full reference](https://findanmcp.com/llms-full.txt): every tool with its JSON input schema and an example
- [Install for any client](https://findanmcp.com/install): Claude Code, Cursor, VS Code, Claude Desktop, ChatGPT, Codex, Gemini CLI, Windsurf, Cline, Continue, Zed
- [OpenAPI twin](https://findanmcp.com/openapi.json): the same tools as plain HTTP POST endpoints
- [Registry server.json](https://findanmcp.com/.well-known/mcp/server.json): machine-readable server record
- [Server card](https://findanmcp.com/.well-known/mcp/server-card.json): transport + tool card (also at https://findanmcp.com/.well-known/mcp.json, SEP-1960)
- [ARD manifest](https://findanmcp.com/.well-known/ard.json): Agentic Resource Discovery entry (also at https://findanmcp.com/.well-known/ai-catalog.json)
## Upstreams
- [MCP Registry](https://registry.modelcontextprotocol.io/docs): keyless
- [Smithery registry](https://smithery.ai/docs): keyless
- [npm search](https://github.com/npm/registry/blob/main/docs/REGISTRY-API.md): keyless
## Optional
- [Health](https://findanmcp.com/healthz): liveness JSON
- [Owner](https://github.com/ux-xd/mcpfinder-mcp): ux-xd
Related sites
Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| mcp.so | MCP.so | documentation AI and machine learning AI agents and MCP +1 | — | 50 | ✓ | ✓ | |
| mcpmarket.com | MCP Market - MCP server Directory | documentation AI and machine learning AI agents and MCP +1 | US | 54 | ✓ | ||
| mcpservers.org | Awesome MCP Servers | documentation AI and machine learning Developer tools +2 | — | 50 | ✓ | ||
| unyly.org | Unyly | interface Developer tools AI agents and MCP | — | 52 | ✓ | ✓ | |
| mcp.directory | MCP.Directory | documentation AI agents and MCP | — | 50 | ✓ | ||
| mentorcruise.com | MentorCruise | interface Recruiting and careers AI agents and MCP | — | 61 | ✓ | ✓ | |
| apitracker.io | API Tracker | interface Developer tools APIs and SDKs +1 | US | 47 | ✓ | ||
| mcpjam.com | MCPJam | interface Developer tools AI agents and MCP +1 | US | 49 | ✓ |
Machine-readable: GET /v1/resolve?q=dsh.sh · GET /v1/domain/dsh.sh · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage dsh.sh, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for dsh.sh:
1. POST https://agentwebmap.com/v1/sites/dsh.sh/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://dsh.sh/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/dsh.sh/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/dsh.sh).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.