MCP.Market

Lawang Onboard MCP server

online · 100% uptime
by gablooge·io.github.gablooge/lawang-onboard·v0.1.1
No reviews yet

Permission-aware onboarding MCP server: answers about a codebase, filtered by the caller's role.

A87/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A87/100

full report

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed Lawang Onboard yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Lawang Onboard tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Public scan report

scanner v0.1.10 · 2026-10-01 · same rubric, same numbers if you re-run it

no findings
  • –Code scanpackage could not be scannedn/a
  • Live reliabilityremote reachable in 697ms (auth required)20/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualityauth enforced (unknown)9/15
  • Maintenancelast push 1 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 87/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Lawang Onboard compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
87/100
higher than 73% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
567 ms
faster than 25% of 30,031 servers

Install Lawang Onboard in Claude Code, Cursor or VS Code

claude mcp add --transport http lawang-onboard https://lawang-onboard.samsulhadi.com/mcp
Add to Cursor

What the publisher says

From the Lawang Onboard repository's README, as published. We do not edit it. Read it on GitHub

Lawang Onboard

Permission-aware AI onboarding. An onboarding copilot inside IBM Bob that explains a codebase to a new engineer, and only the parts they are allowed to see.

Built for the IBM Bob 2.0 Hackathon (lablab.ai, 25 to 27 September 2026) by team Lawang Onboard.

The problem

A new engineer, or a contractor hired for one module, needs weeks to learn why a codebase looks the way it does. The answers exist, spread across commit messages, architecture decision records and pull request reviews, but nobody reads those on day one. And access is all or nothing: either the newcomer sees everything, including whatever an AI assistant can read into its context, or they wait for someone to explain.

What it does

Open the repository in IBM Bob, switch to the Onboard mode, and ask:

  • /tour: the map of what you can see, module by module.
  • /trace webhook: how a webhook becomes a record, step by step.
  • /why internal/ingress: the decisions and reviews behind a path.
  • "What can I pick up first?"

Bob answers from the code and its history, and cites every item it used. Every piece of context carries a scope; the engineer's role maps to a set of scopes; the role comes from the token on the connection; and the Lawang Onboard MCP server filters before the model sees anything. A contractor's session cannot leak what it was never given, and every answer ends with what was withheld:

Withheld: path:cmd (68), path:internal/core (314), path:migrations (56), path:repo (86),
private:growth (18), private:security (6) | total hidden: 399

Results

Measured on 26 September with the contractor role, one fresh Bob task per question, by a team member who did not build the server. Full write-up: docs/benchmark.md.

How it works

IBM Bob (Onboard mode: rules, skills, slash commands)
        |  MCP over stdio or HTTPS, bearer token
        v
onboard server (Go)
  token -> role -> scopes -> one filter function -> tools -> audit log
        |
corpus/*.jsonl  (610 items: files, docs, ADRs, commits, PRs, reviews, issues, each with scopes)

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Lawang Onboard: common questions

Is Lawang Onboard MCP server safe?
Yes, by our scan: it is graded A (87/100). Read the Lawang Onboard safety report
How do I install Lawang Onboard?
It runs remotely at lawang-onboard.samsulhadi.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Lawang Onboard need an API key?
Yes. The registry entry asks for ONBOARD_TOKEN, ONBOARD_TOKEN_CONTRACTOR, ONBOARD_TOKEN_EMPLOYEE, ONBOARD_TOKEN_MAINTAINER and 1 more.
Is Lawang Onboard maintained?
The last commit was 35 days ago (2026-09-30). The latest release is v0.1.1.
Is Lawang Onboard up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Lawang Onboard compare with other MCP servers?
safety score 87/100 (higher than 73% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 567 ms (faster than 25% of 30,031 servers). Full comparison.