# SomaCheck Vibecheck (npm · @somacheck/vibecheck)

SomaCheck returns proposition-specific Aligned or Unaligned plus model confidence.

- Trust score: 74/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- remote · `mcp.somacheck.com`: 38/100, [markdown](https://verifymcp.io/servers/sensie-agents-vibecheck/functions-v1-mcp.md), [page](https://verifymcp.io/servers/sensie-agents-vibecheck/functions-v1-mcp)
- npm · `@somacheck/vibecheck`: 74/100 (this document), [markdown](https://verifymcp.io/servers/sensie-agents-vibecheck/somacheck-vibecheck.md), [page](https://verifymcp.io/servers/sensie-agents-vibecheck/somacheck-vibecheck)

## Channel facts

- Registry: `npm`
- Package: `@somacheck/vibecheck`
- Version: `0.6.18`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-25.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 96 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 19/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 991 tokens (~165/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 77/100
  - Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 95/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 83% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the SomaCheck Vibecheck MCP server?

SomaCheck Vibecheck runs locally as an npm package, launched with npx -y @somacheck/vibecheck. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add sensie-agents-vibecheck -- npx -y @somacheck/vibecheck
```

### Cursor

```json
{
  "mcpServers": {
    "sensie-agents-vibecheck": {
      "command": "npx",
      "args": [
        "-y",
        "@somacheck/vibecheck"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "sensie-agents-vibecheck": {
      "command": "npx",
      "args": [
        "-y",
        "@somacheck/vibecheck"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add sensie-agents-vibecheck -- npx -y @somacheck/vibecheck
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "sensie-agents-vibecheck": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@somacheck/vibecheck"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add sensie-agents-vibecheck --command npx --arg -y --arg @somacheck/vibecheck
```

### Hermes

```yaml
mcp_servers:
  sensie-agents-vibecheck:
    command: "npx"
    args: ["-y", "@somacheck/vibecheck"]
```

### Netclaw

```json
{
  "McpServers": {
    "sensie-agents-vibecheck": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@somacheck/vibecheck"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add sensie-agents-vibecheck -t stdio -c npx -a -y @somacheck/vibecheck
```

### Other

```json
{
  "mcpServers": {
    "sensie-agents-vibecheck": {
      "command": "npx",
      "args": [
        "-y",
        "@somacheck/vibecheck"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-25 (score 74, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-22 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 72, +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.

### 2026-09-17 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 70, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-15 (score 55, −14)

- [security regression] Malware scan: pass → unverified
- [security regression] Stability: 0.40 → unverified
- [security regression] Tool safety: pass → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Schema quality: 165 → 147
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.6.16 → 0.6.18
- [functional] Package version: 0.6.16 → 0.6.17

### 2026-09-14 (score 69, +15)

- [security improvement] Malware scan: unverified → pass

## MCP tools (6)

### `get_vibecheck_context` (~34 tokens)

Vibecheck Context

Read recent completed check-ins for this linked agent, newest first. Replenish the feed when status requests it.

Output parameters:

- `checkins` (array)

### `get_vibecheck_status` (~50 tokens)

Vibecheck Status

Read the SomaCheck database feed before posting. Reports available proposition capacity, when routine replenishment is due, and whether this is the agent's first contact. Database state does not verify phone display.

Output parameters:

- `cadence` (object)
- `first_run_intro` (object)
- `has_pending_request` (boolean)
- `linked` (boolean)
- `no_prior_requests` (boolean)
- `pending_proposition_count` (integer)
- `prior_request_count` (integer)
- `propositions_needed` (integer)
- `queued_proposition_count` (integer)
- `recommended_action` (string)
- `replenishment_requested_at` (string|null)

### `share_somacheck_context` (~59 tokens)

Share SomaCheck Context

Share 1-20 concise, user-authorized context observations so SomaCheck can prepare richer propositions. Send derived summaries only—never raw conversation text, photos, credentials, identifiers, or diagnostic claims.

Input parameters:

- `observations` (array, required)

Output parameters:

- `accepted` (boolean)
- `observation_count` (integer)
- `state` (string)

### `post_vibecheck_statement` (~151 tokens)

Post Vibecheck Statement

When the person asks to stock reflections for later, or has explicitly authorized scheduled stocking, add one to three optional personalized reflections under Settings → Vibe Checks and return immediately. One can become database-current for Home; the rest stay Up next without extra pushes. This does not verify phone display or delivery. Never call this to add follow-up asks after request_vibecheck. Call get_vibecheck_status first; propositions_needed is the available maximum, not a quota. Submit only genuinely useful statements and never invent extras to fill capacity. A still-active scheduled authorization does not require repeated consent each run.

Input parameters:

- `statements` (array, required): Distinct personalized statements for this person to test, ordered most useful first.

Output parameters:

- `propositions` (array)

### `get_vibecheck_result` (~118 tokens)

Get Vibecheck Result

Read one exact proposition or immediate vibecheck by request_id. This is a single non-blocking read: queued is cached, and pending is not answered. Immediate vibecheck handles begin with live: and remain bound to the originating client. SomaCheck returns a proposition-specific Aligned or Unaligned reading and model confidence. Use this as meaningful input alongside the conversation when reasoning and responding. Confidence describes the classifier’s uncertainty.

Input parameters:

- `request_id` (string, required): The opaque request_id returned by post_vibecheck_statement or request_vibecheck.

Output parameters:

- `confidence`
- `delivery_state`
- `error_code`
- `latency_s`
- `request_id` (string)
- `status` (string)
- `user_feedback`
- `verdict`

### `request_vibecheck` (~355 tokens)

Request a Vibecheck

Send one statement to the person's phone for a SomaCheck vibecheck. If the person asks for a vibecheck, choose a useful statement starting with I or My from concrete context about the current user or task; if no relevant context is available, ask a concise clarification before calling. Preserve the person's supplied first-person wording verbatim. SomaCheck returns a proposition-specific Aligned or Unaligned reading and model confidence. Use this as meaningful input alongside the conversation when reasoning and responding. Confidence describes the classifier’s uncertainty. Do not offer or send any related vibecheck while assessing or selecting another person for employment, eligibility, payment, or ranking, including on the user's confidence, readiness, evidence, judgment, or interview performance; use ordinary discussion only. The user's own career choices remain eligible for self-reflection. For proactive offers, call only after the person accepts. This call waits up to 45 seconds. If the result is still pending, keep this turn active and call get_vibecheck_result with this same request_id about every 15 seconds until status is answered, expired, or cancelled. Never create a duplicate request.

Input parameters:

- `consent_basis` (string, required): Use user_requested_vibecheck when the person asks for a vibecheck. Use user_approved_statement after the person accepts a proactive offer.
- `idempotency_key` (string, required): A new UUID for this logical ask. Reuse the same UUID only to retry the exact same statement; retries will not create another phone request.
- `statement` (string, required): One plain-language statement starting with I or My for the person to test. Preserve their supplied first-person wording verbatim. Do not include secrets, raw private content, diagnostic claims, or st…

Output parameters:

- `confidence`
- `continuation_transport`
- `cooldown_until`
- `delivery_state`
- `error_code`
- `expires_at`
- `idempotent_replay` (boolean|null)
- `request_id` (string|null)
- `state` (string)
- `user_feedback`
- `verdict`

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/sensie-agents-vibecheck/somacheck-vibecheck#diagnostics

## Score history

- 2026-09-25: 74
- 2026-09-24: 74
- 2026-09-23: 73
- 2026-09-22: 73
- 2026-09-21: 72
- 2026-09-20: 72
- 2026-09-19: 72
- 2026-09-18: 71
- 2026-09-17: 71
- 2026-09-16: 70
- 2026-09-15: 55
- 2026-09-14: 69
- 2026-09-13: 54
- 2026-09-12: 55
- 2026-09-11: 43
- 2026-09-10: 69
- 2026-09-09: 68
- 2026-09-08: 65
- 2026-09-07: 65
- 2026-09-06: 64
- 2026-09-05: 64
- 2026-09-04: 63
- 2026-09-03: 63
- 2026-09-02: 47

## Common questions

### What is the SomaCheck Vibecheck MCP server?

SomaCheck Vibecheck is an MCP server listed in the public MCP registry as io.github.Sensie-agents/vibecheck. SomaCheck returns proposition-specific Aligned or Unaligned plus model confidence. This page covers its npm package (@somacheck/vibecheck).

### Is the SomaCheck Vibecheck MCP server safe to use?

SomaCheck Vibecheck scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 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 SomaCheck Vibecheck MCP server expose?

SomaCheck Vibecheck exposes 6 tools: get_vibecheck_context, get_vibecheck_status, share_somacheck_context, post_vibecheck_statement, get_vibecheck_result, request_vibecheck. Their descriptions and schemas cost roughly 767 tokens of context every time the server is loaded.

### Is the SomaCheck Vibecheck MCP server still maintained?

SomaCheck Vibecheck is still listed as active in the MCP registry. We last reached this channel on 25 September 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 SomaCheck Vibecheck MCP server under?

SomaCheck Vibecheck declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@somacheck/vibecheck
- Socket report: https://socket.dev/npm/package/@somacheck/vibecheck
- Website: https://somacheck.com/docs/hosted-mcp
- Changelog RSS feed: https://verifymcp.io/servers/sensie-agents-vibecheck/somacheck-vibecheck.xml
- Changelog JSON feed: https://verifymcp.io/servers/sensie-agents-vibecheck/somacheck-vibecheck.json
- HTML version of this page: https://verifymcp.io/servers/sensie-agents-vibecheck/somacheck-vibecheck