Project Handover Checker

Project Handover Checker extracts project handover evidence and checks material completeness without making approval decisions.

Capabilities

• Extract explicitly stated handover items, owners, statuses, dependencies, and source evidence.

• Check supplied handover materials against user-provided requirements.

• Classify requirements as satisfied, partially satisfied, or missing based only on supplied text.

• Preserve operational boundaries: the service does not approve handovers, deploy systems, transfer credentials, rotate secrets, or perform external actions.

Tools

• extract_handover_inventory: Extracts explicitly provided deliverables, owners, stated status, dependencies, and source evidence.

• check_handover_completeness: Checks supplied handover materials against a supplied checklist or explicit requirements.

Boundaries

• Read-only analysis of user-provided project handover text.

• No login, OAuth, database, external API callout, or external system write operation.

• Do not input passwords, API keys, access tokens, private keys, cookies, administrator credentials, or other secrets.

• Results are completeness findings, not approval decisions.

Local Setup

npm install

Start the local Worker:

npm run dev

Local MCP URL:

http://127.0.0.1:8787/mcp

Checks

npm run typecheck
npm run test:mcp:local
npm test

The local MCP regression suite prints an automatic scenario summary with total, passed, failed, and skipped counts.

Deployment

Deploy with the configured Cloudflare Worker target:

npx wrangler deploy

Worker name:

project-handover-checker

Public Routes

• Home: /

• Privacy Policy: /privacy

• Terms of Service: /terms

• Support: /support

• MCP endpoint: /mcp

• Health endpoint: /health

• OpenAI Apps Challenge route: /.well-known/openai-apps-challenge

The current challenge response value is the temporary placeholder:

test

Before formal submission, replace the temporary challenge value "test" with the token supplied by the platform and redeploy. Do not commit real platform tokens or secrets into public Git history.

Support

Support email:

<a href="mailto:sidcraigau@gmail.com">sidcraigau@gmail.com</a>

Public, non-sensitive issues may also use GitHub Issues:

https://github.com/YanKe1816/project-handover-checker/issues

Do not include secrets, tokens, credentials, cookies, private keys, or unnecessary personal information in support requests.