Skip to main content
Glama
ZeroPathAI

ZeroPath MCP Server

Official
by ZeroPathAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ZEROPATH_ORG_IDYesYour ZeroPath organization ID
ZEROPATH_TOKEN_IDYesYour ZeroPath API token ID generated from organization settings
ZEROPATH_TOKEN_SECRETYesYour ZeroPath API token secret generated from organization settings

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
search_vulnerabilitiesC

Search for vulnerabilities using the Zeropath API with a simple search query.

get_issueB
Get a specific vulnerability issue by its ID, including patch information if available.

Args:
    issue_id (str): The ID of the issue to retrieve
approve_patchC
Approve a patch for a specific vulnerability issue.

Args:
    issue_id (str): The ID of the issue whose patch should be approved
mark_true_positiveC
Mark a security issue as a true positive (confirmed vulnerability).

Args:
    issue_id: The ID of the issue to mark as true positive
mark_false_positiveA
Mark a security issue as a false positive (not a real vulnerability).

Args:
    issue_id: The ID of the issue to mark as false positive
archive_issueB
Archive a security issue to remove it from active view.

Args:
    issue_id: The ID of the issue to archive
unarchive_issueB
Unarchive a previously archived security issue to restore it to active view.

Args:
    issue_id: The ID of the issue to unarchive
generate_patchC
Generate an automated patch/fix for a security issue.

Args:
    issue_id: The ID of the issue to generate a patch for
start_scanC
Start a new security scan on one or more repositories.

Args:
    repository_ids: List of repository IDs to scan
list_scansB
List security scans with optional filtering and pagination.

Args:
    search_query: Optional search term to filter scans
    repository_ids: Optional list of repository IDs to filter by
    scan_type: Optional scan type filter (FullScan, PrScan, SCAScan)
    page: Page number (default: 1)
    page_size: Number of results per page (default: 10)
list_repositoriesB
List all repositories in the organization.

Args:
    search_query: Optional search term to filter repositories
get_security_postureB

Get the overall security posture metrics for the organization. Returns security score, vulnerability trends, and risk assessment.

get_issues_by_vuln_classB

Get issue statistics grouped by vulnerability class/type. Shows distribution of vulnerabilities by category (XSS, SQLi, etc.).

get_summary_statisticsB

Get aggregated summary statistics across the organization. Includes total issues, patches, repositories, and key metrics.

list_sca_vulnerabilitiesB
Search for SCA (Software Composition Analysis) vulnerabilities in dependencies.

Args:
    search_query: Optional search term to filter vulnerabilities
    repository_ids: Optional list of repository IDs to filter by
    ecosystems: Optional list of ecosystems to filter (npm, pip, maven, etc.)
    transitivity: Optional filter by dependency type (direct, transitive)
    page: Page number (default: 1)
    page_size: Number of results per page (default: 50)
get_sca_vulnerabilityC
Get detailed information about a specific SCA vulnerability.

Args:
    vulnerability_id: The ID of the vulnerability to retrieve
list_sca_repositoriesB

List repositories with their aggregated dependency inventory information. Shows which repositories have been analyzed for dependencies.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.4/5.0

Scored across 17 tools

Disambiguation4/5

Most tools have distinct purposes, but some overlap exists: 'get_issues_by_vuln_class' and 'search_vulnerabilities' both involve vulnerability discovery, though the former focuses on statistics and the latter on search. 'list_sca_vulnerabilities' and 'search_vulnerabilities' could be confused as both handle vulnerability queries, but their scopes differ (SCA vs. general). Overall, descriptions help clarify boundaries, but minor ambiguity remains.

Naming Consistency5/5

All tools follow a consistent verb_noun naming pattern (e.g., 'approve_patch', 'archive_issue', 'generate_patch'). There are no deviations in style or convention, making the set predictable and easy to parse. This uniformity enhances usability and reduces cognitive load for agents.

Tool Count4/5

With 17 tools, the count is slightly high but reasonable for a security vulnerability management domain, covering issues, patches, scans, repositories, and SCA. It feels comprehensive without being overwhelming, though it borders on the upper limit of typical scoping (3-15 tools).

Completeness5/5

The toolset provides complete coverage for security vulnerability management: CRUD operations for issues (get, archive/unarchive, mark status), patch lifecycle (generate, approve), scanning (start, list), repository management, and SCA vulnerabilities. No obvious gaps exist; agents can handle full workflows from detection to resolution.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources