MCP server for ChipsNews — manage news sources, articles, and triggers
MCP (Model Context Protocol) server for ChipsNews — manage news configuration, sources, articles, and fetch triggers from Claude Code, Claude Desktop, or any MCP client. uv (recommended) or pip No installation needed with : The server uses environment variables for authentication: Variable | Description | Default | ----------|-------------|---------| | Your API key (Bearer token) | — | Add to…
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”.
MCP (Model Context Protocol) server for ChipsNews — manage news configuration, sources, articles, and fetch triggers from Claude Code, Claude Desktop, or any MCP client. uv (recommended) or pip No installation needed with : The server uses environment variables for authentication: Variable | Description | Default | ----------|-------------|---------| | Your API key (Bearer token) | — | Add to your project's : ------|-------------| | Get news configuration (keywords, language, frequency, etc.) |…
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.