MCP server · trust report

io.github.usemycontext/usemycontext

Passes 4 checks with a soft flag on injection surface — worth a look, not a dealbreaker.

Publisher
io.github.usemycontext
Repository
github.com/usemycontext/usemycontext
Install
remote only
Versions
2
MCP revision
2025-06-18 · superseded
Inspected
5 of 6 checks · 85%
Scored
2026-09-01 · rubric 1.0.0

What we checked

Six static checks, weighted by risk. Every result reflects only what could be observed in the published package and repository — never intent.

6 checks4 clean1 flagged1 not inspected
  • Injection surface

    warn25% of grade

    Tool descriptions/manifest scanned for instruction-injection patterns (imperatives at the model, hidden text, 'ignore previous', data-exfil URLs).

    tool "info" description: bare 'IMPORTANT:' prose in a description (tag form is high-confidence; prose is warn).

  • Supply chain

    pass25% of grade

    Package provenance: namespace verification, repo linkage, maintainer count, account age, postinstall scripts, typosquat distance.

    repository linkage verified

  • Credential hygiene

    pass15% of grade

    How the server takes secrets (env vs plaintext config vs hardcoded); secrets appearing in tool schemas.

    No hardcoded secrets, secret-shaped tool parameters, or leaked keys found. PASS = no static red flag; static analysis cannot prove the code honors env-based secret handling at runtime.

  • Permission scope

    unscannable15% of grade

    Declared tools vs. breadth (filesystem, network, exec); flags shell-exec and unbounded filesystem access.

    No source files, package.json, or pyproject were fetched; cannot infer capability scope.

  • Version behavior

    pass10% of grade

    Diff of tool definitions between versions; new permissions or changed descriptions in a patch release (the postmark-mcp class).

    vs prior 1.0.0 (minor bump): tool "profile" description changed (wording only, no injection pattern); tool "ask_docs" description changed (wording only, no injection pattern); tool "suggest_update" description changed (wording only, no injection pattern). Low-severity drift (informational; consistent with the version bump).

  • Transport config

    pass10% of grade

    Remote servers: TLS and auth mode (none/token/OAuth). Local servers: whether the manifest indicates it phones home.

    remote endpoint "https://mcp.usemycontext.ai/mcp" uses TLS (https); remote endpoint uses OAuth (strongest auth mode)

Version history

Each release plotted by grade against the safe line at B. A version that sinks below the line has lost its trusted standing — the shape of a rug-pull.

VersionPublishedGradeScoreInspectedChange
v1.1.0 · current2026-08-23 B87.55/6 · 85%±0
v1.0.02026-07-19 B87.54/6 · 75%