Targetprocess MCP Server

targetprocess-mcp-server npm v2.7.0

Published by serhiimaksymiv — 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 Tartget Process

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/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
Moderate
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 = 96/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 − 4 = 96. 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
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−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 75

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

  • create_bug_based_on_cardingests untrusted input
  • add_commentno sensitive capability
  • add_comment_with_userno sensitive capability
  • add_test_case_step_by_idno sensitive capability
  • add_test_cases_to_test_planno sensitive capability
  • assign_roleno sensitive capability
  • assign_role_to_featureno sensitive capability
  • create_bugno sensitive capability
  • create_card_relationno sensitive capability
  • create_epicno sensitive capability
Show 65 more tools ↓
  • create_featureno sensitive capability
  • create_formatted_featureno sensitive capability
  • create_formatted_user_storyno sensitive capability
  • create_taskno sensitive capability
  • create_test_planno sensitive capability
  • create_user_storyno sensitive capability
  • delete_cardno sensitive capability
  • delete_card_relationno sensitive capability
  • delete_test_case_step_by_idno sensitive capability
  • get_assignment_rolesno sensitive capability
  • get_bug_commentsno sensitive capability
  • get_bug_contentno sensitive capability
  • get_bug_workflowsno sensitive capability
  • get_card_current_statusno sensitive capability
  • get_card_relationsno sensitive capability
  • get_commit_messageno sensitive capability
  • get_current_releasesno sensitive capability
  • get_epic_contentno sensitive capability
  • get_epic_featuresno sensitive capability
  • get_feature_commentsno sensitive capability
  • get_feature_contentno sensitive capability
  • get_feature_user_storiesno sensitive capability
  • get_in_progress_tasks_and_bugsno sensitive capability
  • get_logged_in_userno sensitive capability
  • get_my_time_logsno sensitive capability
  • get_not_covered_user_stories_in_featureno sensitive capability
  • get_prioritiesno sensitive capability
  • get_process_workflowsno sensitive capability
  • get_processesno sensitive capability
  • get_projectsno sensitive capability
  • get_relation_typesno sensitive capability
  • get_release_bugsno sensitive capability
  • get_release_featuresno sensitive capability
  • get_release_open_bugsno sensitive capability
  • get_release_open_user_storiesno sensitive capability
  • get_release_user_storiesno sensitive capability
  • get_release_user_stories_with_descriptionno sensitive capability
  • get_team_iterationsno sensitive capability
  • get_teamsno sensitive capability
  • get_teams_and_team_assignmentsno sensitive capability
  • get_test_case_by_idno sensitive capability
  • get_test_plan_by_idno sensitive capability
  • get_test_plan_test_cases_by_idno sensitive capability
  • get_test_plan_test_cases_with_steps_by_idno sensitive capability
  • get_user_by_idno sensitive capability
  • get_user_story_bugsno sensitive capability
  • get_user_story_commentsno sensitive capability
  • get_user_story_contentno sensitive capability
  • get_user_story_test_casesno sensitive capability
  • get_user_story_workflowsno sensitive capability
  • get_usersno sensitive capability
  • get_versionno sensitive capability
  • list_my_bugsno sensitive capability
  • list_my_user_storiesno sensitive capability
  • log_timeno sensitive capability
  • search_tp_cardsno sensitive capability
  • set_business_valueno sensitive capability
  • update_bugno sensitive capability
  • update_epicno sensitive capability
  • update_featureno sensitive capability
  • update_test_case_by_idno sensitive capability
  • update_test_case_step_by_idno sensitive capability
  • update_user_storyno sensitive capability
  • update_user_story_stateno sensitive capability
  • write_test_casesno sensitive capability

What this scan could not see

Versions 6

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
v2.7.0 latest A 96/100 0 1.13.0 2026-09-08
v2.6.8 A 96/100 0 1.12.1 2026-08-16
v2.6.6 A 96/100 0 1.12.1 2026-08-13
v2.6.5 A 96/100 0 1.12.1 2026-08-05
v2.6.4-a A 96/100 0 1.12.1 2026-08-03
Show 1 more version ↓
v2.6.3 A 96/100 0 1.12.1 2026-07-29

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

Use the free API → How scoring works

More in Productivity & Workflow