Productivity · Remote MCP server
ArtifactGuard Signed AI Deliverable QA
Signed PASS/WARN/FAIL QA receipts for AI-generated JSON, ZIP, PDF, and DOCX deliverables.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.blackcow4234-lab/artifactguard- Version
- 1.0.0
- Status
- Active
- Category
- productivity
- Transport
- Streamable HTTP
- Published
- 2026-08-06
- Updated
- 2026-08-06
- Publisher
- blackcow4234-lab (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/blackcow4234-lab) · how
- Listed under
- PDF MCP servers
- Website
- github.com/blackcow4234-lab/blackcow4234
- Repository
- github.com/blackcow4234-lab/blackcow4234
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://analytical-gratefulne--artifactguard.apify.actor/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401
- Checked on
- 2026-10-05
How to connect ArtifactGuard Signed AI Deliverable QA
ArtifactGuard Signed AI Deliverable QA is a remote MCP server: there is nothing to install. Its endpoint is https://analytical-gratefulne--artifactguard.apify.actor/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More productivity servers
| Server | Runs |
|---|---|
| Arkova VerificationPrivacy-first document verification anchored to the public ledger. | Remote · HTTPLive check: sign-in required |
| ArkrelTurn documents into verified, structured data: fields, tables, and automatic checks. | Remote · HTTPLive check: sign-in required |
| ArmbrainAI memory layer for fractional CMOs -- client-partitioned minds, meeting prep, and EOS. | Remote · HTTPLive check: sign-in required |
| Arne Kellmann ConsultingRead consulting services and search public architecture consulting documents in English or German. | Remote · HTTPLive check: ✓ handshake |
| ArtifactsSave decisions, plans, and notes from any AI session and retrieve them later - from any client. Ask. | Remote · SSELive check: ✗ no handshake |
| AsanaManage tasks, projects, portfolios, and team workflows. | Local · stdio |
| Asana MCP ServerChange Asana without opening Asana - custom fields, sections, start dates, rich notes, bulk. PAT. | Local · stdio |
| asap.coolDrive ASAP: French invoicing, contacts and e-signature from any MCP client (NF203-compliant). | Remote · HTTPLive check: sign-in required |