Home / MCP registry index / io.github.yzlee/opcmenu

独行录 / opcmenu

io.github.yzlee/opcmenu in the official MCP registry. Endpoint https://mcp.opcmenu.com/mcp.

The registry describes it as: Find founders, collaboration opportunities and events; manage authorized signups and messages.

On 2026-10-30 we read its 200 tools, but part of what it advertised was cut before our rules saw it: a description or schema past the size we read, more tools than we read, or a tool list split across pages. Nothing in the part we read matched, but the rest was not checked: this is not a clean result.

Tools it advertises

search_groups search_venues search_products list_products get_product list_creators get_creator get_talent_chips search_all list_activities get_activity get_company list_companies random_feed personalized_feed list_products_discover list_needs_feed get_need search_people search_needs list_posts get_post list_parks get_park list_park_news list_city_policies list_park_city_stats get_product_ratings get_product_rating_summary get_creator_endorsements list_signup_feed get_signup_activity get_activity_agreement list_service_products list_funding list_talent get_organization list_organization_activities preview_organization_invitation list_activity_materials preview_cooperation_share track_event get_my_profile get_my_products get_my_card update_my_profile add_profile_link remove_profile_link set_link_visibility update_my_product follow_creator unfollow_creator list_my_network list_my_conversations start_conversation read_messages send_message mark_conversation_read send_share_card get_contact_exchange_state and 140 more

Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.

Run this server? Show the check in your README

The badge reflects the latest read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-yzlee-opcmenu/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-yzlee-opcmenu)

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. How tool poisoning works. What we found across the registry. Check another server.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.