Repsona MCP Server

@bellx2/repsona-mcp-server npm v1.0.7

Published by @bellx2 — 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.

Repsona MCP Server

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 3

medium Untrusted input can drive an external actionMTC-FLOW-005

Untrusted-input tools ([download_file]) co-exist with external-action tools ([upload_file]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.

Evidence: untrusted [download_file] → sinks [upload_file]

Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.

Location: flow download_file → upload_file

medium Tool "delete_file" can modify the filesystemMTC-CAP-002

Tool "delete_file" can write, overwrite or delete files (keyword "delete_file" in tool name). Verify it is scoped to a safe directory.

Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.

Location: tool delete_file

low Mutating tool "delete_file" declares no destructiveHintMTC-CAP-005

Tool "delete_file" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool delete_file

Tools 52

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

  • delete_filewrites files
  • download_fileingests untrusted input
  • upload_filenetwork egress
  • archive_all_inboxno sensitive capability
  • attach_fileno sensitive capability
  • create_projectno sensitive capability
  • create_project_noteno sensitive capability
  • create_project_note_commentno sensitive capability
  • create_taskno sensitive capability
  • create_task_commentno sensitive capability
Show 42 more tools ↓
  • delete_project_noteno sensitive capability
  • delete_project_note_commentno sensitive capability
  • delete_taskno sensitive capability
  • delete_task_commentno sensitive capability
  • detach_fileno sensitive capability
  • get_all_tagsno sensitive capability
  • get_feedno sensitive capability
  • get_inboxno sensitive capability
  • get_inbox_unread_countno sensitive capability
  • get_meno sensitive capability
  • get_membersno sensitive capability
  • get_my_projectsno sensitive capability
  • get_my_tasksno sensitive capability
  • get_my_tasks_countno sensitive capability
  • get_projectno sensitive capability
  • get_project_activityno sensitive capability
  • get_project_milestonesno sensitive capability
  • get_project_noteno sensitive capability
  • get_project_note_activity_logno sensitive capability
  • get_project_note_childrenno sensitive capability
  • get_project_note_commentsno sensitive capability
  • get_project_note_historyno sensitive capability
  • get_project_notesno sensitive capability
  • get_project_statusesno sensitive capability
  • get_project_usersno sensitive capability
  • get_projectsno sensitive capability
  • get_space_infono sensitive capability
  • get_taskno sensitive capability
  • get_task_activity_logno sensitive capability
  • get_task_commentsno sensitive capability
  • get_task_historyno sensitive capability
  • get_task_subtasksno sensitive capability
  • get_tasksno sensitive capability
  • invite_to_spaceno sensitive capability
  • update_inboxno sensitive capability
  • update_meno sensitive capability
  • update_projectno sensitive capability
  • update_project_noteno sensitive capability
  • update_project_note_commentno sensitive capability
  • update_taskno sensitive capability
  • update_task_commentno sensitive capability
  • update_user_roleno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

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
v1.0.7 latest A 96/100 3 1.13.0 2026-09-08

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/bellx2-repsona-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/bellx2-repsona-mcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/bellx2-repsona-mcp-server"><img src="https://mcptrustchecker.com/registry/bellx2-repsona-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/bellx2-repsona-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 @bellx2/repsona-mcp-server --online

Use the free API → How scoring works

More in Productivity & Workflow