moonlighter (albertosca/moonlighter) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 15 tools. No publisher has claimed this listing.

C
Emerging
74/100

moonlighter

Job hunting from a Claude conversation: scans six ATS job boards, scores every posting against your profile with an LLM, and composes complete application answer sheets — you review and submit. Self-hosted MCP server; your data stays on your machine.

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

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

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

albertosca

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 →

Install from

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
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.
🔐
You'll be asked for 1 credential: ANTHROPIC_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes15 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.

scan_and_evaluate

Scan job boards, evaluate with LLM, return new jobs above threshold.

scan_company

Scan every open posting at ONE company right now and evaluate the new ones.

add_job

Evaluates a manually provided job and saves it to the database.

verify_job

Re-evaluates a job that couldn't be scored automatically because its description was empty, using text you copy from its real page.

archive_stale_jobs

Detect and archive (status='archived', closed_at set) jobs that disappeared from their source.

list_jobs

List jobs from DB filtered by status.

get_job

Get full details of a job posting.

prepare_application

Produce the full set of answers for a job application, for you to paste into the form yourself. Reads the questions from the ATS API when it publishes them (Greenhouse, Recruitee); otherwise asks you to copy the page. job_id: ID of the job

prepare_application_from_paste

Same as prepare_application, for a page whose questions no API publishes: select the whole application page, copy it, and pass the text here. job_id: ID of the job page_text: everything copied off the application page

get_pipeline

Show full application funnel: counts and list by status.

update_status

Update application status manually. status: 'screening' | 'interview' | 'offer' | 'rejected' | 'submitted' | 'draft' notes: free text notes appended to history next_action: e.g. 'follow up on 2026-06-01'

list_answer_bank

Every banked screening answer, most recently used first. Entries older than answer_bank_max_age_days are marked expired: kept, but no longer replayed on a sheet until a new submission refreshes them.

forget_answer

Delete one banked answer by its question text (matched the way the bank keys it: lowercase, collapsed whitespace, no trailing punctuation). Use it when list_answer_bank shows an answer that is wrong or stale; the next application that asks the question goes to the LLM again.

setup_email

Configure Gmail authentication for the account that receives application replies. Run only once. Opens the browser to authorize access. Requires the OAuth client file at email.credentials_path (default MOONLIGHTER_HOME/gmail-client.json) and writes the token to email.token_path — overwriting whateve

sync_email_responses

Read recent emails in the configured Gmail account, whether read or unread, classify them with the LLM, and update the applications database. Returns a summary of the updates made.

// 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.
configMOONLIGHTER_HOMEThe wizard writes config.yaml into (defaults to ~/.moonlighter/). Two
🔐 secretANTHROPIC_API_KEYllm_backend: api — the Anthropic SDK, billed to API credits. Requires
configMOONLIGHTER_DB_PATH
// 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

15/15 tools missing one or more hints — scan_and_evaluate (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); scan_company (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); add_job (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +12 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.

Tool inputs are validated

11/15 tool handlers declare input schemas (73%)

Declare an inputSchema with zod/joi/yup on every tool definition.

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 3 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 Score](https://m8ven.ai/badge/mcp/albertosca/moonlighter)](https://m8ven.ai/mcp/albertosca/moonlighter)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: ffc4d6792fc5f4a3a5fc9a17a4134cd967d26f54
code hash: 54612cf94b767ad4352a2a36c83b574e11f0c12dc4192a866329d60835364a7e
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