Wethod MCP Server

mcp-wethod npm v0.6.0 Source verified

Published by cesconix — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

MCP server for Wethod project management — timesheet, planning, budgets, and team tools

Trust grade
A
100/100
Last scanned get badge →
Trust
A · 100/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Minimal
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 100/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 0 = 100. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

✓ No adoption-risk deductions — minimal blast radius, verified enough, and fully inspected.

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 33

Each tool and what it can reach — statically extracted from the published source.

  • backfill_project_statusesno sensitive capability
  • check_timesheet_statusno sensitive capability
  • create_allocationno sensitive capability
  • create_project_statusno sensitive capability
  • create_timesheetno sensitive capability
  • delete_allocationno sensitive capability
  • delete_project_statusno sensitive capability
  • delete_timesheetno sensitive capability
  • get_availabilityno sensitive capability
  • get_billability_reportno sensitive capability
Show 23 more tools ↓
  • get_projectno sensitive capability
  • get_project_statusno sensitive capability
  • get_team_timesheetno sensitive capability
  • get_weekly_planno sensitive capability
  • list_allocationsno sensitive capability
  • list_budgetsno sensitive capability
  • list_capacitiesno sensitive capability
  • list_clientsno sensitive capability
  • list_production_plansno sensitive capability
  • list_productionsno sensitive capability
  • list_project_statusesno sensitive capability
  • list_projectsno sensitive capability
  • list_timesheet_logsno sensitive capability
  • list_timesheetsno sensitive capability
  • lookup_clientno sensitive capability
  • lookup_personno sensitive capability
  • lookup_projectno sensitive capability
  • lookup_project_typeno sensitive capability
  • resetno sensitive capability
  • setupno sensitive capability
  • syncno sensitive capability
  • update_allocationno sensitive capability
  • update_timesheetno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.6.0 latest A 100/100 0 1.13.0 2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 100/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/mcp-wethod/badge.svg)](https://mcptrustchecker.com/registry/mcp-wethod)
HTML
<a href="https://mcptrustchecker.com/registry/mcp-wethod"><img src="https://mcptrustchecker.com/registry/mcp-wethod/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/mcp-wethod/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan mcp-wethod --online

Use the free API → How scoring works

More in Productivity & Workflow