Bestie Check

io.github.HireBestiev0.3.0Updated Oct 2, 2026

Document reasoning checks: a helicopter view of claims and assumptions before handoff.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowKnowledge & Memory

Overview

AI-generated overview

Prepares a memo or report for a reasoning check, returning its claims and assumptions for review.

What it does
Bestie Check takes a document such as a memo or report and prepares it for a reasoning check, giving a helicopter view of the claims it makes and the assumptions behind them. Agents can inspect capabilities, prepare a deliverable or upload its bytes, poll preparation status until it is ready for review, and report the returned claims and assumptions. For checks already in a connected account, agents can read findings and a fix list. A free Quick Look tier is described alongside paid checks.
When to use it
Useful when an assistant drafts or reviews deliverables and you want its claims and hidden assumptions surfaced before handoff. It fits workflows where a document is prepared, polled, and then reported back without inventing findings or a verdict.
Requirements
Either the hosted remote endpoint with OAuth sign-in to a Bestie account, or the local stdio package run with npx, which needs Node.js 20 or newer and npm. The CLI login stores credentials locally; alternatively a BESTIE_API_KEY can be set in the host's private environment. Paid checks require server availability and approval of a specific quote.
Before you install
Paid checks cost money and require approval of the actual quote, its hash, and a credit ceiling; installing, signing in, or saying check this does not approve spending. Credentials such as BESTIE_API_KEY must never be committed or placed in a prompt. Configuring both the hosted and local connections duplicates the tools.

Installation

In SourceWeft

  1. Open Bestie Check in the dashboard and add it to a workspace.
  2. 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.

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "bestie-check": {
      "type": "http",
      "url": "https://www.hirebestie.com/api/check/mcp"
    }
  }
}

README

Bestie Check

See your document from above: every claim, and every assumption it rests on.

Bestie Check prepares a memo, report, or other document for a reasoning check. The free Quick Look gives you a helicopter view of its claims and assumptions. Agents can also read findings and a fix list from checks in the connected account. Paid checks require server availability and approval of a specific quote.

This repository contains the public plugin distribution. The Node CLI and stdio MCP implementation are bundled in @mybestie/check. Plugin version 1.2.0 uses CLI version 0.3.0, published on npm.

Connect

Hosted MCP with OAuth

For hosts that accept a remote MCP server, connect to:

text
https://www.hirebestie.com/api/check/mcp

Sign in to your Bestie account and authorize the connection. Use the hosted connection or the local stdio connection for each host. Configuring both duplicates the tools.

CLI and local MCP

Requires Node.js 20 or newer and npm.

sh
npx -y @mybestie/[email protected] loginnpx -y @mybestie/[email protected] capabilitiesnpx -y @mybestie/[email protected] prepare --file memo.pdf --wait --progressnpx -y @mybestie/[email protected] mcp

The plugin's local MCP process pins @mybestie/[email protected]. Sign in through the CLI first; credentials stay in the CLI's local credential store. You may instead configure BESTIE_API_KEY in your host's private environment. Never commit a key or include one in a prompt.

Claude Code

text
/plugin marketplace add HireBestie/bestie-check/plugin install bestie-check@bestie

Use /bestie-check:verify to prepare a document. The optional Stop hook asks whether to offer Check; it never approves spending.

Cursor and Codex

The root plugin.json, mcp.json, and skills/ form a portable Agent Plugin. .codex-plugin/plugin.json provides Codex compatibility metadata. .cursor/mcp.json and .cursor/rules/bestie-check.mdc provide a Cursor configuration and rule for manual setup. Follow your client's local-plugin setup instructions.

Public directory acceptance is separate from this repository. This repository does not imply a listing in the Claude, OpenAI, or Cursor directories.

Agent skill

sh
bunx skills add HireBestie/bestie-check --skill verify-deliverable

Expected journey

  1. Call inspect_capabilities and use the returned availability.
  2. Prepare the document with prepare_deliverable, or upload its bytes with the file-upload tools.
  3. Poll get_preparation until the returned nextAction is review; respect retry and failure states.
  4. Report the returned claims and assumptions without inventing findings or a verdict.
  5. For an existing check, read its findings and fix list using the account's authorized access.

Paid tools are offered only when the server reports them ready. An agent must obtain approval for the actual quote, its hash, and a credit ceiling. Installing a plugin, signing in, or saying "check this" does not approve spending.

Links

The fixture under review-fixtures/ is fictional and may be used for integration testing. Review-account credentials are supplied privately through submission portals; they are never part of this repository.

License

The plugin files in this repository are MIT licensed. Bestie's hosted service is governed by its own service terms. See LICENSE.

Source: README.md at commit 62ad5db

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v0.3.0LatestOct 2, 2026