Harvest Forecast MCP Server

harvest-forecast-mcp PyPI v0.1.1

Published by azx-pbc-oss — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server for Harvest and Forecast APIs — let AI agents track time, manage projects, and update scheduling.

Trust grade
A
99/100
Last scanned get badge →
Trust
A · 99/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 = 99/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 − 1 = 99. 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:

PointsAdoption-risk factor
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

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 34

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

  • all_projects_scheduleno sensitive capability
  • budget_statusno sensitive capability
  • create_assignmentno sensitive capability
  • create_time_entryno sensitive capability
  • delete_assignmentno sensitive capability
  • forecast_whoamino sensitive capability
  • get_assigned_peopleno sensitive capability
  • get_forecast_personno sensitive capability
  • get_forecast_projectno sensitive capability
  • get_future_scheduled_hoursno sensitive capability
Show 24 more tools ↓
  • get_future_scheduled_hours_for_projectno sensitive capability
  • get_person_heatmapno sensitive capability
  • get_placeholder_heatmapno sensitive capability
  • get_project_heatmapno sensitive capability
  • get_remaining_budgeted_hoursno sensitive capability
  • harvest_whoamino sensitive capability
  • list_assignmentsno sensitive capability
  • list_forecast_milestonesno sensitive capability
  • list_forecast_peopleno sensitive capability
  • list_forecast_placeholdersno sensitive capability
  • list_forecast_projectsno sensitive capability
  • list_forecast_rolesno sensitive capability
  • list_harvest_clientsno sensitive capability
  • list_harvest_projectsno sensitive capability
  • list_harvest_tasksno sensitive capability
  • list_harvest_usersno sensitive capability
  • list_project_assignmentsno sensitive capability
  • list_time_entriesno sensitive capability
  • person_scheduleno sensitive capability
  • project_overviewno sensitive capability
  • team_utilizationno sensitive capability
  • time_summaryno sensitive capability
  • update_assignmentno sensitive capability
  • who_is_availableno sensitive capability

What this scan could not see

Versions 2

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.1.1 latest A 99/100 0 1.13.0 2026-08-25
v0.1.0 A 98/100 1 1.5.0 2026-07-22

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 · 99/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/harvest-forecast-mcp/badge.svg)](https://mcptrustchecker.com/registry/harvest-forecast-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/harvest-forecast-mcp"><img src="https://mcptrustchecker.com/registry/harvest-forecast-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/harvest-forecast-mcp/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 harvest-forecast-mcp --online --registry pypi

Use the free API → How scoring works

More in Productivity & Workflow