Ten machine-readable signals on one public page: the top miss if any, and a receipt we re-verify.
Inferred from the transports this listing declares (streamable-http). 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 has not completed a tools/list handshake against this endpoint, so it holds no observation of what the server exposes. Nothing here says it exposes nothing.
Ten machine-readable signals on one public page: the top miss if any, and a receipt we re-verify.
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.