OWASP MCP Server

Created By
shadsidda year ago
Overview

what is OWASP ZAP MCP Server?

OWASP ZAP MCP Server is a tool that provides an interface to interact with the OWASP ZAP (Zed Attack Proxy) API, facilitating security testing of web applications.

how to use OWASP ZAP MCP Server?

To use the OWASP ZAP MCP Server, install the necessary dependencies, run the server, and configure it with your ZAP API endpoint and API key. You can then utilize various tools to perform security scans and retrieve alerts.

key features of OWASP ZAP MCP Server?

  • Configure ZAP API endpoint and authentication
  • Start active scans against target URLs
  • Monitor scan progress
  • Retrieve security alerts
  • Spider websites
  • Generate security reports

use cases of OWASP ZAP MCP Server?

  1. Conducting security assessments on web applications.
  2. Automating security scans during the development process.
  3. Generating reports for compliance and security audits.

FAQ from OWASP ZAP MCP Server?

  • What is OWASP ZAP?

OWASP ZAP is an open-source web application security scanner that helps find vulnerabilities in web applications.

  • Is the OWASP ZAP MCP Server free to use?

Yes! The OWASP ZAP MCP Server is free and open-source.

  • Do I need to run ZAP separately?

Yes, you need to have ZAP running with the API enabled to use the MCP Server.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
shadsidd
Star
0
Language
Python
License
-
Category
security
Tags

Recommend Servers

View All
Hellogrowthcrm

2 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago
Payai X402 Tools

11 hours ago