Home / MCP registry index / io.github.Avi-ADAM/1lev1
1lev1
io.github.Avi-ADAM/1lev1 in the official MCP registry.
Endpoint https://api.1lev1.com/api/mcp. Source: github.com/Avi-ADAM/1lev1-mcp.
The registry describes it as: Track partnership work, log mission hours, and see what needs your approval on 1lev1.com.
We read its 60 tools on 2026-10-26. 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
findUserProjectsTool getProjectDetailsTool listProjectResourcesTool getProjectStatsTool getProjectMembersTool getMemberMissionsTool getMissionDetailsTool listUserMissionsTool findMissionTool getActiveTimersTool getMissionStatsTool searchCatalogTool searchContentTool listMyWishesTool getWishDetailsTool listMyWishOffersTool getMyUpdatesTool proposeRikmaBlueprintTool getAssistantTool setAssistantItemsTool undoAssistantTool shareRikmaPreviewTool prepareForSomeoneElseTool startAssistantTool reviseAssistantTool applyAssistantTool dismissOfferTool listMyConversationsTool readConversationTool postConversationMessageTool openRikmaConversationTool getSitePagesTool listRikmaProcessesTool navigateToPageTool createProjectTool prepareMissionTool planProjectWorkTool createPlanBoardTool scanProjectDirectionsTool timerActionTool proposeProjectLinkTool startProcessTool attachToProcessTool createTaskTool listRikmaProductsTool getRikmaProductTool getShopInventoryTool listRikmaProductOptionsTool listRikmaProductVariantsTool listRikmaOrdersTool getRikmaOrderTool getShippingConfigTool quoteShippingTool createRikmaProductTool updateRikmaProductTool archiveRikmaProductTool setShopStockTool updateRikmaOrderStatusTool getPlatformInfo prepareSignup
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-avi-adam-1lev1)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.