Avalyz

com.avalyzPublished by avalyz.comOfficial publisherv1.3.1Updated Oct 26, 2026

Acceptance tests for any web app, however it's built: full journeys on apps you're allowed to test.

VerifiedStreamable HTTPWeb executableBrowser AutomationDeveloper Tools

Overview

AI-generated overview

Avalyz is a remote MCP server that lets an assistant run acceptance tests and full user journeys against web apps you are permitted to test.

What you can do
  • Run acceptance tests against a web app, whatever stack it is built with.
  • Exercise complete end-to-end user journeys rather than isolated checks.
  • Connect from an assistant over a remote HTTP endpoint, with no local package to install.
  • Authenticate either through OAuth or with an Avalyz API key.
When to use it
Use it when you want an assistant to verify that a web app still works end to end, for example after changes or before a release, and you have permission to test the target app.
Requirements
A remote MCP endpoint at avalyz.com over streamable HTTP. An Avalyz account is needed for the API key option; authentication is via OAuth or an Authorization header carrying a Bearer API key. Network access to the endpoint is required.
Before you install
The Authorization header carries a secret API key, so keep it out of shared logs and transcripts. Tests act on live web apps you are allowed to test, so confirm you have permission before pointing it at a target.

Installation

In SourceWeft

  1. Open Avalyz in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.avalyz%2Favalyz/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "avalyz": {
      "type": "http",
      "url": "https://avalyz.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v1.3.1LatestOct 14, 2026
  2. v1.2.2Oct 13, 2026

Score

56% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

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

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

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

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.