Interact with Microsoft 365 and Office services through the Microsoft Graph API.
Nothing to run from here
KirinBoard 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.
96/100
tool-list score
18
tools declared
remote
at its publisher
—
calls last 7d
What it does
Read-only agent claims, CI status and delivery data from a KirinBoard workspace
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http kirinboard-mcp https://app.kirinboard.ai/mcp
# 2 — ask your agent for something these tools do
# board, list_projects, ci_status and 15 more
KirinBoard costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
KIAll 1 server
kirinboard1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
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.
Claude Codedeclared by this listing
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. Its publisher asks you to sign in with OAuth: run /mcp in Claude Code and pick this server, and it opens a browser for that once.
claude mcp add --scope user --transport http kirinboard-mcp https://app.kirinboard.ai/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add — the only sign-in is its publisher’s own, with OAuth.
What it writes
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.
What you approve
18 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.
Call this before you claim or start an issue. One call returns, for the repository you are working in: every active claim (issue, phase, who, tool and model, branch, PR and checks, last active, live or stale); your own claims, if you pass session_id or branch; unclaimed issues in the ready phases (backlog, scoping, planning); who else is changing the paths you pass; and a one-line verdict per issu
| Parameter | Type | Required | Notes |
|---|---|---|---|
| repo | string | no | owner/name from your git remote. Optional when the token covers one repository. |
| issues | array | no | Issue numbers you are about to work on: each gets a verdict. |
| paths | array | no | Files or folders (trailing /) you will change: who else is changing them. |
| session_id | string | no | Your claim's session id, to list your own claims separately. |
| branch | string | no | Your branch, to list your own claims separately. |
| detail | boolean | no | More rows (claims and unclaimed issues). Default compact. |
The repositories (projects) this token can read, by owner/name.
Takes no parameters.
Pushes queued, running or finished in the last hour, with their outcome and checks; with a branch, that branch only (looking back 12 hours if it has nothing in the last hour). For pushes that finished more than an hour ago, use ci_history.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| repo | string | no | owner/name. Optional when the token covers one repository. |
| branch | string | no | Only this branch. |
| limit | integer | no | How many pushes (default 10). |
Whether anyone holds issue #N now (live or stale claim), and who last worked on it (the agent stamped on its pull request).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| repo | string | no | owner/name. Optional when the token covers one repository. |
| issue | integer | yes | The issue number. |
Agent sessions on a repository and the issues each holds: who, tool and model, state, last active. Live sessions only unless include_stale.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| repo | string | no | owner/name. Optional when the token covers one repository. |
| include_stale | boolean | no | Also list parked (stale) sessions. |
| limit | integer | no | How many sessions (default 30). |
What was opened, worked on and closed in a window: counts by phase, blocked items, and the most recently closed. Give days (1 to 90, default 14) or from and to (YYYY-MM-DD).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| repo | string | no | owner/name. Optional when the token covers one repository. |
| days | integer | no | A rolling window of this many days. |
| from | string | no | Start date (UTC), with to. |
| to | string | no | End date (UTC), with from. |
Finds the last tickets that would finish an initiative, and which of them are free to pick up. An initiative is a parent ticket that groups the tickets of one larger piece of work. For a repository it lists the initiatives the dashboard classes as almost done (a few tickets left that belong to the original push; by default 3 or fewer open and at least 75% closed, a setting the team can change), sm
| Parameter | Type | Required | Notes |
|---|---|---|---|
| repo | string | no | owner/name. Optional when the token covers one repository. |
| unclaimed_only | boolean | no | Only tickets that are free to pick up: not in progress and claimed by nobody. Initiatives with none are left out (and counted). |
| include_next_part | boolean | no | Also list initiatives whose first part is done and whose next part has not started. |
| limit | integer | no | How many initiatives (default 10). |
Shows how a repository's pull request gates have fared over the last 7 and 30 days. A gate is a check the dashboard grades every pull request by (for example agent identity, persona, or "closes an issue"). For each gate: how many pull requests passed it, failed it, would have failed it (the gate only warns for now), were not checked by it, are still pending or not read yet, and were exempt (promot
| Parameter | Type | Required | Notes |
|---|---|---|---|
| repo | string | no | owner/name. Optional when the token covers one repository. |
Answers "did the push I made a few hours ago pass?". Lists the pushes on a repository that finished between 1 and 12 hours ago (or 1 and 4 hours ago), newest first, each with its branch, pull request, title, who pushed it, outcome (passed, failed, awaiting, superseded), when it finished, how long it took, its commit and a link to the run, plus a count of each outcome. Narrow it by branch, pull req
| Parameter | Type | Required | Notes |
|---|---|---|---|
| repo | string | no | owner/name. Optional when the token covers one repository. |
| branch | string | no | Only this branch. |
| pr | integer | no | Only pushes for this pull request number. |
| sha | string | no | Only the push of this commit (its first 7 or more characters). |
| outcome | string | no | Only pushes with this outcome. |
| hours | number | no | How far back: 4 or 12 hours (default 12). Both read the same 12-hour list. |
| limit | integer | no | How many pushes to list (default 20). |
Lists what is closest to finished in a repository, so you can pick work that completes something. Two lists, in the dashboard's Quick wins order: initiatives (an initiative is a parent ticket that groups the tickets of one larger piece of work) with open tickets, almost done first, then open, then those whose remaining tickets are a new part, each with what is left and its open tickets, marking th
| Parameter | Type | Required | Notes |
|---|---|---|---|
| repo | string | no | owner/name. Optional when the token covers one repository. |
| kind | string | no | all (the default), initiative, or pull_request. |
| limit | integer | no | How many of each list (default 10). |
Call this before you start a shared operation such as a deploy or a restart (deploy:production, restart:api), to see whether another agent is already doing it. For a repository it lists the operations an agent holds, or held in the last 24 hours: the operation, who holds it, since when, until when the hold lasts unless it is renewed, and the last heartbeat. If someone holds the operation you need,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| repo | string | no | owner/name. Optional when the token covers one repository. |
| operation | string | no | Only this operation, e.g. deploy:production. |
Lists what needs a person on a repository, as the dashboard's Needs you panel does and in its order, most urgent first: the main branch failing CI, failing pull requests nobody is on, work held by a session that has ended, green or approved pull requests left unmerged, pull requests waiting long for review, claims that have gone quiet, two pieces of work changing the same files, issues closed with
| Parameter | Type | Required | Notes |
|---|---|---|---|
| repo | string | no | owner/name. Optional when the token covers one repository. |
| limit | integer | no | How many items (default 20). |
Call this before you push, to judge whether your job will wait for a runner and whether now is a busy time. For a repository it shows: what is waiting for a runner now (jobs, grouped by pull request or push, and the runner labels they wait on), how long the oldest has waited and whether the runners count as congested; the median wait for a runner (self-hosted jobs started today, else GitHub-hosted
| Parameter | Type | Required | Notes |
|---|---|---|---|
| repo | string | no | owner/name. Optional when the token covers one repository. |
| limit | integer | no | How many waiting groups and workflows to list (default 10). |
The dashboard's daily metric history for a repository, oldest day first, for trends: is CI getting slower or failing more, is the backlog growing, are runners congested more often? Each day carries what the dashboard recorded that day: issues filed and closed and open, CI runs passed and not passed, active agents, delivery counts (in progress, blocked, under an initiative, on the project board wit
| Parameter | Type | Required | Notes |
|---|---|---|---|
| repo | string | no | owner/name. Optional when the token covers one repository. |
| days | integer | no | How many days back, today included (default 14, at most 90). |
| sections | array | no | Only these sections: issues, ci, agents, delivery, capacity (default all). |
The thresholds the dashboard uses to judge a repository, as its team set them, and where each value comes from (the repository, the workspace, a settings file, or the default): when an in-progress item counts as stalled, how few tickets left and how much closed make an initiative almost done, how long a finished initiative stays in Recently finished, when an agent session counts as idle or parked,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| repo | string | no | owner/name. Optional when the token covers one repository. |
Answers "what did I or another session start and leave?". For a repository it lists three things. Left behind: open work held by a session that has ended, one row per open pull request (else per issue), most recently active first: the issue or pull request with its title and link, the session that held it, how long it has been quiet, and its status (recent, stale, or done when the issue was closed
| Parameter | Type | Required | Notes |
|---|---|---|---|
| repo | string | no | owner/name. Optional when the token covers one repository. |
| limit | integer | no | How many rows of each list (default 20). |
Lists the initiatives in a repository, and the container issues inside them, that hold at least the dashboard's threshold (default 70) of the 100 sub-issues GitHub allows one parent, fullest first: each with its sub-issue count, how many of those are closed, how many slots are free, and whether it is full. GitHub refuses a parent's 101st sub-issue, and closed sub-issues keep their slots. Use it be
| Parameter | Type | Required | Notes |
|---|---|---|---|
| repo | string | no | owner/name. Optional when the token covers one repository. |
Lists the open issues in a repository that have no area (no [persona] title prefix and no persona: label), as the dashboard's Has an area line counts them, each with a suggested area, the persona: label that gives it, a confidence (high or medium) and a one-line reason. The suggestion comes from the repository's own issues: the area most of the other issues under the same initiative have, or else
| Parameter | Type | Required | Notes |
|---|---|---|---|
| repo | string | no | owner/name. Optional when the token covers one repository. |
| suggested_only | boolean | no | Only the issues that have a suggestion (default false: every issue with no area). |
| limit | integer | no | How many issues (default 50). |
Free
$0 forever
- 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 KirinBoard or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 0.1.1 · scanned 3 Nov 2026
Graded from the tools this server lists, not from its source code.
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.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digest557dc5b7dc4c4ce81aef2e8e0a28398ed15c50d2c9745a58f744bcd35fe314f3
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| board | no tags | |
| list_projects | no tags | |
| ci_status | no tags | |
| who_holds | no tags | |
| live_sessions | no tags | |
| delivery_summary | no tags | |
| almost_done | no tags | |
| gate_compliance | no tags | |
| ci_history | no tags | |
| quick_wins | no tags | |
| operations | no tags | |
| needs_you | no tags | |
| ci_queue | no tags | |
| metrics_history | no tags | |
| settings | no tags | |
| left_behind | no tags | |
| sub_issue_limit | no tags | |
| area_suggestions | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest557dc5b7dc4c4ce8
Scanned2026-11-03
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
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 0.1.1.
0.1.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
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.
Sign in to write one
Any signed-in account that does not publish KirinBoard can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
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.