io.github.Jing7ao/aihot-mcp

Name: io.github.Jing7ao/aihot-mcp
Author: io.github.Jing7ao

MCPcommunity

v1.1.0io.github.Jing7aoUnknownUpdated 4mo agonpm GitHub

AI HOT 资讯 MCP Server - 让 Claude Code 直接获取 AI 行业日报和动态

让 Claude Code 直接获取 AI 行业日报和最新动态，数据来自 aihot.virxact.com。 ------|------|----------| Pro | ￥70/年 | 无限查询 + 历史日报 | | 获取 AI HOT 日报（最新一期或指定日期） | | 搜索 AI 动态，支持分类/关键词/时间范围 | 日报按五个版块组织：模型发布、产品发布、行业动态、论文研究、技巧与观点。覆盖 OpenAI、Anthropic、Google、Meta 等主要 AI 公司和全球 AI 资讯源。 Free tier 每天 50 次搜索查询。购买 Pro 后获得 License Key，配置到环境变量即可无限使用。

Works in

ClaudeCursorCopilotGemini

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.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

4mo agoLast update

Package

Authorio.github.Jing7ao

LicenseUnknown

Version1.1.0

Sourcemcp-registry

npmaihot-mcp

GitHubJing7ao/aihot-mcp

SBOMCycloneDX 1.6 ↓

Trust Status

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/20

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/5

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

—npm Trusted Publishing (Sigstore)+0/5

→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo

—npm maintainer match+0/5

→ Earned once your identity is verified above and that login is an npm maintainer of this package

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

Provenance—

Dependencies✓ 60 resolved+ · none vulnerable

Tool surface4 tools · none privileged

Security scan✓ Cleanv1.1.0 · 3mo agoHow well does this scan work?

EvalsNone

IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

4 tools · none privileged

Statically extracted from the published packagev1.1.0 · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

get_ai_dailyNo description published

This tool published no description. Forge does not invent one.

search_ai_newsNo description published

This tool published no description. Forge does not invent one.

list_ai_dailiesNo description published

This tool published no description. Forge does not invent one.

verify_licenseNo description published

This tool published no description. Forge does not invent one.

0 of 4 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Keywords

mcp

Alternatives

Comparing tool surfaces…

io.github.Jing7ao/aihot-mcp

Tools

Tools exposed

No dependency coverage