Golden Kog token risk analyst by Kognai
REMOTE · WWW.KOGNAI.AI
Risk and structure facts on one Solana or Base token, never a trading signal. Paid per call by x402.
Available components
Last scanned (5 hours ago)
Scores higher than 56% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Crypto and Web3
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 Security63
- 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 1 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 628 tokens (~125/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 78% of tool parameters carry a description.Partial
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 14 Oct 26 65
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 17 Oct 2026 · Probed https://www.kognai.ai/v1/golden-kog/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.kognai.ai | CN=YR2,O=Let's Encrypt,C=US | 30 Aug 2026 | 28 Nov 2026 | RSA 2048 | SHA256-RSA | 52fdb1ced98234fcef1dddcd21bc9315776 |
| SANs: www.kognai.ai | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.kognai.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| kognai.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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=63072000 |
| 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://www.kognai.ai/v1/golden-kog/mcp | Verified | 200 | |
| http (plaintext) | http://www.kognai.ai/v1/golden-kog/mcp | HTTPS enforced | 308 | https://www.kognai.ai/v1/golden-kog/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 →
about About Golden Kog ~34
What Golden Kog does and never does, its prices (set by the Kognai CFO) and how to pay. Free.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
analyze_token Analyze a token ~164
One token risk and structure analysis: risk level and points from a published rule table (a regulated issuer's asset, such as USDC or an xStock, is ISSUER CONTROLLED: its issuer powers listed as expected controls with the issuer named, not as points), every flag with its evidence, the measured facts (authorities, holders outside pools, launch bundle and dev wallet, liquidity and LP, chart structure in numbers) and a short text. Risk and structure facts, never a trading signal. Paid: partner key or x402.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | solana (pump.fun ecosystem first) or base |
| token | string | yes | the token address: a Solana mint (base58) or a Base contract (0x and 40 hex) |
No output schema declared.
No examples provided.
get_job Get a job ~47
A job by its id with the view token from the paid reply: its state, report and alerts. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
| view_token | string | yes | – |
No output schema declared.
No examples provided.
monitor_token Watch a token ~151
Watches one token for a window with risk alerts (dev wallet sells, a top holder sells a large share, liquidity pulled, authorities changed, a new wallet cluster), by webhook or by polling get_job. The window on sale is 24 hours. Paid: partner key or x402.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | solana (pump.fun ecosystem first) or base |
| hours | integer | – | the window in hours; 24 is the window on sale |
| token | string | yes | the token address: a Solana mint (base58) or a Base contract (0x and 40 hex) |
| webhook | string | – | optional public https url that receives each alert as a JSON POST |
No output schema declared.
No examples provided.
resolve_ticker Find the tokens behind a ticker ~125
The Solana tokens that carry a ticker such as WIF or $WIF, side by side: symbol, name, mint, total liquidity in USD, pool count, age, and verified true when the mint is on Jupiter verified list; verified first, then liquidity. Candidates only: Golden Kog never picks one and never analyses a ticker. Show them to the person, let the person choose, then call analyze_token with that exact mint. KOG is never a candidate. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| ticker | string | yes | the ticker, letters and digits, with or without $ |
No output schema declared.
No examples provided.
How do I install the Golden Kog token risk analyst by Kognai MCP server?
Golden Kog token risk analyst by Kognai is a hosted endpoint at https://www.kognai.ai/v1/golden-kog/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 · www.kognai.ai
claude mcp add --transport http ai-kognai-golden-kog 'https://www.kognai.ai/v1/golden-kog/mcp'
What is the Golden Kog token risk analyst by Kognai MCP server?
Golden Kog token risk analyst by Kognai is an MCP server listed in the public MCP registry as ai.kognai/golden-kog. Risk and structure facts on one Solana or Base token, never a trading signal. Paid per call by x402. This page covers its hosted endpoint (https://www.kognai.ai/v1/golden-kog/mcp).
Is the Golden Kog token risk analyst by Kognai MCP server safe to use?
Golden Kog token risk analyst by Kognai scores 66 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 Golden Kog token risk analyst by Kognai MCP server expose?
Golden Kog token risk analyst by Kognai exposes 5 tools: about, resolve_ticker, analyze_token, monitor_token, get_job. Their descriptions and schemas cost roughly 521 tokens of context every time the server is loaded.
Does the Golden Kog token risk analyst by Kognai MCP server require authentication?
No. We connected to Golden Kog token risk analyst by Kognai without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Golden Kog token risk analyst by Kognai MCP server still maintained?
Golden Kog token risk analyst by Kognai is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.