Bestie Check
NPM · @MYBESTIE/CHECK · 2 COMPONENTS
Document reasoning checks: a helicopter view of claims and assumptions before handoff.
Available components
Last scanned (7 hours ago)
Scores higher than 62% of npm servers
Category Documents and Files
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1320 tokens (~73/item across 18 items; 18 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 56% of tool parameters carry a description.Partial
- Structured output schemas are declared (28% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +6
- Stability: unverified → 0.40 ▲ functional
- 13 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 12 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 3 Oct 26 +15
- Malware scan: unverified → pass ▲ security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 23 Oct 2026 · Analysed npm/@mybestie/check@0.3.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
confirm_file_upload Confirm a file upload ~52
Confirm that bytes were PUT to the signed upload URL, then start ingestion (the Quick Look follows automatically). Returns preparation state. Poll get_preparation; do not block.
| Name | Type | Req | Description |
|---|---|---|---|
| uploadHandleId | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| acceptedMediaTypes | array | – | – |
| artifactRef | string | – | – |
| checkId | string | – | – |
| expiresAt | string | – | – |
| ingestion | object | yes | – |
| kind | string | yes | – |
| nextAction | – | yes | – |
| partial | boolean | yes | – |
| quickLook | object | – | – |
| requiredHeaders | object | – | – |
| retryable | boolean | yes | – |
| uploadHandleId | string | yes | – |
| uploadUrl | string | – | – |
| warnings | array | yes | – |
No examples provided.
create_ruling Record a ruling on a finding ~96
Record a human or agent ruling (accept_concern / reject_concern / defer) on a finding or an entire run. Never re-interprets the finding — records a disposition.
| Name | Type | Req | Description |
|---|---|---|---|
| checkId | string | yes | Durable Check run identity. |
| evidenceLocators | array | yes | – |
| findingId | string | yes | – |
| outcome | string | yes | – |
| rationale | string | – | – |
| scope | string | yes | – |
No output schema declared.
No examples provided.
delete_check Delete a Check run ~61
Permanently delete a Check run and its custody artifacts. Irreversible; denies every subsequent route for this checkId on every surface.
| Name | Type | Req | Description |
|---|---|---|---|
| checkId | string | yes | Durable Check run identity. Deletion is irreversible and denies every subsequent route for this checkId. |
No output schema declared.
No examples provided.
export_check Export a Check run ~42
Export a terminal Check run as json, sarif, or pdf_summary.
| Name | Type | Req | Description |
|---|---|---|---|
| checkId | string | yes | Durable Check run identity. |
| format | string | yes | – |
No output schema declared.
No examples provided.
get_artifacts Read Check artifacts ~33
Read committed backing artifacts for a Check run by checkId.
| Name | Type | Req | Description |
|---|---|---|---|
| checkId | string | yes | Durable Check run identity. |
No output schema declared.
No examples provided.
get_check Read a Check run ~35
Read the current status and scorecard for a Check run by checkId.
| Name | Type | Req | Description |
|---|---|---|---|
| checkId | string | yes | Durable Check run identity. |
No output schema declared.
No examples provided.
get_diff Compare a repair with its parent ~44
Compare a repair/rerun's findings against its parent: cleared, persisted, and new findings.
| Name | Type | Req | Description |
|---|---|---|---|
| checkId | string | yes | Child Check run to diff against its parent. |
No output schema declared.
No examples provided.
get_findings Read Check findings ~61
Read findings for a Check run by checkId. Returns locators and disposition summaries on claims, assumptions, warrants, evidence, and rebuttals — not document excerpts.
| Name | Type | Req | Description |
|---|---|---|---|
| checkId | string | yes | Durable Check run identity returned by verify_deliverable. |
No output schema declared.
No examples provided.
get_fix_list Read what to change ~82
Read what to change in the document for a finished Check run, as a short list and a ready-to-use revision prompt. Same list the Bestie workspace shows. Use it after get_findings when you are going to revise the document, then check the revised document again.
| Name | Type | Req | Description |
|---|---|---|---|
| checkId | string | yes | Durable Check run identity returned by verify_deliverable. |
No output schema declared.
No examples provided.
get_lineage Read Check lineage ~38
Read the full rerun/repair lineage tree for a Check run.
| Name | Type | Req | Description |
|---|---|---|---|
| checkId | string | yes | Any Check run in the lineage chain. |
No output schema declared.
No examples provided.
get_preparation Read preparation and Quick Look ~113
Read-only preparation snapshot for an uploadHandleId: ingestion state, the Quick Look operation (progress, claim and assumption counts and previews, graph identity, failed units), partial, warnings, retryable and nextAction. Never starts or retries anything. Poll while nextAction is wait; claim previews appear as work units finish. nextAction review means the Quick Look is done; retry means retry_preparation is available; replace_source means ingestion failed and the source must be prepared again.
| Name | Type | Req | Description |
|---|---|---|---|
| uploadHandleId | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| acceptedMediaTypes | array | – | – |
| artifactRef | string | – | – |
| checkId | string | – | – |
| expiresAt | string | – | – |
| ingestion | object | yes | – |
| kind | string | yes | – |
| nextAction | – | yes | – |
| partial | boolean | yes | – |
| quickLook | object | – | – |
| requiredHeaders | object | – | – |
| retryable | boolean | yes | – |
| uploadHandleId | string | yes | – |
| uploadUrl | string | – | – |
| warnings | array | yes | – |
No examples provided.
get_receipt Read a Check receipt ~55
Read the execution receipt for a terminal Check run by checkId. Records what argument-structure criteria were tested and what was explicitly not engaged.
| Name | Type | Req | Description |
|---|---|---|---|
| checkId | string | yes | Durable Check run identity returned by verify_deliverable. |
No output schema declared.
No examples provided.
get_tasks Read Check progress ~39
Read execution progress (started/completed/failed phases) for a Check run by checkId.
| Name | Type | Req | Description |
|---|---|---|---|
| checkId | string | yes | Durable Check run identity. |
No output schema declared.
No examples provided.
inspect_capabilities Inspect Check capabilities ~69
Read what this Check deployment can do for the caller right now: input formats that are ready (and why others are not), the routed verification profile, presets with the pack stack the server resolves for you, admitted packs, and whether paid execution is available through this client. Call first. Read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
inspect_packs List admitted verifier packs ~80
List admitted verifier packs available to the caller. Packs test mechanism-bearing claims — assumptions, warrants, evidence, and rebuttals — not grammar or generic style. Use to choose packRefs before quote_check and verify_deliverable. There is no list_packs tool. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Optional substring filter over pack display names. |
No output schema declared.
No examples provided.
prepare_deliverable Prepare a deliverable (text or URL) ~108
Put pasted text or a public HTTPS URL into Check custody. Ingestion starts, and the server then runs the Claim and Assumption Quick Look automatically. Returns uploadHandleId and preparation state immediately. Do not wait on this call; poll get_preparation. Never send local file bytes through this tool.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | – | Pasted source text. Mutually exclusive with url. |
| url | string | – | Public HTTPS URL. Mutually exclusive with text. Not a local file. |
| Name | Type | Req | Description |
|---|---|---|---|
| acceptedMediaTypes | array | – | – |
| artifactRef | string | – | – |
| checkId | string | – | – |
| expiresAt | string | – | – |
| ingestion | object | yes | – |
| kind | string | yes | – |
| nextAction | – | yes | – |
| partial | boolean | yes | – |
| quickLook | object | – | – |
| requiredHeaders | object | – | – |
| retryable | boolean | yes | – |
| uploadHandleId | string | yes | – |
| uploadUrl | string | – | – |
| warnings | array | yes | – |
No examples provided.
prepare_file_upload Start a file upload ~98
Create a file-kind Check upload handle and return a signed PUT descriptor including uploadUrl and requiredHeaders. PUT bytes directly to uploadUrl with those headers. Do not send file contents through MCP. After the PUT, call confirm_file_upload.
| Name | Type | Req | Description |
|---|---|---|---|
| byteLength | integer | yes | – |
| filename | string | yes | – |
| mediaType | string | yes | – |
| sha256 | string | yes | SHA-256 of the exact bytes that will be PUT. |
| Name | Type | Req | Description |
|---|---|---|---|
| acceptedMediaTypes | array | – | – |
| artifactRef | string | – | – |
| checkId | string | – | – |
| expiresAt | string | – | – |
| ingestion | object | yes | – |
| kind | string | yes | – |
| nextAction | – | yes | – |
| partial | boolean | yes | – |
| quickLook | object | – | – |
| requiredHeaders | object | – | – |
| retryable | boolean | yes | – |
| uploadHandleId | string | yes | – |
| uploadUrl | string | – | – |
| warnings | array | yes | – |
No examples provided.
retry_preparation Retry a failed Quick Look ~70
Explicit write: re-queue the Quick Look for an upload whose last attempt ended incomplete or failed (or completed with failed units), or start it if ingestion is ready and none exists. Refused otherwise. Never call it to poll; use get_preparation.
| Name | Type | Req | Description |
|---|---|---|---|
| uploadHandleId | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| acceptedMediaTypes | array | – | – |
| artifactRef | string | – | – |
| checkId | string | – | – |
| expiresAt | string | – | – |
| ingestion | object | yes | – |
| kind | string | yes | – |
| nextAction | – | yes | – |
| partial | boolean | yes | – |
| quickLook | object | – | – |
| requiredHeaders | object | – | – |
| retryable | boolean | yes | – |
| uploadHandleId | string | yes | – |
| uploadUrl | string | – | – |
| warnings | array | yes | – |
No examples provided.
How do I install the Bestie Check MCP server?
Bestie Check runs locally as an npm package, launched with npx -y @mybestie/check. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @mybestie/check
claude mcp add hirebestie-bestie-check -- npx -y @mybestie/check
What is the Bestie Check MCP server?
Bestie Check is an MCP server listed in the public MCP registry as io.github.HireBestie/bestie-check. Document reasoning checks: a helicopter view of claims and assumptions before handoff. This page covers its npm package (@mybestie/check).
Is the Bestie Check MCP server safe to use?
Bestie Check scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 October 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Bestie Check MCP server expose?
Bestie Check exposes 18 tools: inspect_capabilities, inspect_packs, prepare_deliverable, prepare_file_upload, confirm_file_upload, and 13 more. Their descriptions and schemas cost roughly 1,176 tokens of context every time the server is loaded.
Is the Bestie Check MCP server still maintained?
Bestie Check is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Bestie Check MCP server under?
Bestie Check declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.