io.github.plastrlab/skyelight-mcp

None of its 18 tools are described as changing anything. For 18 the reading was uncertain, so no mark is shown.

• list_workspaceson 44 other servers

  “Workspaces you can reach, with the role you hold in each, and who you are.”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  Takes no inputs.

• list_projectson 157 other servers

  “Projects you can reach, newest activity first, across every workspace unless one is named.”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  1 input

  • workspaceIdstring“Narrow to one workspace.”
• list_itemson 11 other servers

  “List feedback items (bugs, ideas, comments) people left on a Skyelight project.”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  7 inputs

  • projectIdstring“Project to read.”
  • pagestring“Only items on one page, e.g.”
  • typestring“Item type, e.g.”
  • statusstring“Defaults to everything.”
  • assigneestring“A user id, "me" for whoever this connection belongs to, or "none" for unassigned items.”
  • taskstring“Only items a person handed to an agent with this task (Hand off in the app), or "none" for items with no hand-off.”
  • limitnumber“Max items (default 50).”
• search_itemson 17 other servers

  “Find items whose thread mentions some text.”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  4 inputs, 1 required

  • querystringrequired“Text to look for.”
  • projectIdstring“Project to search.”
  • statusstring
  • limitnumber
• post_update

  “Report back on an item: what you found, what you changed, a link to the PR.”

  Publisher declares: read-only no · destructive no · idempotent no · open-world no

  4 inputs, 2 required

  • itemIdstringrequired“Item id from list_items.”
  • bodystringrequired“What you found or changed, in plain language for the person who reported it.”
  • mentionsarray“People to notify, by name, email or id from list_members ("me" is you).”
  • linksarray“Optional links — a PR, a commit, a deploy.”
• create_itemon 2 other servers

  “Open a new thread on a page, as the person whose connection you are using.”

  Publisher declares: read-only no · destructive no · idempotent no · open-world no

  7 inputs, 2 required

  • urlstringrequired“Full URL of the page this is about.”
  • bodystringrequired“What you want to say.”
  • selectorstring“CSS selector for the element, if there is one.”
  • projectIdstring“Optional if a project is bound.”
  • pageTitlestring
  • mentionsarray“People to notify, by name, email or id from list_members ("me" is you).”
  • assigneestring“Who should take it: a name, email or id from list_members, or "me".”
• publish_review_link

  “Share something with Skyelight for review, and get a link people can pin feedback on.”

  Publisher declares: read-only no · destructive no · idempotent no · open-world yes

  8 inputs

  • codestring“For Skyelight to host: the complete file, never a summary or an excerpt.”
  • urlstring“Where the app is deployed, e.g.”
  • namestring“What it is, in a few words.”
  • kindstring“With code; worked out from it when left out.”
  • projectIdstring“Optional: the project to put it in.”
  • prototypeIdstring“With code: to publish a new version of a prototype published before.”
  • workspaceIdstring“When you are in more than one workspace and give no project, from list_workspaces.”
  • sourcestring“With code: where it was made, shown as its logo in Skyelight: "claude", "claude-code", "openai" (ChatGPT), "cursor", "windsurf", "v0", "lovable" or "other".”
• list_memberson 26 other servers

  “The people in a workspace: name, email, role and id.”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  2 inputs

  • projectIdstring“Optional if a project is bound.”
  • workspaceIdstring“Instead of a project, from list_workspaces.”
• assign

  “Hand an item to a person, who is notified the way an assignment in the app notifies them.”

  Publisher declares: read-only no · destructive no · idempotent yes · open-world no

  2 inputs, 2 required

  • itemIdstringrequired“Item id from list_items.”
  • assigneestring or nullrequired“A name, email or id from list_members, "me", or null to unassign.”
• set_statuson 2 other servers

  “Move an item to open, deferred or resolved.”

  Publisher declares: read-only no · destructive no · idempotent yes · open-world no

  2 inputs, 2 required

  • itemIdstringrequired“Item id from list_items.”
  • statusstringrequired
• get_itemon 37 other servers

  “Everything needed to work one item: the whole thread in order, the page and URL it is on, the anchor identifying the element the person pointed at, and the pictures — what the page looked like when i…”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  1 input, 1 required

  • itemIdstringrequired“Item id from list_items.”
• project_review

  “Everything needed to write an accurate project review or hand-off document: the shape of the work, every resolved thread and how it ended, what was deferred and why, what is still open, and the longe…”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  3 inputs

  • projectIdstring“Project to review.”
  • sectionstring“Omit for the overview (all counts, first rows of each section).”
  • offsetnumber“With section: where to start, from the previous result's 'more' line.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-24.

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.