MCP Junction
REMOTE · MCPJUNCTION.AI
Search a nightly-refreshed directory of MCP servers by keyword, category or topic.
Available components
Last scanned (13 hours ago)
Scores higher than 79% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Search and Retrieval
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 517 tokens (~103/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- 9 Nov 26 0
- Stability: 0.97 → pass security
- 8 Nov 26 0
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Nov 26 0
- Stability: 0.97 → pass security
- 4 Nov 26 0
- Stability: pass → 0.97 functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://mcpjunction.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcpjunction.ai | CN=WE1,O=Google Trust Services,C=US | 11 Oct 2026 | 9 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 50c5d729f3f5eeed1325772310926215 |
| SANs: mcpjunction.ai, www.mcpjunction.ai, *.www.mcpjunction.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcpjunction.ai. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | DS published | 1814 | 8 | Verified |
| mcpjunction.ai. | DS published | 2371 | 13 | Verified |
| mcpjunction.ai. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains |
| content-security-policy | default-src 'none'; frame-ancestors 'none'; base-uri 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcpjunction.ai/mcp | Verified | 200 | |
| http (plaintext) | http://mcpjunction.ai/mcp | HTTPS enforced | 301 | https://mcpjunction.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_dataset_info ~29
Dataset metadata: entry counts, generation timestamp, source, and licensing terms for bulk or training use.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_server ~101
Get the full directory entry for one MCP server by id ('owner--repo', e.g. 'microsoft--playwright-mcp'). Includes install hint, license, stars, category, and editorial fields. Any install_hint is a best-effort guess from the repository language, not a verified command: relay the install_hint_caveat with it rather than presenting it as ready to run.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Server id in owner--repo form |
No output schema declared.
No examples provided.
list_categories ~23
List all directory categories with slugs, names, and active-server counts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_topics ~63
List the curated GitHub topics that have a directory page, with active-server counts. Topics are assigned by repository owners and imported verbatim, so the full dataset carries thousands of them; this returns only the curated subset. search_servers accepts any topic string, curated or not.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_servers ~229
Search the MCP server directory by keyword and/or filters. Keyword matches name, description, and GitHub topics. Returns active servers sorted by relevance then stars. Supply at least one of query, category, or topic — with no query, filters alone enumerate a whole category or topic by stars. Data refreshes nightly from the public GitHub API. Any install_hint is a best-effort guess from the repository language, not a verified command: relay the install_hint_caveat with it rather than presenting it as ready to run.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional category slug filter, e.g. 'databases' (see list_categories) |
| language | string | – | Optional implementation language filter, e.g. 'Python' |
| limit | integer | – | Max results (default 10) |
| query | string | – | Keywords, e.g. 'postgres', 'browser automation'. Optional if category or topic is given. |
| topic | string | – | Optional GitHub topic filter, exact match, e.g. 'kubernetes'. Any topic string works, not only the curated ones from list_topics. |
No output schema declared.
No examples provided.
How do I install the MCP Junction server?
MCP Junction is a hosted endpoint at https://mcpjunction.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcpjunction.ai
claude mcp add --transport http ai-mcpjunction-directory 'https://mcpjunction.ai/mcp'
What is the MCP Junction server?
MCP Junction is listed in the public MCP registry as ai.mcpjunction/directory. Search a nightly-refreshed directory of MCP servers by keyword, category or topic. This page covers its hosted endpoint (https://mcpjunction.ai/mcp).
Is the MCP Junction server safe to use?
MCP Junction scores 81 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the MCP Junction server expose?
MCP Junction exposes 5 tools: search_servers, get_server, list_categories, list_topics, get_dataset_info. Their descriptions and schemas cost roughly 445 tokens of context every time the server is loaded.
Does the MCP Junction server require authentication?
No. We connected to MCP Junction without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the MCP Junction server still maintained?
MCP Junction is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the MCP Junction server?
VerifyMCP ran 12 checks on MCP Junction, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about MCP Junction: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.