Pinafly UAT

com.pinaflyPublished by pinafly.comOfficial publisherv1.1.0Updated Oct 24, 2026

Your agent writes a UAT. You walk it and pin problems. It reads and fixes them. You verify.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowDeveloper Tools

Overview

AI-generated overview

Pinafly UAT lets an AI agent write a user acceptance test, then read the problems you pin while walking it and fix them.

What you can do
  • Have the agent draft a UAT (user acceptance test) for a build.
  • Support a human review pass in which you walk the test and pin the problems you find.
  • Let the agent read those pinned problems and make fixes.
  • Support a final verification step after the fixes.
When to use it
Useful when you want an agent to produce acceptance tests for a product and then act on concrete, human-flagged issues from a review walkthrough rather than on vague feedback.
Requirements
A remote streamable HTTP endpoint at pinafly.com. Authentication is required: either OAuth, or a bearer API token created on Live review sent in the Authorization header (leave the header empty to use OAuth). A Pinafly account is implied.
Before you install
The server takes an Authorization bearer token; treat it as a secret and prefer OAuth where possible. The agent can change your product or test artifacts when fixing pinned problems, so review what it changes before verifying. No tool list is published, so the exact scope of write actions is unclear.

Installation

In SourceWeft

  1. Open Pinafly UAT 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.pinafly%2Fuat/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": {
    "pinafly-uat": {
      "type": "http",
      "url": "https://pinafly.com/mcp/uat"
    }
  }
}

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

1
  1. v1.1.0LatestOct 15, 2026

Score

67% 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
  • 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.

Other Pinafly integrations