A Model Context Protocol (MCP) server for interacting with Microsoft 365 and Office services through the Graph API
1lev1 is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Track partnership work, log mission hours, and see what needs your approval on 1lev1.com.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http 1lev1-mcp https://api.1lev1.com/api/mcp
# 2 — ask your agent for something these tools do
# findUserProjectsTool, getProjectDetailsTool, listProjectResourcesTool and 43 more
1lev1 costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http 1lev1-mcp https://api.1lev1.com/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
46 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 navigate to one, or just created one. Results are paginated: when hasMore is true, call again with offset=nextOffset. Docs: https://1lev1.com/mcp#findUserProjectsTool
| Parameter | Type | Required | Notes |
|---|---|---|---|
| userId | string | no | User id to list projects for. Omit to use the authenticated caller. |
| query | string | no | Optional search query to filter projects by name (case-insensitive substring). |
| limit | integer | no | Page size, default 50. |
| offset | integer | no | How many results to skip, default 0. |
Get the facts about one rikma (project): name, public description, values, links (website, GitHub, Drive, social), members, roles, open missions, missions in progress (and who holds them), open and in-progress resources, and products. Call this before planning or writing anything in a rikma - it is cheap and returns facts, unlike scanProjectDirectionsTool. For a rikma the user is not a member of,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | Rikma (project) id, from findUserProjectsTool. |
List what a rikma already has and needs: its links (live website, repo, Drive, social), resources in progress (equipment, money, services someone provides) and open resources it is looking for, plus its products. Use it to check whether a rikma already has a website/repo before suggesting one. Members only. Docs: https://1lev1.com/mcp#listProjectResourcesTool
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | Rikma (project) id, from findUserProjectsTool. |
Get the pulse of one rikma as numbers: members, open missions, missions in progress, open resources, open decisions (votes), active timers, missions finished and hours logged in the last N days, and when anything last happened. Use it to judge whether a rikma is active before planning. Members only; no per-member financial data. Docs: https://1lev1.com/mcp#getProjectStatsTool
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | Rikma (project) id, from findUserProjectsTool. |
| days | integer | no | Window for the "recent" numbers, default 30. |
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. For a task with no specific person, pick the roles that fit it here and pass their IDs as tafkidims. Docs: https://1lev1.com/mcp#getProjectMembersTool
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | ID of the project |
| query | string | no | Optional text to filter people or roles by name |
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 person) to pick the missionId to pass to createTaskTool. If no mission in progress covers the work, it is not a task: prepare a mission with prepareMissionTool instead. Docs: https://1lev1.com/mcp#getMemberMissionsTool
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | ID of the project |
| userId | string | yes | ID of the member (assignee) whose in-progress missions to list |
Get detailed information about a specific mission including tasks, timeline, and current status Docs: https://1lev1.com/mcp#getMissionDetailsTool
| Parameter | Type | Required | Notes |
|---|---|---|---|
| missionId | string | yes | Mission ID to get details for |
List user missions with various filtering options Docs: https://1lev1.com/mcp#listUserMissionsTool
| Parameter | Type | Required | Notes |
|---|---|---|---|
| filter | string | no | Filter missions by status |
| projectId | string | no | Filter by specific project ID (numeric) |
| projectName | string | no | Filter by project name |
| missionName | string | no | Search for missions by name (partial match) |
| limit | number | no | Maximum number of missions to return |
Find a specific mission for the user by its name. Docs: https://1lev1.com/mcp#findMissionTool
| Parameter | Type | Required | Notes |
|---|---|---|---|
| missionName | string | yes | The name of the mission to find. |
Get all currently active timers for the user Docs: https://1lev1.com/mcp#getActiveTimersTool
| Parameter | Type | Required | Notes |
|---|---|---|---|
| includeDetails | boolean | no | Include detailed timer information |
Get statistics about user missions including counts by status, time spent, etc. Docs: https://1lev1.com/mcp#getMissionStatsTool
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | no | Get stats for specific project only |
Search what the platform already offers publicly: products for sale, open missions (work looking for someone) and open resources (equipment, money, services a rikma needs). Use it before opening a new wish or mission - somebody may already do this. Public data only. Docs: https://1lev1.com/mcp#searchCatalogTool
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Free text; matched against names, descriptions and rikma names. |
| kinds | array | no | Which directories to search. Default: all three. |
| limit | integer | no | Maximum rows per kind, default 10. |
Search inside the rikmas the caller belongs to: rikma names and descriptions, open missions, missions in progress, acts, open and in-progress resources, and products. Use it to find something when the rikma is not known - "where was that task about the logo". For public listings of other rikmas use searchCatalogTool instead. Docs: https://1lev1.com/mcp#searchContentTool
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Free text; matched against names and descriptions. |
| limit | integer | no | Maximum rows per kind, default 10. |
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 for" and to pick the wish a follow-up is about. Docs: https://1lev1.com/mcp#listMyWishesTool
No parameter schema on file.
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 for anyone who proposed on it; others see only the public card of an open wish. Accepting or declining a proposal is never done here - open the returned URL and let the person decide. Docs: https://1lev1.com/mcp#getWishDetailsTool
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wishId | string | yes | Wish (ratson) id, from listMyWishes or a /concierge or /wish URL. |
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. Use it to answer "who wants something from me". Responding to one happens on its page, not here. Docs: https://1lev1.com/mcp#listMyWishOffersTool
No parameter schema on file.
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 waiting for me", "what do I need to answer", "what is happening in rikma X". Returns waiting: each item is ONE ready sentence in the user's language, with its figures, where it is, its deadline (when silenceApproves is true, no answer by the
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | no | Only this rikma (its id, e.g. from findUserProjectsTool). |
| rikma | string | no | Only rikmas whose name contains this text - use when the user names a rikma and you have no id. |
| lang | string | no | The language to word the sentences in. Default: the user's language. |
| limit | integer | no | How many waiting items at most (default 20). |
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 wants to add their business so the concierge can find and order from them, to see how their partnership would look on 1lev1, or to break an idea down and recruit partners. Build it yourself from the site you read or from the conversation: -
| Parameter | Type | Required | Notes |
|---|---|---|---|
| fields | object | yes | — |
| products | array | no | — |
| missions | array | no | — |
| resources | array | no | — |
| partners | array | no | — |
| projectId | string | no | An existing rikma of the caller to import into (from findUserProjectsTool). |
| sourceText | string | no | The site text or conversation summary this was drawn from. |
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 version, and what was changed recently (also from the site). Call it before setAssistantItems when you are not sure you have the latest version. Docs: https://1lev1.com/mcp#getAssistantTool
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kind | string | no | Latest session of this kind. |
| sessionId | string | no | — |
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 (price, keywords, hours…), link (a product recipe), setField (the rikma name, description…). Refer to rows only by their key. Rows already created on the platform, or a wish row a supplier answered, cannot be changed here - you get reason "cr
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sessionId | string | yes | — |
| expectedVersion | integer | yes | — |
| ops | array | yes | — |
| instruction | string | no | The person's words, for the shared transcript. |
| say | string | no | Your one-line summary of the change, for the transcript. |
Undo the last change to the draft list (from here or from the site). Docs: https://1lev1.com/mcp#undoAssistantTool
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sessionId | string | yes | — |
| expectedVersion | integer | yes | — |
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 form - for the person to send to their partners (no account needed to view; nothing is created). Valid 30 days; calling again replaces the old link, and revoke:true ends it. Docs: https://1lev1.com/mcp#shareRikmaPreviewTool
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sessionId | string | yes | — |
| revoke | boolean | no | — |
Prepare a rikma on 1lev1 for ANOTHER person - not the user you are talking to - and get one link to give them: for example the user markets 1lev1 and sets up a new customer's business, or helps another member get started. NEVER use it for the user themselves; for their own business, partnership or idea use proposeRikmaBlueprint. If it is not clear who the rikma is for, ask before calling. Pass tha
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | The name the person gave you to sign up with. |
| string | yes | The email the person gave you to sign up with - the confirmation goes there. | |
| countries | array | no | Country names in English, e.g. ["Israel"]. |
| lang | string | no | — |
| intent | string | yes | — |
| aboutText | string | no | — |
| wishText | string | no | — |
| blueprint | object | no | — |
| forSomeoneElse | boolean | yes | Confirms the rikma is for another person, not the user you are talking to. |
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 says about them (pass what they told you); or (b) a WISH - pass ratsonId (from listMyWishesTool), or text to start a new draft wish from their words. Returns the rows with keys. Then refine with setAssistantItems (your own ops - preferr
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kind | string | yes | — |
| text | string | no | — |
| ratsonId | string | no | — |
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 you can name the ops yourself; this one runs a model. Docs: https://1lev1.com/mcp#reviseAssistantTool
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sessionId | string | yes | — |
| expectedVersion | integer | yes | — |
| instruction | string | yes | — |
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 stays a draft (publishing is theirs, on the site: siteUrl), and rows a supplier already answered are never changed here. A RIKMA is never created here - you get the reviewUrl to give them. Docs: https://1lev1.com/mcp#applyAssistantTool
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sessionId | string | yes | — |
| expectedVersion | integer | yes | — |
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://1lev1.com/mcp#dismissOfferTool
| Parameter | Type | Required | Notes |
|---|---|---|---|
| openMissionId | string | yes | — |
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, with the last message. Use it to find the forumId of the thread a request is about. Docs: https://1lev1.com/mcp#listMyConversationsTool
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | no | Only conversations of this rikma. |
| limit | integer | no | Maximum rows, default 25. |
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 what was already said. Docs: https://1lev1.com/mcp#readConversationTool
| Parameter | Type | Required | Notes |
|---|---|---|---|
| forumId | string | yes | Forum id, from listMyConversations. |
| limit | integer | no | How many of the most recent messages, default 30. |
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 other participants are notified. Use it ONLY when the user asked to say or record something; never to think out loud, and never to agree or refuse on their behalf (approving a decision, a split or a proposal is always their own click). The
| Parameter | Type | Required | Notes |
|---|---|---|---|
| forumId | string | yes | Forum id, from listMyConversations. |
| message | string | yes | The message, in the user's own words and language. Plain text. |
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 first time someone opens it. Use it for "what are we doing next" talk; anything about a specific mission, decision or profit split belongs in that thing's own thread, where it stays on record. Returns a forumId for readConversation and postCo
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | Rikma (project) id. |
Get a structured list of available pages on the 1lev1.com site, useful for navigation. Docs: https://1lev1.com/mcp#getSitePagesTool
No parameter schema on file.
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 missions, resources and other objects that have formed out of it. Use it to see what is already in motion before starting something new. Members only. Docs: https://1lev1.com/mcp#listRikmaProcessesTool
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | Rikma (project) id. |
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 short name for it; the result carries the path to put after https://1lev1.com. getSitePagesTool lists the valid paths. Docs: https://1lev1.com/mcp#navigateToPageTool
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | The URL path to navigate to. |
| pageName | string | yes | A descriptive name for the page being navigated to. |
| idPr | string | no | The ID of the project to navigate to, if applicable. |
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: status is "prepared" until the user opens the link and approves the form. Give the user url exactly as returned — do not decode, shorten or rebuild it. A public-benefit or nonprofit initiative is a normal Partnership, not a failed business:
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | The name of the new Partnership. Required. |
| desc | string | no | A short public description (plain text, one or two sentences). |
| details | string | no | Detailed description as raw HTML, e.g. <h2>Title</h2><p>Body</p>. Allowed tags: h1, h2, h3, p, ul, ol, li, strong, em, u, s, a, br, blockquote. Do NOT HTML-escape it (send <p>, not <p>). |
| url | string | no | A link to a website related to the project. |
| vals | array | no | Values and goals of the partnership, as their names. A value may contain commas. |
| res | string | no | Response time ID: feh (48h), sth (72h), nsh (96h), sevend (1 week). |
| profit | string | no | When the Partnership expects to earn from sales: already, week, month, threeM, sixM, oneY, twoY, more, or never. never is the correct value for a nonprofit / public-benefit initiative - it means "se |
| ont | boolean | no | Whether the partnership is continuous (true) or a one-time event (false). |
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 published. A mission is for work that needs an implementer to be found. If a mission in progress already covers the work, create a task (act) on it with createTaskTool instead. Check the rikma's open missions (getProjectDetailsTool) first: when one
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | ID of the project where the mission will be created. |
| name | string | yes | Mission name (required). |
| descrip | string | no | Mission description as rich HTML - strongly preferred over plain text; a partner decides whether to join from this. Allowed tags: h1, h3, p, ul, ol, li, strong, em, a, br. Recommended shape: a short i |
| skills | array | no | Skill names, free text in the user's language. Matched to the platform catalogue; a skill that does not exist yet is created. Up to 8. |
| roles | array | no | Role names, free text. Matched to the catalogue; created when missing. Up to 8. |
| workways | array | no | Work-mode names (how the work is done, e.g. "remote", "on-site"), free text. Matched to the catalogue; created when missing. Up to 8. |
| nhours | number | no | Estimated hours. |
| valph | number | no | Value per hour. |
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. Nothing is created - the tool returns a reviewUrl where the user approves each row in the real form. Use this when the user describes something they want the project to achieve in loose words. If the conversation already holds a concrete bre
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | ID of the project to plan for. |
| text | string | yes | What the user wants to advance, in their own words. At least 20 characters - the richer the brief, the better the breakdown. |
| title | string | no | Optional title for the board; otherwise one is suggested. |
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 are saved as written, with no second model rewriting or dropping them. Nothing is created - every row is a proposal the user approves in the real creation form at the returned reviewUrl. Every row needs a name AND a descrip; rows without on
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | ID of the project to plan for. |
| title | string | yes | Board title - the direction these rows advance. |
| descrip | string | no | One or two plain-text sentences on what this board is for. |
| items | array | yes | The rows, in the order the user should see them. 1 to 40. |
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 something open-ended like "what should we do next?" or "how do we move this forward?" and has not described a specific goal. These are saved as suggested directions only: nothing is created, and no mission, chore or resource comes out of this cal
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | ID of the project to scan. |
Perform actions on user timers (start, stop, pause, resume) Docs: https://1lev1.com/mcp#timerActionTool
| Parameter | Type | Required | Notes |
|---|---|---|---|
| action | string | yes | The action to perform on the timer |
| missionId | string | no | Specific mission ID (optional, will find active timer if not provided) |
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 website or the Facebook link opens a decision the members vote on (silence approves it when the rikma clock runs out); the other links change directly. Members only. Check listProjectResourcesTool first - the link may already be there. Docs: ht
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | Rikma (project) id. |
| kind | string | yes | Which link to set. |
| url | string | yes | The URL. Pass an empty string to clear the link. |
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, preparing a launch, chasing funding. The description becomes the first message, so a half-formed idea can be written in plain words and take shape later: as it becomes concrete, the open missions and resources it needs are created in the normal
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | Rikma (project) id. |
| name | string | yes | Short name, e.g. "Approach: city community centre". |
| description | string | no | The raw text, in the user's own words: what this is, who it involves, what is hoped for. |
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 rikma is pursuing and what it is actually doing about it stay connected. It does not create the object: create it first (prepareMissionTool, createTaskTool, or the URL the tool returns), then attach it. Docs: https://1lev1.com/mcp#attachToProc
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | Rikma (project) id. |
| processId | string | yes | Process id, from listRikmaProcesses or startProcess. |
| entityType | string | yes | What kind of object is being attached. |
| entityId | string | yes | Id of that object. |
| name | string | no | Its name, for the process timeline. |
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 option. Choose the shape: - A mission in progress already covers the work: create an act linked to it - assignedUserId = the mission holder, missionId from getMemberMissionsTool. - Nobody in the project does this kind of work, so an implement
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | ID of the project where the task will be created |
| name | string | yes | Short name/title of the task |
| description | string | no | What has to be done and what done looks like, as plain text. Strongly recommended - a title alone is hard to act on. |
| link | string | no | Optional URL related to the task |
| assignedUserId | string | no | ID of the person (project member) to assign this task to - usually the holder of the mission it belongs to. Use getProjectMembersTool to resolve a name to an ID. Mutually exclusive with tafkidims. |
| tafkidims | array | no | IDs of the roles (tafkidim) that fit the task, when no specific person is chosen; a holder of one of them picks it up. Use getProjectMembersTool to resolve role names to IDs. Mutually exclusive with a |
| missionId | string | no | ID of the mission in progress (mesimabetahaliches) this task belongs to, from getMemberMissionsTool. Goes with assignedUserId. |
| hashivut | string | no | Urgency level of the task |
| dateS | string | no | Start date (ISO format) |
| dateF | string | no | End date (ISO format) |
Get general information about the 1lev1 platform, its goals, and features. Docs: https://1lev1.com/mcp#getPlatformInfo
No parameter schema on file.
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 the password on the same screen. Use it only when the person's own request is what 1lev1 does: finding partners for their work, turning a business or an idea into a partnership where the work, resources and money each partner brings become a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | The name the person gave you to sign up with. |
| string | yes | The email the person gave you to sign up with - the confirmation goes there. | |
| countries | array | no | Country names in English, e.g. ["Israel"]. |
| lang | string | no | — |
| intent | string | yes | — |
| aboutText | string | no | — |
| wishText | string | no | — |
| blueprint | object | no | — |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install 1lev1 or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish 1lev1 can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.