Clean scanStatic scanned
Fetches Yahoo Finance quotes, history, financials and search from JavaScript, a CLI or your agent.
884.9k installs/moMIT
Logwork Helper
malcohelper · MCP server
Logwork Helper is a local MCP server and terminal command for people who log hours in Resource Optimiser and Jira self-hosted. Your assistant can query what you have logged, edit the hours or task name of an existing entry, reconcile Resource Optimiser against Jira by day, and preview and submit logwork or worklogs once you approve. It also maps ticket prefixes to projects, keeps a local history of what was applied and can schedule reminders. You log in to Resource Optimiser and save a Jira token from the terminal, not through the chat.
Written by ooruby from the README of logwork-helper 0.2.5.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Why it's useful
It keeps logging hours in Resource Optimiser and Jira in one place, with writes previewed for your approval before they happen.
What you could do with it
- Ask your assistant whether you have logged any work today.
- Compare a week of Resource Optimiser and Jira hours and see which days or issues do not match.
- Change the hours on an existing logwork entry after reviewing a before and after difference.
Written from its documentation: what it says it can do, not what our checks found.
Maintenance
Not measuredNo release date is on record for this package yet. The nightly publisher check records one as it reaches each npm package, about once every ten nights.
Release activity only: it says nothing about quality or safety, and a finished small package can be fine without releases. How it is measured
- Command execution is bounded
- inventory
- node child_process (cli.mjs:3)
- node child_process (install-user.mjs:4)
- node child_process (install.mjs:4)
- node child_process (manual-log.mjs:4)
- An inventory of where the code starts another program, not a verdict on this row: whether each one runs a fixed program or whatever it is handed takes a reading by hand.
Published because it was found. A finding is information about where the limits are, not a verdict that the software is unsafe.
What this does not cover
- Everything. Treat it as you would software from anywhere else.
Receipt history: every signed receipt for every version of this listing, and what changed between them.
In its maker's words
Local-first MCP server and terminal CLI for safe Resource Optimiser logwork automation.
Compare with
Compare all 4How far this has been checked
Static scanned
- What it establishes
- Its published package, or for a hosted server its source repository at a recorded commit, was read file by file, without running it, by every check in our current scan.
- What it does not
- How it behaves when it runs, or anything the scan does not read yet: several rubric checks, the repository's history, and compiled code in folders named dist or build. For a hosted server, that the endpoint runs the code that was read. The ooruby Index sets out exactly what was read.
- Exactly what was read
- Version 0.2.5, the file with digest sha512-JjZD0vdVnZtjEE6hoReHAiAdRzZ3zlVgjy953eTMl59IbXX2wdMkDzhgebm9iwMcOAXJvuOlpBzwWGCa01zhbg==, as the registry publishes it. A published version cannot be replaced, so this names the same bytes for anyone who checks.
- Authentication
- Runs locally. No hosted endpoint is listed for this package. You run it on your own machine, so there is no endpoint of ours to authenticate against.
Adding it
Paste this into your client's MCP configuration.
{
"mcpServers": {
"logwork": {
"command": "npx",
"args": [
"-y",
"-p",
"logwork-helper@0.2.5",
"logwork"
]
}
}
}Or run it directly.
npx -y -p logwork-helper@0.2.5 logworkPinned to 0.2.5, which is the version the findings above were found in. Drop the version to take whatever is newest, and the report on this page stops describing what you installed.
Where this came from
- Registry
- npm
- Package
- logwork-helper
- Version read
- 0.2.5
- Resolved
- 2026-10-10
No build provenance published. The repository above is the one the publisher declared, and nothing links it to the package you would install. That is not a mark against this listing, since most packages are published this way, but it is a check nobody can run.
The badge, if this is your listing
It renders the current rung (static scanned) and links back here, where what that does and does not establish is one click away. It updates itself as the evidence deepens.
[](https://ooruby.com/market/logwork-helper)About this listing
- Kind
- MCP server
- Category
- Finance & ops
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-10-05
Similar MCP servers
All MCP serversVerification records what our published tests found on a specific version at a specific date. It is not a warranty, and it does not certify that software is free of defects.