Handinloop Mcp Server

io.github.handinloopPublished by GitHub account handinloopv0.9.1Updated Oct 29, 2026

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

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Handinloop MCP server lets an assistant submit documents for human-in-the-loop extraction and receive validated fields with an audit trail.

What you can do
  • Submit documents for extraction and receive the resulting fields.
  • Get validated field values produced through human review.
  • Retrieve an audit trail for submitted extractions.
  • Connect either to the hosted remote endpoint or run the npm package locally over stdio.
When to use it
Useful when document data must be extracted accurately and reviewed by people rather than trusted blindly, and when you need a record of how each field was validated.
Requirements
A Handinloop account. Authentication is required: OAuth sign-in, or an API key sent as a Bearer token in the Authorization header. Either the hosted remote endpoint or the local npm package with Node.js.
Before you install
The server handles submitted documents and the data extracted from them, which are sent to a third-party service. The Authorization header carries a secret API key; keep it out of logs and shared configuration. Extraction results are human-validated but should still be checked before being used in downstream actions.

Installation

In SourceWeft

  1. Open Handinloop Mcp Server 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/io.github.handinloop%2Fhandinloop-mcp-server/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": {
    "handinloop": {
      "type": "http",
      "url": "https://mcp.sg.handinloop.com/mcp"
    }
  }
}

README

This repository has no README.

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. v0.9.1LatestOct 29, 2026

Score

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.