ArtifactGuard Signed AI Deliverable QA

io.github.blackcow4234-labPublished by GitHub account blackcow4234-labv1.0.0Updated Oct 24, 2026

Signed PASS/WARN/FAIL QA receipts for AI-generated JSON, ZIP, PDF, and DOCX deliverables.

The publisher's own server: Signed

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

A remote MCP server that issues signed PASS/WARN/FAIL QA receipts for AI-generated JSON, ZIP, PDF and DOCX deliverables.

What you can do
Run quality checks on AI-generated deliverables in JSON, ZIP, PDF and DOCX formats and receive a PASS, WARN or FAIL verdict as a signed receipt. The receipt gives a verifiable record of the QA outcome for a deliverable. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Useful when you produce AI-generated files and want an auditable, signed quality verdict attached to each deliverable before handing it on.
Requirements
A remote streamable HTTP endpoint; no local package or runtime is needed. Authentication is required via the Authorization header, which takes a bearer token: your Apify API token.
Before you install
You must supply your Apify API token as a bearer credential in the Authorization header. Deliverables submitted for checking are sent to a third-party Apify-hosted endpoint, so consider whether their contents are sensitive.

Installation

In SourceWeft

  1. Open ArtifactGuard Signed AI Deliverable QA in the dashboard and add it to a workspace.
  2. Connect Authorization token 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.blackcow4234-lab%2Fartifactguard/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.

{
  "mcpServers": {
    "artifactguard-signed-ai-deliverable-qa": {
      "type": "http",
      "url": "https://analytical-gratefulne--artifactguard.apify.actor/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

This repository has no README.

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. v1.0.0LatestSep 16, 2026

Score

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Signed integrations