DeAI Artifact Gateway

io.github.jake-zaibaPublished by GitHub account jake-zaibav0.5.5Updated Nov 7, 2026

Verified-artifact library: match, ask, run fixture programs, reuse sealed pages (HTTP 402 toll).

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

Remote MCP endpoint for a verified-artifact library, letting an assistant match artifacts, ask questions, run fixture programs and reuse sealed pages.

What you can do
  • Match artifacts in a verified-artifact library
  • Ask questions against the library
  • Run fixture programs
  • Reuse sealed pages, with an HTTP 402 toll mentioned for that use
When to use it
Worth considering when you want an assistant to work with a curated library of verified artifacts and sealed pages rather than general web search. The listing gives no tool list, instructions or README, so evaluate it directly before relying on it.
Requirements
A remote streamable HTTP endpoint at the provider's host; no packages, environment variables, headers or authentication are declared.
Before you install
The description mentions an HTTP 402 toll, which suggests some operations may require payment; confirm pricing and what is charged before use. No authentication is declared, so consider what data you send to the third-party host.

Installation

In SourceWeft

  1. Open DeAI Artifact Gateway in the dashboard and add it to a workspace.
  2. 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.jake-zaiba%2Fdeai-research/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": {
    "deai-artifact-gateway": {
      "type": "http",
      "url": "https://research.zaiba.cloud/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

11
  1. v0.5.5LatestNov 7, 2026
  2. v0.5.3Nov 6, 2026
  3. v0.5.2Nov 5, 2026
  4. v0.5.1Nov 3, 2026
  5. v0.4.0Nov 3, 2026
  6. v0.3.2Oct 29, 2026
  7. v0.2.4Oct 24, 2026
  8. v0.2.3Oct 21, 2026
  9. v0.2.2Oct 20, 2026
  10. v0.2.1Oct 13, 2026
  11. v0.2.0Oct 13, 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 listedRequired15 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.