Galactic Radar exit check
REMOTE · GALACTICBRIDGE.COM
Token exit checks (live sell quote, round trip, warnings; x402 USDC) + free GBRIDGE market data.
Available components
Last scanned (20 hours ago)
Scores higher than 7% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Crypto and Web3
Deprecated
This server is marked deprecated in the MCP registry.
The registry records this reason: Galactic Radar is closed. Galactic Bridge's service for AI agents is com.galacticbridge/sourcing at https://galacticbridge.com/mcp.
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 the endpoint returned HTTP 410. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.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, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 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.
Checks we ran (5)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (6)
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 yet verified: we couldn't confirm whether this endpoint requires it.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
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.
- 13 Nov 26 −52
- Endpoint reachability: reachable → not serving MCP ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.17 → unverified ▼ security
- Transport: pass → fail ▼ security
- HSTS header: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 12 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Nov 26 +49
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.13 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 9 Nov 26 −48
- Endpoint reachability: reachable → not serving MCP ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.03 → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 8 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 7 Nov 26 72
First indexed and scored.
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://galacticbridge.com/api/v1/agent/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=galacticbridge.com | CN=YE1,O=Let's Encrypt,C=US | 15 Nov 2026 | 13 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 6dd7a718d7f69fca76daf5fef0eb1215470 |
| SANs: galacticbridge.com, www.galacticbridge.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of galacticbridge.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| galacticbridge.com. | No DS | 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 |
|---|---|
| HTTP status | 410 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://galacticbridge.com/api/v1/agent/mcp | HTTP error | 410 | |
| http (plaintext) | http://galacticbridge.com/api/v1/agent/mcp | HTTPS enforced | 301 | https://galacticbridge.com/api/v1/agent/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 →
exit_check Exit check ($0.02) ~127
Paid ($0.02 in USDC via x402): before buying or sizing a position in a Solana/Base/BNB token, get a live executable sell quote for your position size, round-trip loss, price impact, route availability and Galactic Radar warnings. Data, not advice.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | solana (default), base or bsc |
| position_usd | number | – | position size in USD, 1 to 1000000, default 1000 |
| token_address | string | yes | token mint (Solana) or 0x contract |
No output schema declared.
No examples provided.
gbridge_liquidity GBRIDGE liquidity (free) ~37
Free: GBRIDGE pool liquidity and trade-size limits: available liquidity, sell quotes by size and the largest executable sale right now.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
gbridge_market GBRIDGE market (free) ~63
Free: the GBRIDGE (Galactic Bridge token) market on Solana: verified Meteora DAMM v2 pool, price, liquidity, live buy and sell quotes at $1-$500, the largest sale that executes now, fees, token facts and warnings.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
gbridge_quote GBRIDGE quote (free) ~74
Free: one live Jupiter quote to buy or sell GBRIDGE for a USD amount (expires ~30 s). Execute with your own wallet; Galactic Bridge never trades for you.
| Name | Type | Req | Description |
|---|---|---|---|
| side | string | yes | buy or sell |
| usd | number | yes | trade size in USD, 0.5 to 100000 |
No output schema declared.
No examples provided.
gbridge_token_info GBRIDGE token info (free) ~52
Free: GBRIDGE token facts: mint, supply, decimals, mint/freeze authority, Jupiter verification and organic score, holders, links (Jupiter, Meteora, Solscan, DEX Screener).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
service_info Service info (free) ~25
Free: what the Galactic Radar exit check returns, its price and how payment works.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Galactic Radar exit check MCP server?
Galactic Radar exit check is a hosted endpoint at https://galacticbridge.com/api/v1/agent/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 · galacticbridge.com
claude mcp add --transport http com-galacticbridge-radar-exit-check 'https://galacticbridge.com/api/v1/agent/mcp'
What is the Galactic Radar exit check MCP server?
Galactic Radar exit check is an MCP server listed in the public MCP registry as com.galacticbridge/radar-exit-check. Token exit checks (live sell quote, round trip, warnings; x402 USDC) + free GBRIDGE market data. This page covers its hosted endpoint (https://galacticbridge.com/api/v1/agent/mcp).
Is the Galactic Radar exit check MCP server safe to use?
Galactic Radar exit check scores 23 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 Galactic Radar exit check MCP server expose?
Galactic Radar exit check exposes 6 tools: service_info, gbridge_market, gbridge_quote, gbridge_liquidity, gbridge_token_info, exit_check. Their descriptions and schemas cost roughly 378 tokens of context every time the server is loaded.
Does the Galactic Radar exit check MCP server require authentication?
Its publisher declares no required credentials for Galactic Radar exit check. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Galactic Radar exit check MCP server still maintained?
Galactic Radar exit check is marked deprecated 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 Galactic Radar exit check MCP server?
VerifyMCP ran 5 checks on Galactic Radar exit check, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 1 more. 6 items could not be completed, a gap on our side rather than a finding about Galactic Radar exit check: Authorization, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. 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.