Numguard

io.github.ipezygjPublished by GitHub account ipezygjv0.1.1Updated Oct 27, 2026

Verify a number before an agent asserts it — evals, backtests (Deflated Sharpe), signed receipts.

VerifiedSTDIODesktop onlyData & AnalyticsAI & ML

Overview

AI-generated overview

Numguard is a local MCP server that checks a number before an agent states it, covering evals, backtests with Deflated Sharpe, and signed receipts.

What you can do
  • Verify a numeric claim before an assistant asserts it.
  • Run evaluation checks on reported figures.
  • Assess backtest results, including a Deflated Sharpe measure.
  • Produce signed receipts for the verification outcome.
  • No tool list is published, so exact operations are not documented.
When to use it
Worth adding when an assistant reports metrics, evaluation scores or backtest performance and you want those numbers checked rather than taken at face value, especially where a signed record of the check matters.
Requirements
Runs as a local process on the user's machine, installed from the numguard package on PyPI and started with Python. Desktop only; no web execution. No authentication, environment variables or headers are declared.
Before you install
The server is described as producing signed receipts, but no details on key handling or where data goes are published; confirm how signing keys are managed before relying on it. It is a local desktop-only process with no published tool list, so review its behavior before use.

Installation

In SourceWeft

  1. Open Numguard 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.