Skip to content

MCP servers › io.github.thebanri › limoni-mcp

MCP server · registry snapshot 2026-10-28 · last checked 2026-10-28

limoni-mcp MCP server

Registry name io.github.thebanri/limoni-mcp

Limoni — the publisher's title

by thebanri · GitHub account (the registry's namespace rule)repository: same ownerSource ↗Website ↗

Drive a running Limoni terminal app by its semantic tree: find, click, type, wait_for. — the publisher's description

4 of 4 record checks metversion 0.16.0Gostandard input/output

Summary

io.github.thebanri/limoni-mcp is a local MCP server listed in the official MCP registry at version 0.16.0, under the namespace of the GitHub account thebanri. Its linked repository, github.com/thebanri/limoni, belongs to the same GitHub account.

Record checks

4 of 4 record checks met · 4 do not apply · 1 not checked

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • not checked: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: not an npm or PyPI package
  • #613 of 25,254 repositories by GitHub stars, tied with 6 others

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Operate this server? Correct a fact · README badge · Run the checks yourself

Key facts

Runs
local package
Transport
standard input/output
Your own values
none declared (not a guarantee)
Package
MCP bundle
Repository
public
Last tested
not tested

Tool list

Not read: It could be started, but has not been tested; we call no server's tools for anything we publish. This is our limit, not the server's. So there is no tool-list size and no result from the three APIs.

Add to your client

How fresh this is

Live-tested
no
Last tested
not tested
Latest version
0.16.0, published 2026-10-27 (registry, as of the 2026-10-28 snapshot)
First listed version
2026-10-27 (earliest version still in the registry; older removed versions would be earlier)
Version history
2 versions listed, all on 2026-10-27; 2 in the 90 days before the 2026-10-28 snapshot.
Most recent 2 versions
  • 0.16.0 · 2026-10-27
  • 0.15.0 · 2026-10-27
(versions still listed in the registry only)
Registry data
snapshot 2026-10-28
Package and repository
checked 2026-10-28

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry; repository link does not open; repository archived; no push in over 365 days. Does not apply: listed version cannot be installed or is withdrawn. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

Version 0.15.0 (published 2026-10-27) → 0.16.0 (published 2026-10-27), between the registry lists of 2026-10-27 and 2026-10-28.

The publisher’s GitHub release note for v0.16.0, published 2026-10-27.

Read the release note (the publisher’s text, shown as plain text, cut at 4,000 characters)
### Breaking

The API review before v1.0: one name for each thing, and the frame's
internals out of the public surface. Every removal has a replacement that
already existed; nothing here changes what an application can do.

- Renamed: `graphics.GetCachedEscapeSequence` → `CachedEscapeSequence`,
  `graphics.GetImageID` → `ImageID`, `driver.GetPlatformCapabilities` →
  `PlatformCapabilities`, `VirtualDataState.GetCachedRowText` →
  `CachedRowText`, `accessibility.AccessibilityNode` → `accessibility.Node`
  (the old name stays one release as a deprecated alias),
  `layout.LayoutDiagnostic` → `layout.Diagnostic`,
  `layout.LegacyMeasurable` → `layout.SizeHinter`, and
  `CommandPalette.SelStyle` → `SelectedStyle`, as in every other widget.
- Removed duplicates: `limoni.HAlignLeft/Center/Right` (use
  `AlignLeft/Center/Right`), `limoni.Layout` (`FlexLayout`),
  `driver.Driver` and `limoni.Driver` (`driver.Backend`),
  `Terminal.Backend()` (`Driver()`), `Program.SendBackend` (`SendDriver`),
  `engine.MessageFromBackend` (`MessageFromDriver`),
  `Frame.RenderComponent` (`RenderWidget`).
- Removed the old modal API: `Frame.ActiveModal` and the `Modal` type
  mirrored the topmost modal layer. `RegisterModal` still works; read
  `Frame.TopmostModal()` instead of the field.
- `Frame` no longer exports its bookkeeping: `ImageRegions`,
  `DebugRegions`, `WidgetStats`, `Accessibility`, `Theme`, `ThemeSet` and
  `EventRegions` (whose element type was already unexported) are private.
  Use `RegisterImageRegion` to place a picture (new; or, as pikap now
  does, a widget calling `ctx.RegisterImage`, which works on both sides),
  `ImageRegionsSnapshot`, `AccessibilityTree` and `SetTheme`. `Buffer`,
  `FocusManager`, `ClickRegions`, `Layers`, `Hyperlinks` and
  `ImageProtocol` stay, because applications and testkit read them.

### Added

- `Frame.BeginArea(r)` / `EndArea()`: a view written for the whole
  screen drawn in part of it — a tab, a pane, a preview. Between the two,
  `f.Area()` is `r`, nothing is drawn outside it, and click, scroll and
  event regions are cut to it, so a pane cannot take its neighbour's clicks.
  Areas nest; one left open is closed after the frame. Underneath,
  `Buffer.SetClip` / `ClearClip` / `Clip` limit every write, `Get` included.
  Modals and layers are not scoped to an area yet. Asked for by
  residual's tabbed multiplexer. Writes check the clip, which costs 1–4% in
  the widget draw benchmarks (0 allocations, unchanged).
- `Frame.RegisterImageRegion(region)`: place a picture with its own
  z-index, for applications that draw their own pixels.

### Changed

- `Buffer.Snapshot` reads with `CellAt`, so taking one no longer marks the
  buffer dirty, and works while a clip is set.
- A focused `Button` with neither `Style` nor `FocusedStyle` set takes the
  frame theme's `focus` role; explicit styles, and frames without a theme,
  keep reverse video and bold (#100, by @gezerui888).

### Fixed

- Windows Terminal and the Windows console got 16 colours: Windows Terminal
  sets neither `COLORTERM` nor `TERM`, only `WT_SESSION`. `WT_SESSION`, or a
  Windows process with no terminal named in `TERM`/`TERM_PROGRAM`, now means
  truecolor.
- Apple's Terminal: 24-bit colour only from build 470 (older builds read
  `38;2;r;g;b` as separate attributes and drew reverse video and blue); no
  `REP` (a repeated `─` drew once and the row landed short) and no scroll
  regions (rows the diff thought had moved stayed where they were).
- `go install …/apps/termimg@latest` on Windows stopped at a dozen compile
  errors (`unix.Poll`, `Setsid`, `SIGWINCH`). termimg is Unix-only now by
  build tag; on Windows it builds and says so, and that Windows Terminal
  1.22 and later show sixel by themselves.

- `apps/termimg` made large output 23 times slower in Alacritty: `cat` of
  100 MB took 26 s instead of 1.1 s. The shadow screen (`x/vt`) copies the
  whole screen for every line it scrolls. Lines that would only scroll
  through it are now ski

The release on GitHub

Source: the official MCP Registry list on 2026-10-27 and on 2026-10-28; release notes from the GitHub Releases API, checked 2026-10-28.

What it is

How do I add it to my client?

Config from the registry entry
  • No config: the MCP bundle is a file to install in a client that supports bundles, not a command.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Repository github.com/thebanri/limoniOpens publiclymatchesapi.github.com · 2026-10-28

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
io.github.thebanri
GitHub owner
a personal account (thebanri)
Repository
github.com/thebanri/limoni
Stars
183
Repository age
31–90 days
Last push
0–30 days ago
Archived
no

Source: the registry entry and api.github.com · 2026-10-28.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

4 of 4 record checks met · 4 do not apply · 1 not checked

  • Not ranked by downloads: not an npm or PyPI package
  • #613 of 25,254 repositories by GitHub stars, tied with 6 others
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • Not checkedRepository publishes a security policy (SECURITY.md)We did not read this repository's security policy.
  • Does not applyPackage names its licence with a standard (SPDX) identifierNot an npm or PyPI package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnNot an npm or PyPI package.
  • Does not applynpm package carries build provenance (attestation)PyPI packages have no npm-style attestation.
  • Does not applyNo known critical or high advisory in the package or its dependenciesNot an npm or PyPI package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-28. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about io.github.thebanri/limoni-mcp

Answered from the data above

Who publishes io.github.thebanri/limoni-mcp?

The registry ties the namespace io.github.thebanri to the GitHub account thebanri; only its owner can publish under it. Its linked repository, github.com/thebanri/limoni, belongs to the same GitHub account. These are facts from the registry and GitHub, not a rating.

Is io.github.thebanri/limoni-mcp safe to install?

We do not rate servers as safe or unsafe. 4 of its 4 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Has io.github.thebanri/limoni-mcp been security tested?

No. It could be started, but has not been tested; we call no server's tools for anything we publish. This is our limit, not the server's.

Where is the source code of io.github.thebanri/limoni-mcp?

In github.com/thebanri/limoni, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

Has it been tested?

Feature #1

It could be started, but has not been tested; we call no server's tools for anything we publish. This is our limit, not the server's. — our limit

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added in a later update
listed 2026-10-28; not classified yet
Pricing modelAI-classified
pending: added in a later update
the website is not read yet
Programming language
api.github.com · 2026-10-28
Hosting type
registry · 2026-10-28
MCP capability
not checked
not read (no session)
Transport
standard input/output
registry · 2026-10-28
Required credentials
none declared
registry · 2026-10-28 · no declaration is not a guarantee
Package registry
registry · 2026-10-28
Freshness
0–30 days
registry updatedAt · 2026-10-28
Lifecycle status
registry · 2026-10-28
License class
does not apply
package ecosystem not queried by this layer (mcpb); only npm and PyPI are supported here
Integrity hash
does not apply
package ecosystem not queried by this layer (mcpb); only npm and PyPI are supported here
Signature / provenance
does not apply
package ecosystem not queried by this layer (mcpb); only npm and PyPI are supported here
Dependency advisories
not checked
only npm and PyPI packages are audited
Popularity
does not apply
package ecosystem not queried by this layer (mcpb); only npm and PyPI are supported here
Publisher signals
owner: a personal account · repository age: 31–90 days · stars: 100–999
api.github.com · 2026-10-28
Maintenance
api.github.com · 2026-10-28
Environment
your machine
where it runs, from the hosting type · 2026-10-28

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.thebanri/limoni-mcp: MCP server record.” Data checked 2026-10-28. https://protocolprobe.com/mcp/servers/io.github.thebanri/limoni-mcp

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 4 of 4 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.thebanri/limoni-mcp)](https://protocolprobe.com/mcp/servers/io.github.thebanri/limoni-mcp)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology