Other · Remote MCP server
SomaCheck Vibecheck
SomaCheck returns proposition-specific Aligned or Unaligned plus model confidence.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.Sensie-agents/vibecheck- Version
- 0.6.18
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-09-15
- Updated
- 2026-09-15
- Publisher
- Sensie-agents (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/Sensie-agents) · how
- Website
- somacheck.com/docs/hosted-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.somacheck.com/functions/v1/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @somacheck/vibecheck | 0.6.18 | stdio |
How to connect SomaCheck Vibecheck
SomaCheck Vibecheck is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.somacheck.com/functions/v1/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: @somacheck/vibecheck version 0.6.18. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @somacheck/vibecheck@0.6.18.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"vibecheck": {
"command": "npx",
"args": [
"-y",
"@somacheck/vibecheck@0.6.18"
]
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| Soljo Solar (Switzerland)Independent rooftop solar first estimate for Switzerland: yield, median cost, subsidy, with sources. | Remote · HTTPLive check: ✓ handshake |
| Solucortex MCPLiving technical memory for AI agents: recall approved project context, record what was learned. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| Solvegate MCPInspect a page for Cloudflare Turnstile free, and clear Turnstile and WAF challenges. | Local · stdio |
| SolvScoreCredit scores for AI agents. Underwrite an unknown counterparty before extending credit. | Remote · HTTPLive check: ✓ handshake |
| Sonarqube MCPSonarQube MCP - projects, metrics, quality gate, issues, worst-metric ranking. | Local · stdio |
| SonasAI-powered candidate profiles for foreign professionals in Spain and Europe. | Remote · HTTPLive check: sign-in required |
| sonenta.comMCP server for Sonenta translation management: keys, translations, a11y, and source-health tools. | Local · stdio |
| Sonicake Pocket MasterControl a Sonicake Pocket Master guitar processor over USB MIDI: amps, effects and presets. | Local · stdio |