Physical Layer Linter — validates RF link budgets, Shannon capacity, and noise floors.
Physical Layer Linter — An MCP server that validates RF and physics calculations against hard physical limits. Catches AI hallucinations in engineering workflows. LLMs routinely hallucinate physics. PhysBound catches it: | Category | LLM Hallucination | PhysBound Truth | Verdict | ---|----------|-------------------|-----------------|---------| 1 | Shannon-Hartley | "20 MHz 802.11n at 15 dB SNR…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
Physical Layer Linter — An MCP server that validates RF and physics calculations against hard physical limits. Catches AI hallucinations in engineering workflows. LLMs routinely hallucinate physics. PhysBound catches it: # | Category | LLM Hallucination | PhysBound Truth | Verdict | ---|----------|-------------------|-----------------|---------| 1 | Shannon-Hartley | "20 MHz 802.11n at 15 dB SNR achieves 500 Mbps" | Shannon limit: 100.6 Mbps | CAUGHT | 2 | Shannon-Hartley | "100 MHz 5G channel…
Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.