Veridict

io.github.xkumakichiPublished by GitHub account xkumakichiv0.1.1Updated Oct 28, 2026

Know if you can trust your MCP server. Trust judgment for AI agents.

VerifiedSTDIODesktop onlySecurity & MonitoringAI & ML

Overview

AI-generated overview

Veridict is a local MCP server that gives an AI assistant a way to judge whether another MCP server can be trusted.

What you can do
  • Provides trust judgment for MCP servers, so an assistant can assess whether a given server is trustworthy.
  • Aims to help agents decide how much to rely on the tools and data a connected MCP server offers.
  • No tool list, instructions or README were supplied, so the exact operations and outputs are not documented here.
When to use it
Consider it when an assistant connects to third-party MCP servers and you want a trust assessment before relying on them. Because its behavior is undocumented in the supplied material, verify what it actually does before depending on it.
Requirements
Runs as a local process over stdio, installed from the npm package veridict, so a Node.js runtime is needed. No authentication, environment variables or headers are declared.
Before you install
The server's purpose is judging trust, yet no tool list, instructions or README are available, so its criteria, data sources and outputs cannot be checked. Review the package before installing, and note that any assessment it produces is only as reliable as its undisclosed method.

Installation

In SourceWeft

  1. Open Veridict in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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.