Divinci AI

ai.divinciPublished by divinci.aiv1.0.0Updated Oct 24, 2026

Release management and QA for custom AI assistants: RAG, releases, scored QA, signed TrustBench runs

VerifiedStreamable HTTPWeb executableDeveloper ToolsAI & ML

Overview

AI-generated overview

Remote MCP endpoint for Divinci AI that lets an assistant manage releases and QA for custom AI assistants, including RAG, scored QA and signed TrustBench runs.

What you can do
  • Manage releases of custom AI assistants, including publishing and versioning.
  • Work with RAG content that backs those assistants.
  • Run scored QA evaluations against assistant behavior.
  • Produce signed TrustBench runs as evidence of testing.
  • No tool list is published, so exact operations are not documented.
When to use it
Useful when you build or operate custom AI assistants on Divinci AI and want an assistant to help with release management, retrieval content, and scored QA or TrustBench evaluation runs.
Requirements
Remote streamable HTTP endpoint at mcp.divinci.app; OAuth authentication is required. No environment variables or headers are declared. A Divinci AI account with access to the relevant assistants is implied.
Before you install
OAuth grants the server access to your Divinci AI account. Release and QA operations may change or publish assistant configurations and evaluation results, so review actions before confirming. No tool list is published, so scope of access cannot be verified in advance.

Installation

In SourceWeft

  1. Open Divinci AI 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.divinci%2Fdivinci/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": {
    "divinci-ai": {
      "type": "http",
      "url": "https://mcp.divinci.app/mcp"
    }
  }
}

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 29, 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.