io.github.rog0x/network
NPM · @ROG0X/MCP-NETWORK-TOOLS · SCANNED SEP 21
DNS, IP info, SSL, WHOIS, ping for AI agents
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 182 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 407 tokens (~81/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 Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 5 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
How do I install the io.github.rog0x/network MCP server?
io.github.rog0x/network runs locally as an npm package, launched with npx -y @rog0x/mcp-network-tools. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @rog0x/mcp-network-tools
claude mcp add rog0x-network -- npx -y @rog0x/mcp-network-tools
{
"mcpServers": {
"rog0x-network": {
"command": "npx",
"args": [
"-y",
"@rog0x/mcp-network-tools"
]
}
}
} {
"servers": {
"rog0x-network": {
"command": "npx",
"args": [
"-y",
"@rog0x/mcp-network-tools"
]
}
}
} codex mcp add rog0x-network -- npx -y @rog0x/mcp-network-tools
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"rog0x-network": {
"type": "local",
"command": [
"npx",
"-y",
"@rog0x/mcp-network-tools"
],
"enabled": true
}
}
} openclaw mcp add rog0x-network --command npx --arg -y --arg @rog0x/mcp-network-tools
mcp_servers:
rog0x-network:
command: "npx"
args: ["-y", "@rog0x/mcp-network-tools"] {
"McpServers": {
"rog0x-network": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@rog0x/mcp-network-tools"
]
}
}
} assistant mcp add rog0x-network -t stdio -c npx -a -y @rog0x/mcp-network-tools
{
"mcpServers": {
"rog0x-network": {
"command": "npx",
"args": [
"-y",
"@rog0x/mcp-network-tools"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −3
- Stability: pass → 0.80 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 Sept 2026 · Analysed npm/@rog0x/mcp-network-tools@1.0.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
dns_lookup ~134
Resolve a domain name to DNS records (A, AAAA, MX, TXT, NS, CNAME, SOA). Supports reverse DNS and propagation checking.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name to look up (e.g. example.com) |
| mode | string | – | Mode: 'resolve' (default) for forward DNS, 'reverse' for reverse DNS (pass IP in domain), 'propagation' to check across public DNS servers |
| record_types | array | – | Record types to query (default: all). Options: A, AAAA, MX, TXT, NS, CNAME, SOA |
No output schema declared.
No examples provided.
http_ping ~98
Measure HTTP response time to a URL over multiple requests. Returns per-request latency and statistics: average, min, max, p95, and success rate.
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | Number of requests to send (default: 5, max: 20) |
| timeout_ms | number | – | Timeout per request in milliseconds (default: 10000) |
| url | string | yes | URL to ping (e.g. https://example.com) |
No output schema declared.
No examples provided.
ip_info ~52
Get geolocation and network information for an IP address: country, city, ISP, ASN, coordinates. Supports IPv4 and IPv6.
| Name | Type | Req | Description |
|---|---|---|---|
| ip | string | yes | IPv4 or IPv6 address to look up |
No output schema declared.
No examples provided.
ssl_check ~72
Check the SSL/TLS certificate of a host: validity, issuer, expiry date, days until expiry, subject alternative names, certificate chain, cipher, and protocol.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | Hostname to check (e.g. example.com) |
| port | number | – | Port number (default: 443) |
No output schema declared.
No examples provided.
whois_lookup ~51
Look up WHOIS information for a domain: registrar, creation date, expiry date, nameservers, and domain status.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name to look up (e.g. example.com) |
No output schema declared.
No examples provided.
What is the io.github.rog0x/network MCP server?
io.github.rog0x/network is an MCP server listed in the public MCP registry as io.github.rog0x/network. DNS, IP info, SSL, WHOIS, ping for AI agents. This page covers its npm package (@rog0x/mcp-network-tools).
Is the io.github.rog0x/network MCP server safe to use?
io.github.rog0x/network scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. 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.github.rog0x/network MCP server expose?
io.github.rog0x/network exposes 5 tools: dns_lookup, ip_info, ssl_check, whois_lookup, http_ping. Their descriptions and schemas cost roughly 407 tokens of context every time the server is loaded.
Is the io.github.rog0x/network MCP server still maintained?
io.github.rog0x/network is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.rog0x/network MCP server under?
io.github.rog0x/network declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.