Venture Foundry QA

io.github.ventureagent-aiPublished by GitHub account ventureagent-aiv0.4.0Updated Oct 27, 2026

Preflight QA for AI-agent deliverables with structured verdicts and repair guidance.

VerifiedStreamable HTTPWeb executableDeveloper ToolsAI & ML

Overview

AI-generated overview

Remote MCP endpoint that runs preflight QA on AI-agent deliverables and returns structured verdicts with repair guidance.

What you can do
  • Run preflight quality checks on deliverables produced by AI agents.
  • Receive structured verdicts on whether a deliverable passes review.
  • Get repair guidance describing what to fix before delivery.
  • No individual tools are documented, so the exact operations are not specified.
When to use it
Useful when an agent produces deliverables that need a pass/fail check and concrete fix suggestions before they are handed off, and you want that review available to the assistant as a tool rather than a manual step.
Requirements
A remote streamable HTTP endpoint; no local package or runtime is needed. OAuth authentication is required, so the user must sign in to the provider's service. No environment variables or headers are declared.
Before you install
The service is hosted by a third party, so deliverables submitted for review are sent to that provider. OAuth grants access to the account on that service. No tool list is published, so what it can read or change cannot be verified in advance.

Installation

In SourceWeft

  1. Open Venture Foundry QA 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/io.github.ventureagent-ai%2Fventure-foundry-qa/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": {
    "venture-foundry-qa": {
      "type": "http",
      "url": "https://venture-foundry-qa.jenvan.chatgpt.site/api/mcp"
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v0.4.0LatestSep 16, 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.