MCP.Market

Where Them Logs MCP server

online · 100% uptime
by wherethemlogs.app·app.wherethemlogs/log-locations·v1.0.0
No reviews yet

Where apps write their log files on Windows, macOS and Linux, as exact copyable paths.

A91/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A91/100

full report

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed Where Them Logs yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Where Them Logs tools (2)

write = sends, deletes, buys or posts
  • get_app_log_locationsFree

    Every log location for one app, by the slug that search_log_locations returns.

  • search_log_locationsFree

    Find where an application writes its log files. Matches app names and aliases (for example 'teams', 'zoom', 'docker') and the names of files listed under a path (for example 'AppWorkload.log'), not vendor names. Returns each app's log paths by platform.

Public scan report

scanner v0.1.10 · 2026-10-14 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 1610ms20/20
  • Tool poisoning2 tool descriptions checked15/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenancelast push 7 days ago15/15
  • Maintainer identityendpoint served from the registry-verified namespace domain8/10
Overall 91/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Where Them Logs compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
91/100
higher than 85% of 48,255 servers
Tools
2
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
401 ms
faster than 37% of 30,031 servers

What its tools let an agent do: 2 read

Install Where Them Logs in Claude Code, Cursor or VS Code

claude mcp add --transport http log-locations https://wherethemlogs.app/api/mcp
Add to Cursor

What the publisher says

From the Where Them Logs repository's README, as published. We do not edit it. Read it on GitHub

wherethemlogs.app

A searchable index of application log file locations across Windows, macOS and Linux - every path qualified by installer type and architecture, printed exactly as the machine writes it.

Built for the people who need the path mid-incident: IT and endpoint administrators, application packagers, and anyone else who has lost twenty minutes to a forum thread of unknown vintage.

Layout

app/                  pages, route handlers, proxy - Next.js 16
components/  lib/     UI, shared model, server-only data access
infra/                Azure resources - Bicep
scripts/              seed data and the seeder
docs/                 architecture, API reference, deployment, MCP, answer engines

One application, one image. Pages are server-rendered from Cosmos; route handlers under app/api/ serve the browser and the admin portal from the same process.

Run it

npm install
LOCAL_ADMIN_BYPASS=true \
COSMOS_ENDPOINT=https://<account>.documents.azure.com:443/ \
COSMOS_DATABASE=wtla \
npm run dev            # http://localhost:3777

Needs az login with an account that holds the Cosmos data-plane role. Full setup is in docs/DEPLOYMENT.md.

What's here

Keyboard: / focuses the search field from anywhere, arrows walk the type-ahead, Enter commits to the full results, Shift+Enter copies the highlighted result's first path.

The catalogue

Vendor > App > LogPath. One vendor has many apps; one app has many log paths, embedded on the app document. Every vendor carries an icon and every app may override it - App.iconUrl: null means inherit the vendor's, resolved on read.

Currently seed data: 24 vendors, 33 apps, 86 log paths in scripts/seed-data.json, all real and verifiable, labelled as a demonstration set in the footer and on the privacy page.

npm run seed -- --endpoint https://<account>.documents.azure.com:443/

Paths are stored byte for byte - %LOCALAPPDATA%, ~/Library/Logs, $XDGSTATEHOME are never expanded, because the machine being fixed is not this one.

Contributing an entry

Open an issue. One issue per application, with the platform and installer type in the title, and say how you verified the path.

Issues are public: do not paste real hostnames, usernames, tenant identifiers or customer names into one.

Before this goes live

  • [ ] Register the Entra ID app, add the admin app role, and set the AUTHCLIENTID / AUTHTENANTID repository variables. Until then /admin has nowhere to send you. docs/DEPLOYMENT.md § 7.
  • [x] Choose the analytics provider - Google Analytics 4, loaded only after Accept (components/Consent.tsx).
  • [ ] Replace the seed catalogue with the real index - /admin/import takes the research JSON.
  • [x] Build the admin UI on top of the CRUD API.
  • [x] Make the repo public - requests and corrections are issues here, from the forms in .github/ISSUE_TEMPLATE/.

Infrastructure

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Where Them Logs: common questions

Is Where Them Logs MCP server safe?
Yes, by our scan: it is graded A (91/100). Read the Where Them Logs safety report
How do I install Where Them Logs?
It runs remotely at wherethemlogs.app. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Where Them Logs need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Where Them Logs maintained?
The last commit was 28 days ago (2026-10-07). The latest release is v1.0.0.
Is Where Them Logs up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of Where Them Logs?
Servers from other publishers that do the same job: SSH — policy-gated remote access MCP server and Token Optimizer MCP server.
How does Where Them Logs compare with other MCP servers?
safety score 91/100 (higher than 85% of 48,255 servers); tools 2 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Where Them Logs

Same job from other publishers: the closest match first, then the best rated.

  • SSH — policy-gated remote access
    Policy-gated, audited SSH for Linux and Windows hosts: roles, approvals, and an audit log.
    B
  • Token Optimizer
    Context-window optimization: caching, compression & smart file tools that cut tokens 60-90%.
    C