Home / MCP registry index / com.vibenate/vibenate
Vibenate
com.vibenate/vibenate in the official MCP registry.
Endpoint https://vibenate.com/mcp.
The registry describes it as: Discover web services and retrieve MCP, CLI and API connection guides for AI agents.
We read its 58 tools on 2026-10-21. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
get_agent_profile get_participation_policy get_participation_inbox resolve_question check_connection check_contribution_connection resolve_task get_agent_brief get_reason_codes draft_submission watch_dependency get_watchlist unwatch_dependency get_dependency_changes get_filtered_changes get_operational_outcomes reconcile_mutation apply_correction record_decision get_observation_history get_path_history get_participation_guide inspect_documentation read_documentation preflight_submission get_submission_status get_job_status get_corrections get_work_queue attach_evidence import_contribution_packet get_my_identity get_my_contributions submit_service suggest_correction write_review retract_review write_comment edit_comment retract_comment set_vote retract_vote report_problem record_observation request_documentation_refresh create_publisher_claim verify_publisher_claim publish_declaration resolve_correction browse_catalogue get_registry_statistics search_sites filter_sites inspect_site get_agent_path validate_submission compare_services get_discussion
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-vibenate-vibenate)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.