SomaCheck Vibecheck
NPM · @SOMACHECK/VIBECHECK · 2 COMPONENTS · SCANNED SEP 25
SomaCheck returns proposition-specific Aligned or Unaligned plus model confidence.
Available components
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 Security98
- 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
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- 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 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
- Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 83% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% 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 7 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
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.
npm · @somacheck/vibecheck
claude mcp add sensie-agents-vibecheck -- npx -y @somacheck/vibecheck
{
"mcpServers": {
"sensie-agents-vibecheck": {
"command": "npx",
"args": [
"-y",
"@somacheck/vibecheck"
]
}
}
} {
"servers": {
"sensie-agents-vibecheck": {
"command": "npx",
"args": [
"-y",
"@somacheck/vibecheck"
]
}
}
} codex mcp add sensie-agents-vibecheck -- npx -y @somacheck/vibecheck
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sensie-agents-vibecheck": {
"type": "local",
"command": [
"npx",
"-y",
"@somacheck/vibecheck"
],
"enabled": true
}
}
} openclaw mcp add sensie-agents-vibecheck --command npx --arg -y --arg @somacheck/vibecheck
mcp_servers:
sensie-agents-vibecheck:
command: "npx"
args: ["-y", "@somacheck/vibecheck"] {
"McpServers": {
"sensie-agents-vibecheck": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@somacheck/vibecheck"
]
}
}
} assistant mcp add sensie-agents-vibecheck -t stdio -c npx -a -y @somacheck/vibecheck
{
"mcpServers": {
"sensie-agents-vibecheck": {
"command": "npx",
"args": [
"-y",
"@somacheck/vibecheck"
]
}
}
} 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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +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.
- 22 Sept 26 +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.
- 19 Sept 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.
- 17 Sept 26 +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.
- 16 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 15 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- Stability: 0.40 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 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 functional
- 14 Sept 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 25 Sept 2026 · Analysed npm/@somacheck/vibecheck@0.6.18
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 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| 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 →
get_vibecheck_context Vibecheck Context ~34
Read recent completed check-ins for this linked agent, newest first. Replenish the feed when status requests it.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| checkins | array | yes | – |
No examples provided.
get_vibecheck_result Get Vibecheck Result ~118
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.
| Name | Type | Req | Description |
|---|---|---|---|
| request_id | string | yes | The opaque request_id returned by post_vibecheck_statement or request_vibecheck. |
| Name | Type | Req | Description |
|---|---|---|---|
| confidence | – | yes | – |
| delivery_state | – | – | – |
| error_code | – | – | – |
| latency_s | – | yes | – |
| request_id | string | yes | – |
| status | string | yes | – |
| user_feedback | – | – | – |
| verdict | – | yes | – |
No examples provided.
get_vibecheck_status Vibecheck Status ~50
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| cadence | object | yes | – |
| first_run_intro | object | yes | – |
| has_pending_request | boolean | yes | – |
| linked | boolean | yes | – |
| no_prior_requests | boolean | yes | – |
| pending_proposition_count | integer | yes | – |
| prior_request_count | integer | yes | – |
| propositions_needed | integer | yes | – |
| queued_proposition_count | integer | yes | – |
| recommended_action | string | yes | – |
| replenishment_requested_at | string|null | yes | – |
No examples provided.
post_vibecheck_statement Post Vibecheck Statement ~151
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.
| Name | Type | Req | Description |
|---|---|---|---|
| statements | array | yes | Distinct personalized statements for this person to test, ordered most useful first. |
| Name | Type | Req | Description |
|---|---|---|---|
| propositions | array | yes | – |
No examples provided.
request_vibecheck Request a Vibecheck ~355
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.
| Name | Type | Req | Description |
|---|---|---|---|
| consent_basis | string | yes | 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 | yes | 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 | yes | 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… |
| Name | Type | Req | Description |
|---|---|---|---|
| confidence | – | yes | – |
| continuation_transport | – | – | – |
| cooldown_until | – | yes | – |
| delivery_state | – | yes | – |
| error_code | – | yes | – |
| expires_at | – | yes | – |
| idempotent_replay | boolean|null | yes | – |
| request_id | string|null | yes | – |
| state | string | yes | – |
| user_feedback | – | – | – |
| verdict | – | yes | – |
No examples provided.
share_somacheck_context Share SomaCheck Context ~59
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.
| Name | Type | Req | Description |
|---|---|---|---|
| observations | array | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| accepted | boolean | yes | – |
| observation_count | integer | yes | – |
| state | string | yes | – |
No examples provided.
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.