Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Project Context

NPM · @SANDOVALRR/PROJECT-CONTEXT-MCP

Safely manage repository-scoped issues across Linear, GitHub Issues, and Jira Cloud.

0 this week 95 Trust /100

Last scanned (19 hours ago)

Scores higher than 98% of npm servers

Category Project Management

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to sandovalrr/project-context). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 104 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability77
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1160 tokens (~105/item across 11 items; 11 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage90
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 63% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 0
    • Stability: 0.97 → pass security
  • 3 Nov 26 0
    • Stability: pass → 0.97 functional
  • 28 Oct 26 0
    • Stability: 0.97 → pass security
  • 27 Oct 26 0
    • Stability: pass → 0.97 functional
  • 21 Oct 26 0
    • Stability: 0.97 → pass security
  • 20 Oct 26 0
    • Stability: pass → 0.97 functional
  • 17 Oct 26 +2
    • Stability: 0.83 → pass security
  • 16 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 4 Nov 2026 · Analysed npm/@sandovalrr/project-context-mcp@0.4.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo sandovalrr/project-context
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/sandovalrr/project-context/.github/workflows/publish-release.yml@refs/tags/v0.4.0
Rekor log index 2219810644
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:20221d5e0fbefa63927a663e8d46326b8c9ca810b37c55414f0eb8a95fc9d0ff7d30c5c6a4803d9f4ffe78617b324e435b419e8987716d1390451e24c

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 11 exposed · ~1,004 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
apply_issue_change ~55

Apply a previously previewed external issue change after revalidating repository, config, identity, and issue version.

NameTypeReqDescription
cwdstring–Git working directory; defaults to the server process cwd
tokenstringyes–
NameTypeReqDescription
errorobject––
resultobject––

No examples provided.

get_issue ~82

Get one issue using deterministic URL, qualified-reference, or identifier routing.

NameTypeReqDescription
cwdstring–Git working directory; defaults to the server process cwd
include_relationsboolean–Include target-validated parent, subissue, blocking, related, and duplicate relations
providerstring–Explicit configured provider alias
referencestringyes–
NameTypeReqDescription
errorobject––
resultobject––

No examples provided.

get_issue_capabilities ~79

Get supported issue fields, exact reusable options, configured canonical statuses, defaults, and named creation presets for the configured target.

NameTypeReqDescription
allboolean–Get capabilities from all configured providers only when explicitly true
cwdstring–Git working directory; defaults to the server process cwd
providerstring–Explicit configured provider alias
NameTypeReqDescription
errorobject––
resultarray––

No examples provided.

list_issue_comments ~81

List target-scoped issue comments newest first. This returns comments only, not field history or a full activity timeline, and rejects GitHub pull requests.

NameTypeReqDescription
cwdstring–Git working directory; defaults to the server process cwd
limitinteger––
providerstring–Explicit configured provider alias
referencestringyes–
NameTypeReqDescription
errorobject––
resultobject––

No examples provided.

list_issues ~140

List issues ordered by most recently updated, optionally filtered by canonical status or target-scoped parent in the default, selected, or all configured providers.

NameTypeReqDescription
allboolean–List from all configured providers only when explicitly true
cwdstring–Git working directory; defaults to the server process cwd
include_archivedboolean–Include archived issues when the configured provider supports it
limitinteger––
parentstring–List direct subissues of this target-scoped parent issue
providerstring–Explicit configured provider alias
statusesarray–Unique canonical statuses; omission lists all statuses
NameTypeReqDescription
errorobject––
resultarray––

No examples provided.

list_users ~85

List active users assignable to issues in the configured target. Pass a returned assignee value unchanged when preparing a create or update.

NameTypeReqDescription
allboolean–List from all configured providers only when explicitly true
cwdstring–Git working directory; defaults to the server process cwd
limitinteger––
providerstring–Explicit configured provider alias
NameTypeReqDescription
errorobject––
resultarray––

No examples provided.

prepare_issue_change ~153

Resolve, validate, and preview an issue write. Returns a token valid for ten minutes; does not change the external provider.

NameTypeReqDescription
bodystring––
comment_idstring–Edit this existing comment after verifying it belongs to the target issue
cwdstring–Git working directory; defaults to the server process cwd
fieldsobject––
identifierstring––
operationstringyes–
parent_comment_idstring–Reply to this comment after verifying it belongs to the target issue
presetstring––
providerstring–Explicit configured provider alias
statusstring––
target_urlstring––
NameTypeReqDescription
errorobject––
resultobject––

No examples provided.

resolve_project_context ~37

Resolve the configured issue providers for the current Git repository.

NameTypeReqDescription
cwdstring–Git working directory; defaults to the server process cwd
NameTypeReqDescription
errorobject––
resultobject––

No examples provided.

search_issue_options ~101

Search target-scoped labels, priorities, issue types, cycles, or milestones. Pass returned option values unchanged and treat truncated results as incomplete.

NameTypeReqDescription
allboolean–Search all configured providers only when explicitly true
cwdstring–Git working directory; defaults to the server process cwd
fieldstringyes–
limitinteger––
providerstring–Explicit configured provider alias
querystringyes–
NameTypeReqDescription
errorobject––
resultarray––

No examples provided.

search_issues ~92

Search issue titles and descriptions in the default or explicitly selected configured provider.

NameTypeReqDescription
allboolean–Search all configured providers only when explicitly true
cwdstring–Git working directory; defaults to the server process cwd
limitinteger––
providerstring–Explicit configured provider alias
querystringyesTitle/description text only; not a status or structured filter
NameTypeReqDescription
errorobject––
resultarray––

No examples provided.

search_users ~99

Search active users assignable to issues by name, username, or email where the configured provider exposes those fields. Return every match and ask the user to choose when ambiguous.

NameTypeReqDescription
allboolean–Search all configured providers only when explicitly true
cwdstring–Git working directory; defaults to the server process cwd
limitinteger––
providerstring–Explicit configured provider alias
querystringyes–
NameTypeReqDescription
errorobject––
resultarray––

No examples provided.

Install

How do I install the Project Context MCP server?

Project Context runs locally as an npm package, launched with npx -y @sandovalrr/project-context-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @sandovalrr/project-context-mcp

# add to Claude Code
claude mcp add sandovalrr-project-context -- npx -y @sandovalrr/project-context-mcp
Common questions

What is the Project Context MCP server?

Project Context is an MCP server listed in the public MCP registry as io.github.sandovalrr/project-context. Safely manage repository-scoped issues across Linear, GitHub Issues, and Jira Cloud. This page covers its npm package (@sandovalrr/project-context-mcp).

Is the Project Context MCP server safe to use?

Project Context scores 95 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Project Context MCP server expose?

Project Context exposes 11 tools: resolve_project_context, list_issues, search_issues, list_users, search_users, and 6 more. Their descriptions and schemas cost roughly 1,004 tokens of context every time the server is loaded.

Is the Project Context MCP server still maintained?

Project Context is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Project Context MCP server under?

Project Context declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.