1lev1

Name: 1lev1
Author: Avi-ADAM

MCP serverMCP

Track partnership work, log mission hours, and see what needs your approval on 1lev1.com.

by Avi-ADAMrepository ↗homepage ↗v1.0.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"1lev1","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability (some checks stopped at authentication)108/108 checks ok

Some successful checks reached the service and some stopped at an authentication response; figures combine both.

when	check	result	http	latency	detail
6 h ago	mcp initialize	ok	200	36 ms	server 1lev1 Platform MCP 1.0.0 · protocol 2025-06-18 · 45 tools
12 h ago	mcp initialize	ok	200	27 ms	server 1lev1 Platform MCP 1.0.0 · protocol 2025-06-18 · 45 tools
19 h ago	mcp initialize	ok	200	26 ms	server 1lev1 Platform MCP 1.0.0 · protocol 2025-06-18 · 45 tools
26 h ago	mcp initialize	ok	200	27 ms	server 1lev1 Platform MCP 1.0.0 · protocol 2025-06-18 · 45 tools
32 h ago	mcp initialize	ok	200	24 ms	server 1lev1 Platform MCP 1.0.0 · protocol 2025-06-18 · 45 tools
2 d ago	mcp initialize	ok	200	28 ms	server 1lev1 Platform MCP 1.0.0 · protocol 2025-06-18 · 45 tools
2 d ago	mcp initialize	ok	200	26 ms	server 1lev1 Platform MCP 1.0.0 · protocol 2025-06-18 · 44 tools
2 d ago	mcp initialize	ok	200	59 ms	server 1lev1 Platform MCP 1.0.0 · protocol 2025-06-18 · 44 tools
2 d ago	mcp initialize	ok	200	31 ms	server 1lev1 Platform MCP 1.0.0 · protocol 2025-06-18 · 44 tools
3 d ago	mcp initialize	ok	200	31 ms	server 1lev1 Platform MCP 1.0.0 · protocol 2025-06-18 · 44 tools

Tools observed via MCP handshake

findUserProjectsTool — Find the projects (rikmot) the current user belongs to, newest first, with their creation time. Use this when the user mentions a project by name, wants to navi
getProjectDetailsTool — Get the facts about one rikma (project): name, public description, values, links (website, GitHub, Drive, social), members, roles, open missions, missions in pr
listProjectResourcesTool — List what a rikma already has and needs: its links (live website, repo, Drive, social), resources in progress (equipment, money, services someone provides) and
getProjectStatsTool — Get the pulse of one rikma as numbers: members, open missions, missions in progress, open resources, open decisions (votes), active timers, missions finished an
getProjectMembersTool — List the people (members) and roles (tafkidim) of a project. Use this to resolve a task assignee - a person or a role - to its ID before calling createTaskTool.
getMemberMissionsTool — List a project member's in-progress missions. A task is linked to a mission-in-progress the assignee performs, so call this after choosing the assignee (a perso
getMissionDetailsTool — Get detailed information about a specific mission including tasks, timeline, and current status Docs: https://1lev1.com/mcp#getMissionDetailsTool
listUserMissionsTool — List user missions with various filtering options Docs: https://1lev1.com/mcp#listUserMissionsTool
findMissionTool — Find a specific mission for the user by its name. Docs: https://1lev1.com/mcp#findMissionTool
getActiveTimersTool — Get all currently active timers for the user Docs: https://1lev1.com/mcp#getActiveTimersTool
getMissionStatsTool — Get statistics about user missions including counts by status, time spent, etc. Docs: https://1lev1.com/mcp#getMissionStatsTool
searchCatalogTool — Search what the platform already offers publicly: products for sale, open missions (work looking for someone) and open resources (equipment, money, services a r
searchContentTool — Search inside the rikmas the caller belongs to: rikma names and descriptions, open missions, missions in progress, acts, open and in-progress resources, and pro
listMyWishesTool — List the caller's own wishes (concierge requests): status, coverage, and how many missions and resources each one still needs. Use it to answer "what did I ask
getWishDetailsTool — Get one wish (concierge request): what it needs broken into missions and resources, its coverage, and the proposals on it. Full detail for the wish owner and fo
listMyWishOffersTool — The supplier side of the concierge: every proposal the caller is the proposer of - what someone asked them to provide and what they offered, with its status. Us
getMyUpdatesTool — What waits for the user and what is new for them - across their rikmas, their wishes (concierge) and their deals. Use it for "what's new today", "what is waitin
proposeRikmaBlueprintTool — Turn a business, an existing partnership or an idea into a draft rikma on 1lev1: the rikma, its PRODUCTS, missions, resources and partners. Use it when someone
getAssistantTool — Read the person's current draft list on 1lev1 - a rikma blueprint (kind 'rikma'), or later their profile or a wish - with its rows, their keys and status, the v
setAssistantItemsTool — Change the draft list with small ops - what the person just told you: keep ("that is right"), drop ("not now", reversible with restore), add, rename, setSpec (p
undoAssistantTool — Undo the last change to the draft list (from here or from the site). Docs: https://1lev1.com/mcp#undoAssistantTool
shareRikmaPreviewTool — Make a read-only link that shows how the drafted rikma would look on 1lev1 - its products, missions, resources, who brings what and an example of how shares for
startAssistantTool — Open the person's living list of (a) their PROFILE - skills, roles, ways of working, values, resources they own - seeded from what is on it now, plus what `text
reviseAssistantTool — Change a list with the person's own words ("that's right, drop the second, add photography") - the platform turns them into ops. Prefer setAssistantItems when y
applyAssistantTool — Save a list: a PROFILE is saved to their profile right away (what they set aside leaves it; resources are only added). A WISH: its own rows are saved - a draft
dismissOfferTool — The person says an open mission suggested to them is not relevant: it stops being suggested to them. A filter for them only - nobody is told no. Docs: https://1
listMyConversationsTool — List the conversations (forums) the caller takes part in - one per mission, act, decision, profit split or wish proposal they are involved in, newest first, wit
readConversationTool — Read one conversation (forum) the caller takes part in: its messages, newest last, with who wrote each. Use it before answering in a thread, so the reply fits w
postConversationMessageTool — Post a message, as the user, in a conversation (forum) they take part in - an update on a mission, an answer in a decision thread, a note on a profit split. The
openRikmaConversationTool — Get the rikma's own general conversation - the one thread that belongs to the whole rikma rather than to a single mission, act or decision. It is created the fi
getSitePagesTool — Get a structured list of available pages on the 1lev1.com site, useful for navigation. Docs: https://1lev1.com/mcp#getSitePagesTool
listRikmaProcessesTool — List a rikma's processes: the open-ended threads it is running - an approach to a partner, a launch, a funding attempt - each with its conversation and the open
navigateToPageTool — Turn a 1lev1.com page into a link to give the user - it does not open anything by itself. Pass the path (e.g. "/lev", or "/moach/<projectId>" with idPr) and a s
createProjectTool — Prepare the "create a Partnership" form (a Partnership is also called a rikma, or "רקמה") and return a link that opens it pre-filled. Nothing is created yet: st
prepareMissionTool — Prepare the mission creation form and return a link that opens it pre-filled. Use this when the user should review and confirm the mission before it is publishe
planProjectWorkTool — Turn a free-text brief into a planning board for a project: proposed missions, chores (acts) and resources, deduplicated against what the project already has. N
createPlanBoardTool — Create a planning board from rows YOU already structured. Use this when the conversation already holds the breakdown - decisions, scope, a task list: your rows
scanProjectDirectionsTool — Cheaply scan a project's real current state and propose a few DIRECTIONS for advancing it - strategic angles, not task lists. Use this when the user asks someth
timerActionTool — Perform actions on user timers (start, stop, pause, resume) Docs: https://1lev1.com/mcp#timerActionTool
proposeProjectLinkTool — Set or clear one of a rikma's links - its website, GitHub repo, Drive, Discord, Facebook, X or WhatsApp. In a rikma with more than one member, changing the webs
startProcessTool — Start a process in a rikma: a named thread with its own conversation, for something that is not yet a mission or a resource - approaching an organisation, prepa
attachToProcessTool — Attach an existing object - an open mission, an open resource, a mission in progress, or a mission/resource still being voted on - to a process, so what the rik
createTaskTool — Create a task (Act, "מטלה") in a project - the way a member gets something new done. Whenever the user wants something new to happen in a project, offer this op
getPlatformInfo — Get general information about the 1lev1 platform, its goals, and features. Docs: https://1lev1.com/mcp#getPlatformInfo
prepareSignup — Prepare a 1lev1 signup for a person who has NO 1lev1 account yet, so joining is one screen - the agreement prefilled with their name, email and countries, and t

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

kind Official MCP Registry

name Official MCP Registry

repoUrl Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

homepageUrl Official MCP Registry

publisherName Official MCP Registry

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registryio.github.Avi-ADAM/1lev1

first seen 1 mo ago · fetched 7 h agoopen ↗

Field history (7 recent events)

1 mo ago · declared · summary → "Track partnership work, log mission hours, and see what needs your approval on 1lev1.com."
1 mo ago · declared · description → "Track partnership work, log mission hours, and see what needs your approval on 1lev1.com."
1 mo ago · declared · publisherName → "Avi-ADAM"
1 mo ago · declared · homepageUrl → "https://1lev1.com"
1 mo ago · declared · repoUrl → "https://github.com/Avi-ADAM/1lev1-mcp"
1 mo ago · declared · version → "1.0.0"
1 mo ago · declared · protocols → ["mcp"]

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from