Bestie Check

What Bestie Check does

Bestie Check MCP server prepares a memo, report, or other document for a reasoning check. Its free Quick Look provides a high-level view of the document's claims and the assumptions supporting them. Agents can also access findings and a fix list for checks already associated with the connected Bestie account.

The service is intended for review before handoff. It does not authorize spending merely because a user installs the plugin, signs in, or asks for a document to be checked. Paid checks require the server to report availability, followed by approval of the specific quote, quote hash, and credit ceiling.

How it works

An agent should first call inspect_capabilities and use the availability returned by the service. It can then prepare a document with prepare_deliverable, or upload document bytes through the available file-upload tools. Preparation is asynchronous: the agent polls get_preparation until the response reports nextAction as review, while honoring retry and failure states.

After preparation, the agent should report the returned claims and assumptions without creating findings or a verdict that the service did not provide. For an existing check, authorized account access can be used to read its findings and fix list. Bestie Check MCP server supports either a hosted connection at https://www.hirebestie.com/api/check/mcp or a local stdio MCP process.

Setup and configuration

The local implementation requires Node.js 20 or newer and npm. Authenticate with the CLI, inspect available capabilities, prepare a file, and start the MCP process with commands based on @mybestie/check@0.3.0. Credentials are kept in the CLI's local credential store. As an alternative, a host can receive BESTIE_API_KEY through its private environment; keys should not be committed or placed in prompts.

Hosts that support remote MCP can use the hosted endpoint after signing in to a Bestie account and authorizing the connection. Do not configure hosted and local connections for the same host unless duplicate tools are intended.

The repository also supplies plugin setup for Claude Code, Cursor, and Codex. Claude Code can install the marketplace plugin and invoke /bestie-check:verify; Cursor and Codex should follow their client-specific local-plugin procedures. The optional Claude Code Stop hook can ask whether to offer a check, but it does not approve payment.

Tools and capabilities

• Inspect service availability with inspect_capabilities.
• Prepare a document with prepare_deliverable.
• Upload document bytes through the file-upload tools.
• Poll preparation state with get_preparation.
• Read findings and fix lists for existing checks when the account authorizes access.
• Receive a free Quick Look of claims and assumptions.

Limitations and notes

Paid checks depend on server availability and approval of the exact quote. Agents must respect retry, failure, and review states during preparation. The returned material should be reported as provided; the workflow does not permit inventing findings or a verdict. The repository distributes the plugin, while the hosted Bestie service has separate service terms. Plugin files are MIT licensed, and the repository's fictional review fixture is intended for integration testing.