personal-ops-manual (aka-kika/personal-ops-manual) is an MCP server listed on the M8ven Trust Index. It scores 68 out of 100, grade C. It declares 7 tools. No publisher has claimed this listing.

Caution

68/100

personal-ops-manual

Item: personal-ops-manual
Rating: 68
Author: M8ven

Native macOS manual for your own setup: one Markdown page per machine, service and agent, read by every agent through MCP, written by one operator.

→ aka-kika/personal-ops-manual · listed on github_repo_search

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every push why connect →

Who stands behind it

aka-kika

Source: github_repo_search

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

GitHub

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings

⚠️

Tool descriptions don’t match what handlers do

6 tools describe read intent but their handlers mutate — list_documents (line 28: execFileSync("defaults", ["read", "com.kikalab.opsmanual", "documentsPath"], {); get_document (line 28: execFileSync("defaults", ["read", "com.kikalab.opsmanual", "documentsPath"], {); search_documents (line 28: execFileSync("defaults", ["read", "com.kikalab.opsmanual", "documentsPath"], {)

✅

No credential exfiltration, no sensitive file access, no obfuscation

Static analysis found nothing flowing your secrets to unexpected places.

✅

Open source with a license and README

Anyone can audit the code, the license is declared, and the publisher documents what it does.

// tools this server exposes7 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

list_documents

List documents in the Personal Ops Manual: id, title, category, tags, summary, timestamps. Sorted by category then title. Filter with `category`; page with `limit` (default 200) and `offset`. The response carries `total` so you know when you have everything.

get_document

Get a single document by its id, including the full Markdown body, summary, tags, and custom properties.

search_documents

Search titles, tags, summaries, categories, and bodies. Hits are ranked: title matches first, then tag, then summary or category, then body; ties by title. Each hit carries `matchedIn`, `updatedAt`, and a snippet around the first body match. `limit` defaults to 50.

list_categories

List all document categories with the number of documents in each.

get_stale

Pages that need a look. mode `oldest` (default) sorts by the Verified date on the page (falling back to updatedAt), oldest first. mode `unchecked` returns pages with open `- [ ]` checkboxes and lists them. Read-only; report findings to Kika or the operator, who edit the files.

report_change

For readers. Report a mismatch between a page and the machine so the operator can fix the page. Read the page first (search_documents, then get_document). Appends one dated line to _inbox/reports.md in the documents folder; it never edits a page. If the page already says it, do not report; news abou…

list_reports

For the operator (and anyone curious): the reports readers filed with report_change. status `open` (default) returns unticked lines, `handled` the ticked ones, `all` both. The operator applies open reports to the pages and ticks them in _inbox/reports.md.

// environment variables

To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.

configOPS_MANUAL_DIR

// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

7/7 tools missing one or more hints — list_documents (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_document (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); search_documents (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +4 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Descriptions match behaviour

Rename the tool, rewrite the description, or move the side-effect into a separate clearly-named tool.

Tests exist

No test files found

Add tests that exercise each declared tool.

Tool description accuracy

6 tools have description/behavior mismatches: list_documents: description implies read-only but handler writes/deletes/executes; get_document: description implies read-only but handler writes/deletes/executes; search_documents: description implies read-only but handler writes/deletes/executes

Update tool descriptions to accurately reflect all capabilities — especially write, delete, or execute operations.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail

The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.

// improvement guidance — verified publishers only

We have 5 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.

// embed badge in your README

[![M8ven Verified](https://m8ven.ai/badge/mcp/aka-kika/personal-ops-manual?variant=verified)](https://m8ven.ai/mcp/aka-kika/personal-ops-manual)

Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.

commit: 776d80352833a9b679d0056767908497a49dab6d

code hash: c667c7f4f1f6708113dba1e01c67a5d75bdb2296028cc2a7f53212ce601e040a

view raw JSON →

Check MCPs from inside your assistant

Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check

check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern

How to add it →Free · no account needed · works in any MCP client