Skip to content
Back to search

FridaScope

On-device Android API tracer powered by Frida: pick an app, watch the APIs it uses live, get a report. Works standalone on the phone or connected to a PC, with an MCP server for AI agents.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/jon2g--fridascope/badge.svg)](/listings/jon2g--fridascope)

HTML

<a href="/listings/jon2g--fridascope"><img src="/api/listings/jon2g--fridascope/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 44 lines
  1. # FridaScope
  2. On-device Android API tracer powered by Frida: pick an app, watch the APIs it
  3. uses live, get a report. Inspired by Inspeckage, rebuilt on Frida — with
  4. native-call tracing and an MCP server so AI agents can drive it.
  5. ## What it does
  6. - **App selector** — list installed apps, search, filter user/system, pick a
  7. target in one tap.
  8. - **Live API report** — API calls stream in as the target app runs: timestamp,
  9. API name, category (network, file, crypto, IPC, location…), arguments, and
  10. counts. Pause, filter, and export the session as JSON.
  11. - **Two modes, no compromises**
  12. - **Standalone on-device:** the companion app runs on the rooted phone,
  13. talks to `frida-server` on localhost, and traces without any PC.
  14. - **PC-connected:** connect over USB/ADB and drive the same tracing from a
  15. computer — same engine, same report.
  16. - **MCP server** — expose tracing as MCP tools (`list_apps`, `start_trace`,
  17. `get_report`, …) so coding agents like Cursor can run traces and read
  18. reports directly.
  19. ## How it works
  20. Frida does the instrumentation (Java methods, JNI, and native functions —
  21. something Xposed-based tools cannot see). A small engine collects the events,
  22. the app (or the PC client) renders the live report, and the MCP server wraps
  23. the same engine for agents.
  24. ```
  25. Target app ──Frida──▶ Engine (event stream) ──▶ App UI (live report)
  26. └──▶ MCP server ──▶ AI agent
  27. ```
  28. ## Status
  29. Early planning. See `.meta/plans/` for the MVP plan and the MCP server plan.
  30. ## Plans
  31. - [MVP plan](.meta/plans/fridascope-mvp.md) — engine, app UI, both modes,
  32. icon ideas
  33. - [MCP server plan](.meta/plans/fridascope-mcp.md) — tools, report schema,
  34. transport

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.