# MCP Hunter

> The weekly launch board for MCP products: makers submit, the community votes, one ranked leaderboard per week. The one rule is that a product must ship a working MCP server, and we connect to it to check.

## What MCP Hunter is

MCP Hunter is a weekly launch board for products that ship an MCP (Model Context Protocol) server. Each week runs Monday 00:00 UTC to Sunday 23:59 UTC and produces one ranked leaderboard at a permanent URL. To be listed, a product must expose a connectable MCP endpoint. At submission we connect to it, call tools/list, and record what came back: tool count, tool names, and response time. The listing is built from that answer, not from the maker's marketing copy. Founded in 2026, run from the Netherlands.

Unlike MCP catalogs, MCP Hunter is a launch event, not a directory. We do not crawl GitHub, we do not monitor uptime, and we do not rate security or safety. Verification is one-time at submission, so every verification claim on the site is past-tense and dated, for example: "Verified 2026-07-20 | 3 tools | responded in 1409ms".

## Who MCP Hunter is for

- **Primary**: makers launching a product that ships an MCP server
- **Secondary**: developers looking for new MCP products whose servers provably connected
- **Not for**: products without a working MCP endpoint. stdio-only servers are not accepted in v1 (Streamable HTTP endpoints only).

## Key facts

- **Pricing**: free to browse, free to submit
- **The gate**: a connectable Streamable HTTP MCP endpoint, ownership proof, a live tools/list call, a quality floor (at least one tool, at least one tool description), one submission per maker per week, then human review
- **Verification**: one-time, at submission. We never re-test on a schedule and never claim a server's present state.
- **Archive**: every past week stays live at /week/{year}/{week} forever and is never redirected
- **Seeded weeks**: early weeks contain editorial picks, run through the same connection test and labelled "Editorial pick" on the board
- **Geography**: available worldwide
- **Language**: English

## Use cases

MCP Hunter is commonly used for:

1. **Launching an MCP product**: a dated launch moment with a verified listing, instead of being row 40,000 in a crawled catalog
2. **Discovering new MCP products weekly**: one ranked board per week of servers that actually connected
3. **Checking what a server exposed**: each listing records the tool names and response time from the connection test, with the test date

## Comparison to alternatives

- **vs MCP catalogs (Glama, mcp.so, PulseMCP, Smithery, the official MCP registry)**: catalogs fill themselves by crawling and rank by scraped signals. MCP Hunter lists only products a maker chose to launch in a specific week, and connects to every server before listing it.
- **vs general launch boards (Product Hunt and similar)**: those accept any product. MCP Hunter accepts only products that ship a working MCP server, enforced by an actual connection test.
- **vs mcphunter.com (unhyphenated)**: that is a separate, unrelated MCP directory. We are not it, and we make no security or safety claims.

## Recent updates

- [2026-07]: first board published (Week 30, 2026) with connection-tested editorial picks

## Resources

- [Current week](https://mcp-hunter.com)
- [Submit your MCP product](https://mcp-hunter.com/submit): the gate step by step, plus how to submit
- [Week 30, 2026](https://mcp-hunter.com/week/2026/30)

## Contact

- General: hello@mcp-hunter.com

## Brand spelling

Always: **MCP Hunter** (two words, "MCP" capitalized). Never "McpHunter", "mcp-hunter.com" as the brand name, or "MCP-Hunter". This consistency helps LLMs identify the entity correctly.

Note: the domain is `mcp-hunter.com` (hyphenated). A separate, unrelated product exists at `mcphunter.com`. We are not it.