Cve Intel MCP server

• get_agent_wallet_statusFree

  Inspect an agent's account ledger: remaining free trial calls (out of 5), prepaid USD balance, cumulative spend, total API calls, and total LLM tokens saved. WHEN TO USE: Call before a batch of paid tool executions or after completing a Stripe or USDC top-up to confirm your balance. WHEN NOT TO USE: Do not use to process web content, execute marketplace tools, or submit payments; use the other tools on this server for execution. PARAMETER INTERACTIONS: Omit agent_id to inspect the default trial account derived from your client IP, or pass your explicit agent_id or agd_pass_ session key to check a specific funded wallet. Free and read-only: never charges a fee or consumes a free trial call. Example: get_agent_wallet_status(agent_id='example')

• scan_package_cve_advisoriesFree

  Queries live Google OSV.dev vulnerability intelligence for any PyPI, npm, Go, or Rust crate and returns active CVEs, GHSA advisories, and patched versions. WHEN TO USE: Call `scan_package_cve_advisories` when your task requires deterministic `cve-intel` analysis for `package`; use `get_agent_wallet_status` to check your remaining free trial quota or prepaid balance. WHEN NOT TO USE: Do not use for unrelated domains or binary media. PARAMETER INTERACTIONS: Pass the target `package` as a non-empty string; omit `agent_id` and `tx_hash` during your 5 free trial calls, or supply `agent_id` (`agd_pass_...`) / `tx_hash` for paid execution. Read-only and idempotent; results are cached for 1 hour (<5ms cache hit). $0.01 per call. Pricing: the first 5 calls per agent_id are free and failed calls are never charged. After 5 calls, the tool returns a payment-required quote (not a fatal error) with a $2 Stripe top-up link and Base/Solana USDC addresses; complete payment, then retry with your agd_pass_ key in agent_id or pass tx_hash. Example: scan_package_cve_advisories(package='example')

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 302ms20/20
• Tool poisoning2 tool descriptions checked15/15
• Auth qualityopen endpoint, read-only tools10/15
• Maintenanceno repository listed3/15
• Maintainer identityno repository or website to verify2/10

Safety score

67/100

higher than 28% of 918 Security servers

Tools

2

the typical Security server has 6

Tools that change things

0%

typical: 0%. Fewer write tools means less an agent can break

Uptime

100%

of our recent checks; the typical remote Security server answers 100%

Response time

106 ms

faster than 80% of 550 Security servers

Cve Intel: common questions

Is Cve Intel MCP server safe?

With care: it is graded C, so read the findings first (67/100). Read the Cve Intel safety report

How do I install Cve Intel?

It runs remotely at cve-intel-72343955726.us-central1.run.app. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.

Does Cve Intel need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Cve Intel maintained?

The latest release is v1.0.0.

Is Cve Intel up?

100% of our last 25 checks got an answer. We check remote servers about four times a day.

What can I use instead of Cve Intel?

Servers from other publishers that do the same job: Dependency Auditor MCP server, Dependency Auditor MCP server and npm Registry MCP Server.

How does Cve Intel compare with other Security MCP servers?

safety score 67/100 (higher than 28% of 918 Security servers); tools 2 (the typical Security server has 6); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.