Developer Tools
mcpjunction.ai
Provides a searchable directory of MCP servers with metadata and dataset access.
ENDPOINT 1
https://mcpjunction.ai/mcp
MCP server metadata
- Name
- mcpjunction
- Version
- 1.0.0
Queryable index of the mcpjunction.ai MCP server directory. Use search_servers to find servers, get_server for one entry, list_categories and list_topics to browse. Categories are a curated single-assignment taxonomy; topics are owner-assigned GitHub tags, many per server. Data refreshes nightly. Attribution: via mcpjunction.ai.
Known tools 5
get_serverGet the full directory entry for one MCP server by id ('owner--repo', e.
Inferred read-onlylist_categoriesList all directory categories with slugs, names, and active-server counts.
Inferred read-onlylist_topicsList the curated GitHub topics that have a directory page, with active-server counts.
Inferred read-onlyget_dataset_infoDataset metadata: entry counts, generation timestamp, source, and licensing terms for bulk or training use.
Inferred read-onlyCONNECT 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.mcpjunction]
url = "https://mcpjunction.ai/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"mcpjunction": {
"type": "http",
"url": "https://mcpjunction.ai/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: mcpjunction
Remote MCP URL: https://mcpjunction.ai/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": {
"mcpjunction": {
"url": "https://mcpjunction.ai/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"mcpjunction": {
"type": "http",
"url": "https://mcpjunction.ai/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "mcpjunction",
"transport": "streamable-http",
"url": "https://mcpjunction.ai/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.