Prior-art exploration for software projects; finds related patents, never judges infringement
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.
PATENT_CHECKER_OPS_KEYAPI keyoptionalEPO OPS credentials; leave unset for degraded mode
PATENT_CHECKER_OPS_SECRETAPI keyoptionalEPO OPS credentials; leave unset for degraded mode
PATENT_CHECKER_SERVER_TOKEN_FILEAPI keyrequiredFile holding the bearer token clients must present
PATENT_CHECKER_OPS_KEY_FILEAPI keyoptionalEPO OPS credentials; leave unset for degraded mode
PATENT_CHECKER_OPS_SECRET_FILEAPI keyoptionalEPO OPS credentials; leave unset for degraded mode
Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge has no scan on record for this entry, so it holds no observation of its tool surface. That is an absence of evidence, not evidence that it exposes no tools.
Prior-art exploration for software projects; finds related patents, never judges infringement
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.