io.nip.5-9-107-124/token-risk
REMOTE · 5-9-107-124.NIP.IO · SCANNED SEP 11
DeFi pool yield+security intelligence & token/contract risk scanner. USDC on Base via x402.
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 Security11
- 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.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.
How do I install the io.nip.5-9-107-124/token-risk MCP server?
io.nip.5-9-107-124/token-risk is a hosted endpoint at https://5-9-107-124.nip.io/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 · 5-9-107-124.nip.io
claude mcp add --transport http io-nip-5-9-107-124-token-risk 'https://5-9-107-124.nip.io/mcp'
{
"mcpServers": {
"io-nip-5-9-107-124-token-risk": {
"url": "https://5-9-107-124.nip.io/mcp"
}
}
} {
"servers": {
"io-nip-5-9-107-124-token-risk": {
"type": "http",
"url": "https://5-9-107-124.nip.io/mcp"
}
}
} [mcp_servers.io-nip-5-9-107-124-token-risk] url = "https://5-9-107-124.nip.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-nip-5-9-107-124-token-risk": {
"type": "remote",
"url": "https://5-9-107-124.nip.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-nip-5-9-107-124-token-risk --url 'https://5-9-107-124.nip.io/mcp' --transport streamable-http
mcp_servers:
io-nip-5-9-107-124-token-risk:
url: "https://5-9-107-124.nip.io/mcp" {
"McpServers": {
"io-nip-5-9-107-124-token-risk": {
"Transport": "http",
"Url": "https://5-9-107-124.nip.io/mcp"
}
}
} assistant mcp add io-nip-5-9-107-124-token-risk -t streamable-http -u 'https://5-9-107-124.nip.io/mcp'
{
"mcpServers": {
"io-nip-5-9-107-124-token-risk": {
"type": "http",
"url": "https://5-9-107-124.nip.io/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.
- 11 Sept 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 10 Sept 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 9 Sept 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 8 Sept 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 7 Sept 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 5 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: 0.83 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 2 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
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 11 Sept 2026 · Probed https://5-9-107-124.nip.io/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of 5-9-107-124.nip.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| nip.io. | 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://5-9-107-124.nip.io/mcp | Unreachable | ||
| http (plaintext) | http://5-9-107-124.nip.io/mcp | HTTPS enforced |
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 →
defi_pool ~55
DeFi pool pre-deposit intelligence: live APY + TVL enriched with an on-chain security read of the pool's underlying token contracts. $0.02 USDC (Base).
| Name | Type | Req | Description |
|---|---|---|---|
| pool | string | yes | – |
No output schema declared.
No examples provided.
defi_pool_deep ~50
Deep DeFi pool intelligence: + 30d yield stability + deep contract-control analysis of the underlying tokens. $0.06 USDC (Base).
| Name | Type | Req | Description |
|---|---|---|---|
| pool | string | yes | – |
No output schema declared.
No examples provided.
defi_pool_top ~83
Risk-adjusted DeFi yield screener: best Base/Ethereum pools ranked by yield discounted for volatility, incentive-share, TVL, outliers, IL. $0.02 USDC (Base).
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | – |
| limit | integer | – | – |
| min_tvl | integer | – | – |
| stablecoin | boolean | – | – |
No output schema declared.
No examples provided.
token_risk_deep ~61
Deep contract-control analysis: owner()/admin, renounced?, EOA-vs-multisig owner, proxy implementation. $0.05 USDC (Base).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| chain | string | – | – |
No output schema declared.
No examples provided.
token_risk_scan ~70
Static on-chain token/contract risk scan (proxy/mint/pause/blacklist/setFee/ honeypot, verified source). Returns risk_score, risk_band, flags. $0.02 USDC (Base).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| chain | string | – | – |
No output schema declared.
No examples provided.
What is the io.nip.5-9-107-124/token-risk MCP server?
io.nip.5-9-107-124/token-risk is an MCP server listed in the public MCP registry as io.nip.5-9-107-124/token-risk. DeFi pool yield+security intelligence & token/contract risk scanner. USDC on Base via x402. This page covers its hosted endpoint (https://5-9-107-124.nip.io/mcp).
Is the io.nip.5-9-107-124/token-risk MCP server safe to use?
io.nip.5-9-107-124/token-risk 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.
What tools does the io.nip.5-9-107-124/token-risk MCP server expose?
io.nip.5-9-107-124/token-risk exposes 5 tools: defi_pool_top, defi_pool, defi_pool_deep, token_risk_scan, token_risk_deep. Their descriptions and schemas cost roughly 319 tokens of context every time the server is loaded.
Does the io.nip.5-9-107-124/token-risk MCP server require authentication?
Its publisher declares no required credentials for io.nip.5-9-107-124/token-risk. 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.nip.5-9-107-124/token-risk MCP server still maintained?
io.nip.5-9-107-124/token-risk 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 4 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.