INDIVIDUAL MCP TOOL
get_mcp_server
The full record for one listed product: what its maker says it does, how it is reached, the dated result of our connection test where there is one, what a guarded server published about signing in, what a package registry held for it, and where it placed on its launch week.
LIVE ENDPOINT
https://mcp-hunter.com/mcp
Connect to this endpoint to inspect the live schema for get_mcp_server and invoke it with your own arguments.
Indexed input schema
{}Risk classification
Inferred read-only · medium confidence · heuristic, not a guarantee.
- No write-capable action terms were found; this is not proof that invocation has no side effects.
Parent server
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.mcp-hunter]
url = "https://mcp-hunter.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"mcp-hunter": {
"type": "http",
"url": "https://mcp-hunter.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: mcp-hunter
Remote MCP URL: https://mcp-hunter.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"mcp-hunter": {
"url": "https://mcp-hunter.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"mcp-hunter": {
"type": "http",
"url": "https://mcp-hunter.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "mcp-hunter",
"transport": "streamable-http",
"url": "https://mcp-hunter.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
Related tools
search_mcp_servers— Search the MCP products listed on MCP Hunter: name, tagline, description and category.weekly_leaderboard— The ranked board for one launch week, most voted first.check_mcp_server— Connect to any Streamable HTTP MCP endpoint and record what it returned: whether it answered, how many tools it exposes, their names, the protocol revision it replied with, and one round trip in milliseconds.get_check_result— The finished result of a check started by check_mcp_server: what the endpoint returned, when, and what it exposed.mcp_ecosystem_stats— Aggregate results from calling MCP servers in bulk: what share of the official registry answered, refused, or went nowhere on a dated sweep, plus a smaller hand-picked corpus checked in depth.