io.github.junct-bot/jupiter-mcp
REMOTE · JUPITER.MCP.JUNCT.DEV · SCANNED AUG 18
Jupiter - 4 tools for swap quotes, liquidity pools, and trading data
Available components
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
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 Security0
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 409, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety–
Not scored yet: our latest scan of this component recorded no findings here. It fills in the next time we score it.
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 4 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the io.github.junct-bot/jupiter-mcp server?
io.github.junct-bot/jupiter-mcp is a hosted endpoint at https://jupiter.mcp.junct.dev/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 · jupiter.mcp.junct.dev
claude mcp add --transport http junct-bot-jupiter-mcp 'https://jupiter.mcp.junct.dev/mcp'
{
"mcpServers": {
"junct-bot-jupiter-mcp": {
"url": "https://jupiter.mcp.junct.dev/mcp"
}
}
} {
"servers": {
"junct-bot-jupiter-mcp": {
"type": "http",
"url": "https://jupiter.mcp.junct.dev/mcp"
}
}
} [mcp_servers.junct-bot-jupiter-mcp] url = "https://jupiter.mcp.junct.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"junct-bot-jupiter-mcp": {
"type": "remote",
"url": "https://jupiter.mcp.junct.dev/mcp",
"enabled": true
}
}
} openclaw mcp add junct-bot-jupiter-mcp --url 'https://jupiter.mcp.junct.dev/mcp' --transport streamable-http
mcp_servers:
junct-bot-jupiter-mcp:
url: "https://jupiter.mcp.junct.dev/mcp" {
"McpServers": {
"junct-bot-jupiter-mcp": {
"Transport": "http",
"Url": "https://jupiter.mcp.junct.dev/mcp"
}
}
} assistant mcp add junct-bot-jupiter-mcp -t streamable-http -u 'https://jupiter.mcp.junct.dev/mcp'
{
"mcpServers": {
"junct-bot-jupiter-mcp": {
"type": "http",
"url": "https://jupiter.mcp.junct.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 18 Aug 26 −3
The score moved with no change recorded against any check. We would rather say so than guess.
- 13 Aug 26 −3
The score moved with no change recorded against any check. We would rather say so than guess.
- 12 Aug 26 −2
The score moved with no change recorded against any check. We would rather say so than guess.
- 11 Aug 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
- 10 Aug 26 −3
The score moved with no change recorded against any check. We would rather say so than guess.
- 9 Aug 26 −3
The score moved with no change recorded against any check. We would rather say so than guess.
- 31 Jul 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
- 30 Jul 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 18 Aug 2026 · Probed https://jupiter.mcp.junct.dev/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of jupiter.mcp.junct.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| junct.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://jupiter.mcp.junct.dev/mcp | Unreachable | ||
| http (plaintext) | http://jupiter.mcp.junct.dev/mcp | Inconclusive | 409 |
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 →
No tool schema has been captured from this endpoint yet.
What is the io.github.junct-bot/jupiter-mcp server?
io.github.junct-bot/jupiter-mcp is listed in the public MCP registry as io.github.junct-bot/jupiter-mcp. Jupiter - 4 tools for swap quotes, liquidity pools, and trading data. This page covers its hosted endpoint (https://jupiter.mcp.junct.dev/mcp).
Is the io.github.junct-bot/jupiter-mcp server safe to use?
io.github.junct-bot/jupiter-mcp scores 0 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.
Does the io.github.junct-bot/jupiter-mcp server require authentication?
Its publisher declares no required credentials for io.github.junct-bot/jupiter-mcp. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the io.github.junct-bot/jupiter-mcp server still maintained?
io.github.junct-bot/jupiter-mcp has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 27 July 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.