Security & governancePublic source

Security Advisory MCP Server

Let your AI agents check for vulnerabilities. This MCP server queries the OSV.dev advisory database to search CVEs, map vulnerabilities to your dependencies, score risk, generate patch plans, and export compliance…

Open the source Read the official guide ↗

What it gives an agent

A purpose-built capability behind one MCP connection.

The server owns its domain logic and publishes a tool contract an MCP client can discover. ADK-Rust can load that contract into an agent, normalize each schema for the chosen model provider, and keep the connection lifecycle outside the agent’s business logic.

Provides security capabilities through a typed MCP contract.

Provides advisory capabilities through a typed MCP contract.

Architecture

How Security Advisory MCP Server fits into an agent system.

The model never needs the implementation details or credentials of the system behind the server. It sees reviewed tool definitions. The MCP client handles discovery and calls, while the server keeps ownership of validation, policy, and communication with its domain system.

ADK-Rust agent

Chooses a capability from the reviewed tool catalog.

→

MCP client

Discovers schemas, sends calls, and receives typed content.

→

Security Advisory MCP Server

Validates the request and owns 6 documented tool contracts.

→

Domain system

Keeps the API, data, credentials, and business rules behind the server.

Connection: stdio · Server framework: ADK MCP SDK + rmcp

Security Advisory MCP Server architecture diagram from its official repository

Tool catalog

What can an agent ask Security Advisory MCP Server to do?

Each tool has a stable name, a human-readable purpose, and a JSON input contract discovered during MCP initialization. Risk classes come from the project’s registry manifest when one is available.

6 named tools

search_advisories

Search advisories (CVE/GHSA/OSV/RustSec) by package, ecosystem, or keyword

read only

get_advisory

Get full advisory details by ID (CVE-*, GHSA-*, RUSTSEC-*, OSV-*)

read only

audit_dependencies

Map advisories against project dependencies from lockfiles

read only

score_risk

Score practical risk — severity, exploitability, exposure, reachability

read only

remediation_plan

Generate a remediation plan: upgrade, patch, workaround, rollout order

read only

export_findings

Export security findings as audit/compliance evidence

read only

Governance

Understand the effect of every tool.

A server connection inherits the authority of its credentials and deployment environment. The declarations below come from this project’s README and MCP registry manifest; your application still decides which tools an agent receives and where approval is required.

6 read only

The registry manifest declares read only tool risk classes.

MCP surface

What the current documentation declares.

MCP can carry tools, resources, prompts, structured results, progress, cancellation, and long-running work. This record highlights the modern protocol features explicitly mentioned by this repository.

The current README concentrates on its tool surface. Check the source and release notes before relying on optional MCP capabilities beyond tool discovery and invocation.

ADK MCP SDKrmcpRegistry manifest

Install and connect

Follow the project’s documented starting point.

Install the server in the environment that owns its credentials and domain access. Add it to your MCP host, verify the discovered tools, and narrow the toolset before giving it to a production agent.

Install

cargo install mcp-security-advisory

ADK-Rust connection shape

let toolset = McpToolset::from_stdio(
    "mcp-security-advisory",
    ["mcp-security-advisory"],
).await?;

let agent = LlmAgentBuilder::new("agent")
    .tools(toolset.tools().await?)
    .build()?;

Commands and configuration are extracted from the public README. Confirm prerequisites, environment variables, and release-specific options in the official documentation before deployment.

Official documentation

Continue with the project maintainers’ source of truth.

This page provides an approachable map of the server. The repository remains authoritative for exact schemas, prerequisites, configuration, examples, tests, releases, and security updates.

Overview ↗README.md CHANGELOG ↗CHANGELOG.md Architecture ↗docs/architecture.svg Issues and support ↗github.com issues

Keep exploring