Handinloop Mcp Server

io.github.lesofiPublished by GitHub account lesofiv0.5.0Updated Nov 4, 2026

Human-in-the-loop document extraction: submit a doc, get validated fields and an audit trail.

VerifiedSTDIODesktop onlyFiles & Storage

Overview

AI-generated overview

Local MCP server for human-in-the-loop document extraction: submit a document and get validated fields plus an audit trail.

What you can do
  • Submit a document for extraction and receive structured, validated fields.
  • Review the human-in-the-loop results and the audit trail behind them.
  • No tool list is published, so the exact operations are not documented; the description centers on document submission, field validation and audit records.
When to use it
Consider it when an assistant needs extracted data from documents that should be checked by a person and traced, rather than fully automated parsing.
Requirements
Runs as a local process on the user's machine, installed from the npm package handinloop-mcp-server over stdio. Desktop only; no authentication, environment variables or headers are declared.
Before you install
Documents submitted for extraction leave the local machine and are processed by the service behind the server; avoid sending confidential material unless that is acceptable. No credentials are declared, so any account or key setup is undocumented. The tool list is unpublished, so review what it can do before installing.

Installation

In SourceWeft

  1. Open Handinloop Mcp Server 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

2
  1. v0.5.0LatestOct 5, 2026
  2. v0.4.0Sep 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.