run.onvibe/onvibe
REMOTE · ONVIBE.RUN · SCANNED SEP 21
Talk to Claude and get a live web app deployed to a real URL, with Postgres, storage and cron.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 723 tokens (~723/item across 0 items; 0 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Nothing to assess: this server has no tools to check for usage examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Unverified: 2 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the run.onvibe/onvibe MCP server?
run.onvibe/onvibe is a hosted endpoint at https://onvibe.run/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · onvibe.run
claude mcp add --transport http run-onvibe-onvibe 'https://onvibe.run/mcp'
{
"mcpServers": {
"run-onvibe-onvibe": {
"url": "https://onvibe.run/mcp"
}
}
} {
"servers": {
"run-onvibe-onvibe": {
"type": "http",
"url": "https://onvibe.run/mcp"
}
}
} [mcp_servers.run-onvibe-onvibe] url = "https://onvibe.run/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"run-onvibe-onvibe": {
"type": "remote",
"url": "https://onvibe.run/mcp",
"enabled": true
}
}
} openclaw mcp add run-onvibe-onvibe --url 'https://onvibe.run/mcp' --transport streamable-http
mcp_servers:
run-onvibe-onvibe:
url: "https://onvibe.run/mcp" {
"McpServers": {
"run-onvibe-onvibe": {
"Transport": "http",
"Url": "https://onvibe.run/mcp"
}
}
} assistant mcp add run-onvibe-onvibe -t streamable-http -u 'https://onvibe.run/mcp'
{
"mcpServers": {
"run-onvibe-onvibe": {
"type": "http",
"url": "https://onvibe.run/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 21 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 20 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 19 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 18 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 17 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 16 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 15 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 14 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
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 21 Sept 2026 · Probed https://onvibe.run/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=onvibe.run | CN=YE1,O=Let's Encrypt,C=US | 14 Aug 2026 | 12 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 54903eaa63287db25bd35db85fb1619a65d |
| SANs: onvibe.run | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of onvibe.run. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| run. | present | 37315 | 8 | Verified |
| onvibe.run. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src https://fonts.gstatic.com; img-src 'self' data: https://storage.onvibe.run https://assets.onvibe.run https://images.onvibe.run https://*.google-analytics.com https://www.googletagmanager.com https://googleads.g.doubleclick.net https://www.google.com; script-src 'self' https://www.googletagmanager.com https://www.googleadservices.com https://googleads.g.doubleclick.net 'sha256-8AU9qUU2+ZLmgOmOXiazh6dEz5ChZW1yEI0whlBb66Y='; connect-src 'self' https://www.googletagmanager.com https://*.google-analytics.com https://*.analytics.google.com https://googleads.g.doubleclick.net https://www.google.com; frame-src 'self' https://td.doubleclick.net https://www.googletagmanager.com; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://onvibe.run/mcp | Verified | 200 | |
| http (plaintext) | http://onvibe.run/mcp | HTTPS enforced | 301 | https://onvibe.run/mcp |
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 →
No tool schema has been captured from this endpoint yet.
What is the run.onvibe/onvibe MCP server?
run.onvibe/onvibe is an MCP server listed in the public MCP registry as run.onvibe/onvibe. Talk to Claude and get a live web app deployed to a real URL, with Postgres, storage and cron. This page covers its hosted endpoint (https://onvibe.run/mcp).
Is the run.onvibe/onvibe MCP server safe to use?
run.onvibe/onvibe scores 62 out of 100 on VerifyMCP. 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.
Does the run.onvibe/onvibe MCP server require authentication?
No. We connected to run.onvibe/onvibe without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the run.onvibe/onvibe MCP server still maintained?
run.onvibe/onvibe is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.