Daishi Studio

ai.daishiPublished by daishi.aiOfficial publisherv1.0.0Updated Oct 24, 2026

Run AI agent evaluations on your own model keys, and publish runs others can review and re-run.

VerifiedStreamable HTTPWeb executableAI & ML

Overview

AI-generated overview

Remote MCP server for running AI agent evaluations on your own model keys and publishing runs others can review and re-run.

What you can do
  • Run AI agent evaluations using your own model API keys.
  • Publish evaluation runs so other people can review them.
  • Let others re-run published evaluations.
  • No tool list is published, so the exact operations available are not documented in the supplied material.
When to use it
Useful when you want an assistant to set up, run and share evaluations of AI agents, and when you need results that teammates or outside reviewers can inspect and reproduce.
Requirements
A remote streamable HTTP endpoint at daishi.ai; no local package or environment variables are declared. OAuth authentication is required. Your own model provider keys are needed to run evaluations.
Before you install
You supply your own model API keys, which may incur usage costs on those providers. Published runs are shared with others for review and re-running, so check what prompts, outputs and data a run exposes before publishing. The available tools are not listed, so verify permissions after connecting.

Installation

In SourceWeft

  1. Open Daishi Studio 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/ai.daishi%2Fstudio/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": {
    "daishi-studio": {
      "type": "http",
      "url": "https://daishi.ai/mcp/studio"
    }
  }
}

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.0.0LatestSep 30, 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 Daishi integrations