Home/Compare/cve-mcp-server vs Agent-Reach

Comparison

cve-mcp-server vs Agent-Reach

Verdict

Pick cve-mcp-server when license: cve-mcp-server is Apache-2.0, Agent-Reach is MIT; pick Agent-Reach when license: Agent-Reach is MIT, cve-mcp-server is Apache-2.0.

Markdown twin · cve-mcp-server alternatives · Agent-Reach alternatives

GraphCanon updated today

cve-mcp-server logo

cve-mcp-server

mukul975/cve-mcp-server

1.1kpushed Jun 22, 2026
vs
Agent-Reach logo

Agent-Reach

Panniantong/Agent-Reach

55kpushed Jul 10, 2026

Trust & integrity

Signalcve-mcp-serverAgent-Reach
Maintenance
Active (18d since push)
As of today · github_public_v1
Very active (0d since push)
As of today · github_public_v1
Provenance
Not a fork · Personal account
As of today · github_public_v1
Not a fork · Personal account
As of today · github_public_v1
Security (OSV)
No MCP manifest
As of today · mcp_manifest
No MCP manifest
As of today · mcp_manifest

Tagline

cve-mcp-server
Production-grade MCP server giving Claude 27 security intelligence tools across 21 APIs — CVE lookup, EPSS scoring, CISA KEV, MITRE ATT&CK, Shodan, VirusTotal, and more.
Agent-Reach
Give your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.

Stars

cve-mcp-server
1.1k
Agent-Reach
55k

Forks

cve-mcp-server
176
Agent-Reach
4.5k

Open issues

cve-mcp-server
8
Agent-Reach
144

Language

cve-mcp-server
Python
Agent-Reach
Python

Adopt for

cve-mcp-server
-
Agent-Reach
-

Persona

cve-mcp-server
-
Agent-Reach
-

Runtime

cve-mcp-server
-
Agent-Reach
-

License

cve-mcp-server
Apache-2.0
Agent-Reach
MIT

Last pushed

cve-mcp-server
Jun 22, 2026
Agent-Reach
Jul 10, 2026

Categories

cve-mcp-server
Developer Tools
Agent-Reach
AI Agents, LLM Frameworks, Developer Tools

Trust and health

Maintenance

cve-mcp-server
Active (82%)
Agent-Reach
Very active (96%)

Days since push

cve-mcp-server
18d
Agent-Reach
0d

Open issues (now)

cve-mcp-server
8
Agent-Reach
144

Full report

cve-mcp-server
Trust report
Agent-Reach
Trust report

Choose cve-mcp-server if…

  • License: cve-mcp-server is Apache-2.0, Agent-Reach is MIT.
  • Tags unique to cve-mcp-server: cve, cisa-kev, claude-ai, cybersecurity.
  • Leaner open-issue backlog (8).

When NOT to use cve-mcp-server

  • Developer Tools: A gateway is overkill when you're pinned to a single provider and model.

Choose Agent-Reach if…

  • License: Agent-Reach is MIT, cve-mcp-server is Apache-2.0.
  • Tags unique to Agent-Reach: agent-infrastructure, ai-search, bilibili, claude-code.
  • Also covers AI Agents, LLM Frameworks.

When NOT to use Agent-Reach

  • AI Agents: Don't use an agent loop when a deterministic workflow would do; agents add latency, cost, and non-determinism.
  • LLM Frameworks: Avoid a framework for a single prompt-and-retrieve call; the abstraction can cost more than it saves.
  • Developer Tools: A gateway is overkill when you're pinned to a single provider and model.

Explore

Sources

Every stat on this page traces to a dated GitHub sync, license file, enrichment field, or trust scan.

GitHub stars on cards: cve-mcp-server 1.1k · Agent-Reach 55k (synced Jul 11, 2026).

Common questions

What is the difference between cve-mcp-server and Agent-Reach?
cve-mcp-server: Production-grade MCP server giving Claude 27 security intelligence tools across 21 APIs — CVE lookup, EPSS scoring, CISA KEV, MITRE ATT&CK, Shodan, VirusTotal, and more.. Agent-Reach: Give your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.. See the comparison table for live GitHub stats and shared categories.
When should I choose cve-mcp-server over Agent-Reach?
Choose cve-mcp-server over Agent-Reach when License: cve-mcp-server is Apache-2.0, Agent-Reach is MIT; Tags unique to cve-mcp-server: cve, cisa-kev, claude-ai, cybersecurity; Leaner open-issue backlog (8).
When should I choose Agent-Reach over cve-mcp-server?
Choose Agent-Reach over cve-mcp-server when License: Agent-Reach is MIT, cve-mcp-server is Apache-2.0; Tags unique to Agent-Reach: agent-infrastructure, ai-search, bilibili, claude-code; Also covers AI Agents, LLM Frameworks.
When should I avoid cve-mcp-server?
Developer Tools: A gateway is overkill when you're pinned to a single provider and model.
When should I avoid Agent-Reach?
AI Agents: Don't use an agent loop when a deterministic workflow would do; agents add latency, cost, and non-determinism. LLM Frameworks: Avoid a framework for a single prompt-and-retrieve call; the abstraction can cost more than it saves. Developer Tools: A gateway is overkill when you're pinned to a single provider and model.
Is cve-mcp-server or Agent-Reach more popular on GitHub?
Agent-Reach has more GitHub stars (54,715 vs 1,077). Stars measure visibility, not whether either tool fits your constraints.
Are cve-mcp-server and Agent-Reach open source?
Yes - both are open-source projects on GitHub (cve-mcp-server: Apache-2.0, Agent-Reach: MIT).
Where can I find alternatives to cve-mcp-server or Agent-Reach?
GraphCanon lists graph-backed alternatives at cve-mcp-server alternatives and Agent-Reach alternatives (cve-mcp-server markdown twin, Agent-Reach markdown twin), ranked by typed relationship edges rather than popularity votes.
Is there a machine-readable version of this comparison?
Yes. The markdown twin at this comparison mirrors this page for agents and LLM crawlers, with the same stats table and FAQ answers.
Which is better maintained, cve-mcp-server or Agent-Reach?
cve-mcp-server: Active. Agent-Reach: Very active. Compare maintenance labels, days since push, and release cadence in the trust section below - stars alone do not measure maintenance.
Where are the full trust reports for cve-mcp-server and Agent-Reach?
GraphCanon publishes per-repo trust reports with dated maintenance, provenance, and scan summaries: cve-mcp-server trust report; Agent-Reach trust report.