Skip to content

MCP servers › io.github.risyadul › lionscope

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

io.github.risyadul/lionscope

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

Android profiler and Layout Inspector: CPU, memory, frames, stalls, layouts, network, logcat — the publisher's description

7 of 8 record checks metversion 0.11.0TypeScriptApache-2.0standard input/output

Summary

io.github.risyadul/lionscope is a local MCP server listed in the official MCP registry at version 0.11.0, under the namespace of the GitHub account risyadul. Its linked repository, github.com/risyadul/Lionscope, belongs to the same GitHub account.

Record checks

7 of 8 record checks met · 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)
  • met: Package names its licence with a standard (SPDX) identifier
  • met: The version the registry lists can be installed and is not withdrawn
  • not met: npm package carries build provenance (attestation)
  • met: No known critical or high advisory in the package or its dependencies
  • #1,566 of 18,234 packages by monthly downloads, tied with 1 other
  • Not ranked by stars: 0 stars (ranked from 10)

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
npm · listed version current
License
Apache-2.0
Dependencies
no known high or critical advisories
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.11.0, published 2026-10-30 (registry, as of the 2026-10-31 snapshot)
First listed version
2026-10-24 (earliest version still in the registry; older removed versions would be earlier)
Version history
2 versions listed, 2026-10-24 to 2026-10-30; 2 in the 90 days before the 2026-10-31 snapshot.
Most recent 2 versions
  • 0.11.0 · 2026-10-30
  • 0.9.0 · 2026-10-24
(versions still listed in the registry only)
Registry data
snapshot 2026-10-31
Package and repository
checked 2026-10-31

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry; listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. 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.9.0 (published 2026-10-24) → 0.11.0 (published 2026-10-30), between the registry lists of 2026-10-30 and 2026-10-31.

The publisher’s GitHub release note for 0.11.0 (“Lionscope 0.11.0”), published 2026-10-30.

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

- Agent tool `mark` (session): names the current moment of the running session, e.g. `run-3` before the third
  repetition of a test. `search_logcat` and `get_crashes` take `sinceMarker` (instead of `since`) and
  `untilMarker`, so lines and crashes can be counted per run without clock math or clearing the device's log
  buffer; a range that ends before it starts is refused. Markers are on the clock logcat lines are timed on (the
  device clock plus the offset measured at the session start); marking a label again moves it, `status` lists the
  newest 20 and a new session starts without any. They are not shown in the dashboard.
- `search_logcat` and `get_crashes` return the resolved time `range`, and `search_logcat` `complete`: false once
  lines of that range have been dropped from the log buffer, so a count taken too late does not read as zero.
- `screenshot` returns `meanLuminance`, `nonBlackRatio`, `dominantRatio` and `blank` of the full-size capture, to
  tell across runs whether a screen rendered or stayed black without comparing images: `blank` means one colour
  covers at least 98% of the pixels, all near-black shades counting as one (a black video area with only status
  bar icons on top, also a sparse page of any colour). The image is unchanged; a capture that can't be decoded
  gets null numbers.
- Agent tool `stop_app` (device control): force-stops an app with `am force-stop`, for a clean run without starting
  it again (`launch_app` with `cold` only stops it to start it). Its unsaved state is lost, unlike pressing HOME.
- `hint` selector for `tap_element`, `type_text`'s `field`, `wait_for` and `scroll_to`: a field's hint (placeholder)
  as `get_ui_tree` lists it. Where the dump has hints, it keeps matching once the field has text, unlike `text` (an
  empty field reports its hint as its text). Where it has none (older Android versions), it matches the text of any
  editable field instead, so it finds an empty field by its hint but not a filled one.
- `type_text` `mode`: `cursor` (the default, as before: text goes in at the caret, which lands where the tap
  landed), `append` (the caret goes to the end of the text first) and `replace` (the field's text is deleted
  first); `replace` with `text: ""` clears the field. Both need a focused text field, read from a new dump before
  any key: the one given as `field` must have taken the focus (one that opens a picker instead gets no key), and
  without `field` the focused one is used. An empty field gets no keys. Android 13+ gets ctrl+End, or ctrl+A and
  Delete (`input keycombination`). Older versions, or a device whose version can't be read, have no ctrl key from
  adb: `append` presses End, which reaches the end of the caret's line only in a multi-line field, and `replace`
  deletes as many characters as the UI tree shows (End then Delete, or Delete and Forward delete around the caret
  when the text has line breaks), so it refuses a password field, whose text the tree hides. In a multi-line field
  whose text wraps without line breaks, part of it may stay (the dump does not say a field is multi-line);
  `matches` then says `false`.
- Agent tool `get_crashes`: the app's crashes since the session started, read from logcat's `crash` buffer (the
  package's process and its `<package>:*` processes, not just the PID being followed), so a crash is kept even when
  the app's own logcat turns over within a minute, when the process died before Lionscope saw its PID (a
  start-and-crash loop), and for the app's other processes (`:remote`). Uncaught Java/Kotlin exceptions
  (`FATAL EXCEPTION`) and native crashes (crash_dump's report: signal, cause, abort message, backtrace), the last 50
  per session, with time, pid, thread, process, exception and message, and the stack (every `Caused by`, the first
  12 frames of each exception). Stored redacted; other apps' crash lines are passed over and never stored.
- `search_logcat` returns `retained` (`entries`, `capacity`, `oldes

The release on GitHub

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

What it is

How do I add it to my client?

Config from the registry entry

From the npm package lionscope

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below. The command runs the publisher’s code on your machine.

Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)
{
  "mcpServers": {
    "lionscope": {
      "command": "npx",
      "args": [
        "-y",
        "lionscope@0.11.0",
        "mcp"
      ]
    }
  }
}
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "lionscope": {
      "command": "npx",
      "args": [
        "-y",
        "lionscope@0.11.0",
        "mcp"
      ]
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "lionscope": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "lionscope@0.11.0",
        "mcp"
      ]
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"lionscope","type":"stdio","command":"npx","args":["-y","lionscope@0.11.0","mcp"]}'
Claude Code
claude mcp add --transport stdio lionscope -- npx -y lionscope@0.11.0 mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "lionscope": {
      "command": "npx",
      "args": [
        "-y",
        "lionscope@0.11.0",
        "mcp"
      ],
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "lionscope": {
      "command": "npx",
      "args": [
        "-y",
        "lionscope@0.11.0",
        "mcp"
      ]
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.lionscope]
command = "npx"
args = ["-y", "lionscope@0.11.0", "mcp"]
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "lionscope": {
      "command": "npx",
      "args": [
        "-y",
        "lionscope@0.11.0",
        "mcp"
      ]
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 -- npx -y lionscope@0.11.0 mcp
  • Arguments are written as the registry entry gives them; a named one as “--name value”, the form the registry documentation shows.
  • This runs the publisher's code on your machine (npx). Read its README first.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

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.

Can it be installed, and is it up to date?

Version pin · advisories

Listed version

Registry lists
0.11.0
Latest stable
0.11.0
Status
current
Withdrawn
no

Source: registry.npmjs.org · 2026-10-31. About the version the registry lists; a manual install may resolve to a different one.

Dependency advisories

critical0high0moderate0low0

Counted in the full dependency tree as resolved on 2026-10-31 (npm audit; each bar counts packages with an advisory, not advisories). Bars share one scale. The package itself has no known vulnerability (OSV.dev).

Integrity, provenance, license

Integrity
sha512-tuWYIdiwxsyeOpJcx…
Signature
signed
License
Apache-2.0

Source: the package registry · 2026-10-31.

Usage

Downloads
1,635 in the last month

Source: api.npmjs.org · 2026-10-31.

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
Version 0.11.0 on npmExists and can be installedmatchesnpm · 2026-10-31
Repository github.com/risyadul/LionscopeOpens publiclymatchesapi.github.com · 2026-10-31

Who made it?

Feature #7 · lineage

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

Namespace
io.github.risyadul
GitHub owner
a personal account (risyadul)
Build record
signed
Repository
github.com/risyadul/Lionscope
Stars
0
Repository age
0–30 days
Last push
0–30 days ago
Archived
no

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

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

7 of 8 record checks met · 1 not checked

  • #1,566 of 18,234 packages by monthly downloads, tied with 1 other
  • Not ranked by stars: 0 stars (ranked from 10)
  • 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.
  • MetPackage names its licence with a standard (SPDX) identifierApache-2.0
  • MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
  • Not metnpm package carries build provenance (attestation)Signed by npm, but no build attestation.What changes this check: npm's documentation describes publishing with provenance from a cloud-hosted runner of a supported CI/CD provider, using npm CLI 9.5.0 or newer and npm publish --provenance. npm: generating provenance statements
  • MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-31. 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.risyadul/lionscope

Answered from the data above

Who publishes io.github.risyadul/lionscope?

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

Is io.github.risyadul/lionscope safe to install?

We do not rate servers as safe or unsafe. 7 of its 8 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. The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Has io.github.risyadul/lionscope 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.

Is the listed version current?

Yes. The registry lists 0.11.0, the latest stable release on npm.

Where is the source code of io.github.risyadul/lionscope?

In github.com/risyadul/Lionscope, 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 the weekly update
listed 2026-10-31; not classified yet
Pricing modelAI-classified
not checked
no website in the registry entry
Programming language
api.github.com · 2026-10-31
Hosting type
registry · 2026-10-31
MCP capability
not checked
not read (no session)
Transport
standard input/output
registry · 2026-10-31
Required credentials
none declared
registry · 2026-10-31 · no declaration is not a guarantee
Package registry
registry · 2026-10-31
Freshness
0–30 days
registry updatedAt · 2026-10-31
Lifecycle status
registry · 2026-10-31
License class
package registry · 2026-10-31
Integrity hash
declared (sri)
package registry · 2026-10-31
Signature / provenance
signed
package registry · 2026-10-31
Dependency advisories
none known
npm audit · 2026-10-31
Popularity
1,635 downloads a month
package registry · 2026-10-31
Publisher signals
owner: a personal account · repository age: 0–30 days · stars: 0–9 · build record: signed
api.github.com · 2026-10-31
Maintenance
api.github.com · 2026-10-31
Environment
your machine
where it runs, from the hosting type · 2026-10-31

“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.risyadul/lionscope: MCP server record.” Data checked 2026-10-31. https://protocolprobe.com/mcp/servers/io.github.risyadul/lionscope

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: 7 of 8 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.risyadul/lionscope)](https://protocolprobe.com/mcp/servers/io.github.risyadul/lionscope)

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