ai-smithery-ramadasmr-networkcalc-mcp
ToolProof Connection Signal
Connect With Limits
Connect only with scoped credentials, limited permissions, audit logging, and human review for sensitive outputs or unusual requests.
Evidence Confidence86/100
Tools Inferred10
Control Signals0
Profile status
ToolProof reviewSnapshotEvidence-backed review from observed public information.
Owner statusUnclaimedOwner-provided details have not been maintained yet.
Watch statusNot monitoredEnable ToolProof Watch to monitor drift and freshness.
Last observed2026-06-07T19:20:29.210576+00:00MCP servers can change after observation.
Why this signal
- Source evidence fetched from 2 file(s).
- 10 MCP tool(s) inferred: calculate_subnet, certificate_info, dns_lookup, fetch_cert_info, fetch_dns_lookup.
- No visible control signals were observed.
- 3 static finding(s) should be reviewed before connection.
What this server exposes
calculate_subnetcertificate_infodns_lookupfetch_cert_infofetch_dns_lookupfetch_spf_lookupfetch_subnet_infofetch_whois_lookupspf_lookupwhois_lookup
Source and observation
Source: https://github.com/ramadasmr/networkcalc-mcp
Observed: 2026-06-07T19:20:29.210576+00:00
Machine ID: mcp:ai-smithery-ramadasmr-networkcalc-mcp
Capabilities inferred
- remote_context_data_exposure
- critical_or_unmitigated_high
- {"has_packages": false, "has_remotes": true, "package_registry_types": [], "remote_types": ["streamable-http"], "requires_secret_header": true}
Controls observed
- No controls observed.
Recommended controls
- Install in a sandbox before team or production use.
- Pin the exact package/repository version.
- Review install scripts, Dockerfile behavior, and dependency pins.
- Do not use production credentials during first install.
- Restrict filesystem, repository, cloud, and database scope.
- Require human approval for destructive actions.
- Review what prompts, queries, or documents are sent to remote endpoints.
- Avoid sensitive context until data handling is understood.
Open questions before connection
- What credentials or environment variables are required?
- What data can leave the local environment?
- What systems can the agent reach through this server?
- What actions should require human approval?
Findings and concerns
- Install risk pattern: unpinned_dependency — Dockerfile:16
- Detected capability: network_egress — main.py:3
- Configuration environment variable access — main.py:117
Claim or update this profile
Are you the owner of this MCP server? Submit official docs, intended use cases, support links, security contact, and recommended safe configuration.
Owner-provided information is shown separately from ToolProof evidence and does not change the connection signal unless reviewed.
Payment may buy review, monitoring, or sponsored visibility. It does not change the ToolProof connection signal.
Evidence fetched
- https://github.com/ramadasmr/networkcalc-mcp
- Registry entry: ai.smithery/ramadasmr-networkcalc-mcp 1.13.0