Fray — WAF Security Testing MCP Server

io.github.dalisecurityPublished by GitHub account dalisecurityv3.0.1Updated Oct 24, 2026

WAF security testing: 5,500+ payloads, 25 WAF fingerprints, 21 recon checks, bypass AI

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

Fray is a local MCP server for WAF security testing, offering payloads, WAF fingerprints, recon checks and bypass assistance to an AI assistant.

What you can do
Run WAF security testing from the assistant, drawing on a large payload library of over 5,500 entries and 25 WAF fingerprints to identify protections in place. Perform reconnaissance with 21 built-in checks. Get help crafting bypass attempts against detected WAFs. The manifest lists no individual tools, so exact operations are not documented here.
When to use it
Useful for authorized security testing or penetration-testing work where you need to identify a web application firewall and probe its defenses, and want an assistant to drive the payload and recon steps.
Requirements
Runs as a local process on the user's machine via the PyPI package fray over stdio; desktop only, not available as a web executable. No authentication, environment variables or headers are declared.
Before you install
This is offensive security tooling: payloads and bypass assistance are meant for systems you are authorized to test, and misuse may be illegal or disruptive. The manifest declares no credentials, but testing sends crafted requests to target systems, so confirm scope and permission first.

Installation

In SourceWeft

  1. Open Fray — WAF Security Testing MCP Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v3.0.1LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.