Pack local or remote codebases into AI-friendly files that LLMs and coding agents can read or search
Nothing to run from here
Owl24 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.
99/100
trust score
7
downloads a day
local
runs on your machine
742
downloads in 30d
What it does
Hand a production error to the coding agent you already use — it claims it and writes the fix.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --env 'OWL24_API_KEY=${OWL24_API_KEY}' --transport stdio owl24-mcp '--' npx -y owl24-mcp
# 2 — ask your agent for something these tools do
# list_errors, queue_error, list_queue and 7 more
It needs OWL24_API_KEY: this reads it from your environment, so export it first.
Owl24 costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
MAAll 1 server
Madnands51 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. This one runs on your machine: your client starts Owl24 as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads OWL24_API_KEY (Your owl24 project API key, from that project's page on the owl24 dashboard. Agent Access must be enabled for the project first) from your environment each time it starts the server, so the value stays out of its config: export it in your shell profile (macOS, Linux), or run setx OWL24_API_KEY … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user --env 'OWL24_API_KEY=${OWL24_API_KEY}' --transport stdio owl24-mcp '--' npx -y owl24-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
It reaches a system of yours, so it needs your own credential rather than the publisher’s: OWL24_API_KEY — Your owl24 project API key, from that project's page on the owl24 dashboard. Agent Access must be enabled for the project first.. You set it in your own client’s config, on your machine — this marketplace never holds it.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
10 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.
Lists deduplicated error groups for this project - one row per distinct bug, with occurrence count, first/last seen, which service it's in, whether it's already queued/claimed/resolved (queue_state), and whether a cached AI root-cause report already exists for it (has_report). Use this to answer "wh
No parameter schema on file.
Adds one or more error groups (by fingerprint, from list_errors) to the agent-access queue. Free, and never calls an AI provider - this only marks errors as ready for an agent to claim and investigate. Safe to call again on an already-queued-and-open fingerprint (a no-op, reported back as "skipped")
No parameter schema on file.
Lists items already in the agent-access queue, each with its numeric id (what claim_error/resolve_error need), fingerprint, trace_id, service_name, and claim state. Defaults to open (unclaimed, unresolved) items only - the actual work queue. Pass status: "all" or "resolved" to see history instead.
No parameter schema on file.
Claims one queue item by its numeric id (from list_queue), so no other agent works it at the same time. IMPORTANT: this is what triggers billing (see the owl24 Pricing page) - the first time an item is ever claimed, it's billed once, immediately, with no monthly cap; resolving or releasing it afterw
No parameter schema on file.
Fetches the spans, logs, and stack trace for one trace_id (from list_errors' sample_trace_id or list_queue's trace_id). This is the primary evidence to investigate from - most queued items have no AI report attached (queuing never runs one), so read this before assuming one exists.
No parameter schema on file.
Checks whether a human already ran (and paid for) AI Root-Cause Analysis on this trace, and returns it if so. Read-only - this tool NEVER runs a new analysis or spends AI-RCA credit. Returns {found: false} for the normal case where no report exists yet; that is not an error, and is not a reason to w
No parameter schema on file.
Resolves a queue item once you have opened a pull request for it. Always include the PR link and the fingerprint you believe you fixed in resolutionNote (e.g. "Opened myorg/myrepo#123 - fixes fingerprint <fingerprint>") - that is what lets a later check confirm the error actually stopped recurring.
No parameter schema on file.
Returns just the count of open (unresolved) queue items, without the cost of fetching the full list - call this on every poll and only call list_queue when the count is greater than 0. Matches GET /api/v1/agent-access/count.
No parameter schema on file.
Releases a claimed item back to open WITHOUT resolving it - use this when you can't actually find or confirm the cause, instead of marking it resolved with a "couldn't fix" note. This never adds a new charge on top of the claim - if that claim was billable, releasing it doesn't refund the charge eit
No parameter schema on file.
Pushes a claim's expiry another claim-TTL window out. Use this if you're still actively working an item and getting close to claim_expires_at (from claim_error's or list_queue's response) - the alternative is racing the clock and risking another agent claiming it out from under you. Free, and does n
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- 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 Owl24 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: —
ATrust score 99 / 100
Release 0.2.2 · scanned 14 Oct 2026
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 score99
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationrepo
Surface digestd9a807df6a7f6db81ad0380fabaecca74228220ba42b4013762a6398b1cb78a8
Score vectorthreat 100 → client 99
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
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.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (10 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
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 |
|---|---|---|
| list_errors | no tags | |
| queue_error | no tags | |
| list_queue | no tags | |
| claim_error | no tags | |
| get_trace | no tags | |
| get_rca_report | no tags | |
| resolve_error | no tags | |
| count_open_items | no tags | |
| release_error | no tags | |
| extend_claim | 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 digestd9a807df6a7f6db8
Scanned2026-10-14
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
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.2.2. Pin a release below and the command asks for exactly that one.
0.2.2
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 Owl24 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.