Project Context
NPM · @SANDOVALRR/PROJECT-CONTEXT-MCP · SCANNED SEP 20
Safely manage repository-scoped issues across Linear, GitHub Issues, and Jira Cloud.
Available components
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 59 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 Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
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
claude mcp add sandovalrr-project-context -- npx -y @sandovalrr/project-context-mcp
{
"mcpServers": {
"sandovalrr-project-context": {
"command": "npx",
"args": [
"-y",
"@sandovalrr/project-context-mcp"
]
}
}
} {
"servers": {
"sandovalrr-project-context": {
"command": "npx",
"args": [
"-y",
"@sandovalrr/project-context-mcp"
]
}
}
} codex mcp add sandovalrr-project-context -- npx -y @sandovalrr/project-context-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sandovalrr-project-context": {
"type": "local",
"command": [
"npx",
"-y",
"@sandovalrr/project-context-mcp"
],
"enabled": true
}
}
} openclaw mcp add sandovalrr-project-context --command npx --arg -y --arg @sandovalrr/project-context-mcp
mcp_servers:
sandovalrr-project-context:
command: "npx"
args: ["-y", "@sandovalrr/project-context-mcp"] {
"McpServers": {
"sandovalrr-project-context": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@sandovalrr/project-context-mcp"
]
}
}
} assistant mcp add sandovalrr-project-context -t stdio -c npx -a -y @sandovalrr/project-context-mcp
{
"mcpServers": {
"sandovalrr-project-context": {
"command": "npx",
"args": [
"-y",
"@sandovalrr/project-context-mcp"
]
}
}
} 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
- Security disclosure: unverified → pass ▲ functional
- 16 Sept 26 −3
- Security disclosure: pass → unverified ▼ functional
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +2
- Security disclosure: unverified → pass ▲ functional
- 13 Sept 26 −1
- Security disclosure: pass → unverified ▼ functional
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 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.
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 20 Sept 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 | 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 →
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 →
apply_issue_change Apply previewed issue change ~55
Apply a previously previewed external issue change after revalidating repository, config, identity, and issue version.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Git working directory; defaults to the server process cwd |
| token | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| error | object | – | – |
| result | object | – | – |
No examples provided.
get_issue Get issue ~82
Get one issue using deterministic URL, qualified-reference, or identifier routing.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Git working directory; defaults to the server process cwd |
| include_relations | boolean | – | Include target-validated parent, subissue, blocking, related, and duplicate relations |
| provider | string | – | Explicit configured provider alias |
| reference | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| error | object | – | – |
| result | object | – | – |
No examples provided.
get_issue_capabilities Get issue capabilities ~79
Get supported issue fields, exact reusable options, configured canonical statuses, defaults, and named creation presets for the configured target.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | Get capabilities from all configured providers only when explicitly true |
| cwd | string | – | Git working directory; defaults to the server process cwd |
| provider | string | – | Explicit configured provider alias |
| Name | Type | Req | Description |
|---|---|---|---|
| error | object | – | – |
| result | array | – | – |
No examples provided.
list_issue_comments 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.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Git working directory; defaults to the server process cwd |
| limit | integer | – | – |
| provider | string | – | Explicit configured provider alias |
| reference | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| error | object | – | – |
| result | object | – | – |
No examples provided.
list_issues 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.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | List from all configured providers only when explicitly true |
| cwd | string | – | Git working directory; defaults to the server process cwd |
| include_archived | boolean | – | Include archived issues when the configured provider supports it |
| limit | integer | – | – |
| parent | string | – | List direct subissues of this target-scoped parent issue |
| provider | string | – | Explicit configured provider alias |
| statuses | array | – | Unique canonical statuses; omission lists all statuses |
| Name | Type | Req | Description |
|---|---|---|---|
| error | object | – | – |
| result | array | – | – |
No examples provided.
list_users List assignable users ~85
List active users assignable to issues in the configured target. Pass a returned assignee value unchanged when preparing a create or update.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | List from all configured providers only when explicitly true |
| cwd | string | – | Git working directory; defaults to the server process cwd |
| limit | integer | – | – |
| provider | string | – | Explicit configured provider alias |
| Name | Type | Req | Description |
|---|---|---|---|
| error | object | – | – |
| result | array | – | – |
No examples provided.
prepare_issue_change Preview issue change ~153
Resolve, validate, and preview an issue write. Returns a token valid for ten minutes; does not change the external provider.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | – |
| comment_id | string | – | Edit this existing comment after verifying it belongs to the target issue |
| cwd | string | – | Git working directory; defaults to the server process cwd |
| fields | object | – | – |
| identifier | string | – | – |
| operation | string | yes | – |
| parent_comment_id | string | – | Reply to this comment after verifying it belongs to the target issue |
| preset | string | – | – |
| provider | string | – | Explicit configured provider alias |
| status | string | – | – |
| target_url | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| error | object | – | – |
| result | object | – | – |
No examples provided.
resolve_project_context Resolve project issue context ~37
Resolve the configured issue providers for the current Git repository.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Git working directory; defaults to the server process cwd |
| Name | Type | Req | Description |
|---|---|---|---|
| error | object | – | – |
| result | object | – | – |
No examples provided.
search_issue_options 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.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | Search all configured providers only when explicitly true |
| cwd | string | – | Git working directory; defaults to the server process cwd |
| field | string | yes | – |
| limit | integer | – | – |
| provider | string | – | Explicit configured provider alias |
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| error | object | – | – |
| result | array | – | – |
No examples provided.
search_issues Search issues ~92
Search issue titles and descriptions in the default or explicitly selected configured provider.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | Search all configured providers only when explicitly true |
| cwd | string | – | Git working directory; defaults to the server process cwd |
| limit | integer | – | – |
| provider | string | – | Explicit configured provider alias |
| query | string | yes | Title/description text only; not a status or structured filter |
| Name | Type | Req | Description |
|---|---|---|---|
| error | object | – | – |
| result | array | – | – |
No examples provided.
search_users Search assignable 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.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | Search all configured providers only when explicitly true |
| cwd | string | – | Git working directory; defaults to the server process cwd |
| limit | integer | – | – |
| provider | string | – | Explicit configured provider alias |
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| error | object | – | – |
| result | array | – | – |
No examples provided.
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 94 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 20 September 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.