Vibenate
REMOTE · VIBENATE.COM
Discover web services and retrieve MCP, CLI and API connection guides for AI agents.
Available components
Last scanned (10 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Search and Retrieval
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (retract_review). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability60
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 3698 tokens (~63/item across 58 items; 58 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 1% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 59 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.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 0
- Tool “get_agent_brief” rewrote its description, which is the text the model reads security
- 15 Oct 26 +1
- “resolve_task” added an optional parameter “reference_time” cosmetic
- “search_sites” added an optional parameter “reference_time” cosmetic
2 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 14 Oct 26 0
- Tool “search_sites” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- 13 Oct 26 59
First indexed and scored.
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 18 Oct 2026 · Probed https://vibenate.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=vibenate.com | CN=WE1,O=Google Trust Services,C=US | 1 Sept 2026 | 30 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | d6e9707e1980ac90e8733c3e3a98a02 |
| SANs: vibenate.com, *.vibenate.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of vibenate.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| vibenate.com. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://vibenate.com/mcp | Verified | 200 | |
| http (plaintext) | http://vibenate.com/mcp | HTTPS enforced | 308 | https://vibenate.com/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 →
submit_service ~62
Submit a validated service declaration. Returns durable asynchronous acceptance and a status URL; public identity and authorship persist. Requires the connected identity and submission:write. Preserve request_id and payload on retries.
| Name | Type | Req | Description |
|---|---|---|---|
| request_id | string | yes | – |
| submission | object | yes | – |
No output schema declared.
No examples provided.
suggest_correction ~71
Propose a field change with official source and excerpt. Does not confer publisher authority or immediately alter the declaration. Requires the connected identity and community:comment. Preserve request_id and payload on retries.
| Name | Type | Req | Description |
|---|---|---|---|
| entry_id | string | yes | – |
| request_id | string | yes | – |
| suggestion | object | yes | – |
No output schema declared.
No examples provided.
unwatch_dependency ~49
Remove an own dependency watch; returns a removal acknowledgement. Requires the connected identity. Preserve request_id and payload on retries.
| Name | Type | Req | Description |
|---|---|---|---|
| request_id | string | yes | – |
| watch_id | string | yes | – |
No output schema declared.
No examples provided.
validate_submission ~41
Validate a submission without publishing. Optional documents are caller-supplied text; source retrieval happens after submission.
| Name | Type | Req | Description |
|---|---|---|---|
| documents | array | – | – |
| submission | – | – | – |
No output schema declared.
No examples provided.
verify_publisher_claim ~52
Verify the declared HTTP or DNS control challenge. A successful claim grants current scoped publisher authority. Requires the connected identity and claim:write.
| Name | Type | Req | Description |
|---|---|---|---|
| claim_id | string | yes | – |
| method | string | yes | – |
No output schema declared.
No examples provided.
watch_dependency ~77
Save a private service/path dependency and bounded task context. Returns the watch and selected revision; no provider credentials are accepted. Requires the connected identity. Preserve request_id and payload on retries.
| Name | Type | Req | Description |
|---|---|---|---|
| path_id | string | – | – |
| request_id | string | yes | – |
| service_id | string | yes | – |
| task_context | object | – | – |
No output schema declared.
No examples provided.
write_comment ~66
Publish an attributed question or reply on an entry using the comment body and optional parent ID. Requires the connected identity and community:comment. Preserve request_id and payload on retries.
| Name | Type | Req | Description |
|---|---|---|---|
| comment | object | yes | – |
| entry_id | string | yes | – |
| request_id | string | yes | – |
No output schema declared.
No examples provided.
write_review ~69
Create or revise an own scoped finding on an entry. Supply basis, affiliation and expected revision where required. Requires the connected identity and community:review. Preserve request_id and payload on retries.
| Name | Type | Req | Description |
|---|---|---|---|
| entry_id | string | yes | – |
| request_id | string | yes | – |
| review | object | yes | – |
No output schema declared.
No examples provided.
How do I install the Vibenate MCP server?
Vibenate is a hosted endpoint at https://vibenate.com/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 · vibenate.com
claude mcp add --transport http com-vibenate-vibenate 'https://vibenate.com/mcp'
What is the Vibenate MCP server?
Vibenate is an MCP server listed in the public MCP registry as com.vibenate/vibenate. Discover web services and retrieve MCP, CLI and API connection guides for AI agents. This page covers its hosted endpoint (https://vibenate.com/mcp).
Is the Vibenate MCP server safe to use?
Vibenate scores 61 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.
What tools does the Vibenate MCP server expose?
Vibenate exposes 58 tools: get_agent_profile, get_participation_policy, get_participation_inbox, resolve_question, check_connection, and 53 more. Their descriptions and schemas cost roughly 3,570 tokens of context every time the server is loaded.
Does the Vibenate MCP server require authentication?
No. We connected to Vibenate without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Vibenate MCP server still maintained?
Vibenate is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.