SandboxAPIs
NPM · @SANDBOXAPIS/MCP
Drop-in read-only replicas of GitHub, Jira, Slack and 22 more, preloaded with one fake company.
Available components
Last scanned (4 hours ago)
Scores higher than 45% of npm servers
Category Version Control
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1380 tokens (~138/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 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
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 +15
- Malware scan: unverified → pass ▲ security
- 3 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.3.20 → 0.3.21 functional
- 2 Nov 26 +1
- Stability: 0.97 → pass security
- 1 Nov 26 −1
- Stability: pass → 0.97 functional
- 28 Oct 26 +15
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Package version: 0.3.19 → 0.3.20 functional
- 27 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.3.17 → 0.3.19 functional
- 26 Oct 26 +1
- Stability: 0.97 → pass security
- 25 Oct 26 −1
- Stability: pass → 0.97 functional
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 5 Nov 2026 · Analysed npm/@sandboxapis/mcp@0.3.21
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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 →
check_budget Check the remaining request budget ~140
Costs nothing. Call it before any loop of more than a handful of requests. Returns this server's real hourly window (limit, remaining, when it resets) read from the provider's own budget endpoint, which is exempt from the budget it reports, plus whether a key is set and where to raise the limit. The window is ONE bucket per caller shared across every provider host, so the numbers apply to all of them.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | – | The provider host you are about to call, one of the ids orient lists, e.g. 'github'. Optional: the budget is one shared window, so the numbers are the same for every provider. |
No output schema declared.
No examples provided.
get_pull_request Get a pull/merge request with its reviews ~157
Fetch one PR (GitHub) / MR (GitLab) plus its reviews (GitHub) / approvals (GitLab). Returns both in one result; each carries provider-form ids for cross-referencing.
| Name | Type | Req | Description |
|---|---|---|---|
| number | integer | yes | The pull request number as the provider shows it (the merge request iid on GitLab), a positive integer, e.g. 47. |
| provider | string | yes | The git host to read from, one of the ids orient lists: 'github', 'gitlab', 'bitbucket' or 'ado', e.g. 'github'. |
| repo | string | – | The repository name without the organisation, e.g. 'parthenon', the flagship repo, which is used when omitted. |
No output schema declared.
No examples provided.
get_repository Get a repository ~102
Fetch one repository by name (default: the flagship repo). Provider-shaped, with provider-form ids.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | yes | The git host to read the repository from, one of the ids orient lists: 'github', 'gitlab', 'bitbucket' or 'ado', e.g. 'github'. |
| repo | string | – | The repository name without the organisation, e.g. 'parthenon', the flagship repo, which is used when omitted. |
No output schema declared.
No examples provided.
get_snapshot Get a pinned snapshot hostname ~83
Return the pinned, reproducible hostname for a provider. Point your client's base URL at it for drift-free CI. A snapshot regenerates byte-identically on every request.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | yes | The provider to pin, one of the ids orient lists, e.g. 'github'; the newest frozen generation for it is returned, with any older ones listed beside it. |
No output schema declared.
No examples provided.
get_user Get a user ~93
Fetch a user by login/username. Provider-shaped, with provider-form ids.
| Name | Type | Req | Description |
|---|---|---|---|
| login | string | yes | The user's login (GitHub) or username (GitLab), e.g. 'athena'. |
| provider | string | yes | The git host to read the user from, one of the ids orient lists: 'github', 'gitlab', 'bitbucket' or 'ado', e.g. 'github'. |
No output schema declared.
No examples provided.
list_issues List issues ~154
List a repo's issues. Optional state filter (open/closed/all).
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | yes | The provider to read issues from, one of the ids orient lists: 'github' or 'gitlab' (per repository), or 'jira' or 'linear' (across the whole tracker), e.g. 'jira'. |
| repo | string | – | The repository name without the organisation, e.g. 'parthenon', the flagship repo, which is used when omitted; ignored by 'jira' and 'linear'. |
| state | string | – | Filter by state, one of 'open', 'closed' or 'all', e.g. 'closed'; when omitted the provider's own default applies. |
No output schema declared.
No examples provided.
list_pull_requests List pull requests / merge requests ~147
List a repo's pull requests (GitHub) or merge requests (GitLab). Optional state filter.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | yes | The git host to read from, one of the ids orient lists: 'github', 'gitlab', 'bitbucket' or 'ado', e.g. 'gitlab' for merge requests. |
| repo | string | – | The repository name without the organisation, e.g. 'parthenon', the flagship repo, which is used when omitted. |
| state | string | – | Filter by state, one of 'open', 'closed', 'merged' or 'all', e.g. 'merged'; when omitted the provider's own default applies. |
No output schema declared.
No examples provided.
list_repositories List the org's repositories ~80
List repositories for the universe's org. Results are identical to the provider's REST API and carry provider-form ids (node_id / numeric id).
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | yes | The git host to list repositories from, one of the ids orient lists: 'github', 'gitlab', 'bitbucket' or 'ado', e.g. 'github'. |
No output schema declared.
No examples provided.
orient Orient in the SandboxAPIs universe ~183
START HERE. Returns everything needed to use SandboxAPIs with no docs: the universe/theme, every API surface and its base URL (git hosts and issue trackers), live-vs-snapshot modes and how to pin, the org and its teams/repos, notable entry points (each with a ready-to-run REST path), where the coverage manifest lives, and this server's access block: whether a key is set and how many requests are left this hour. Writes: this server is READ-ONLY, including for a scratch-enabled key. The scratch layer (a per-key, 24-hour overlay: GitHub issues and issue comments, Jira comments and transitions, and Slack messages into existing channels) is a REST feature, so use the GitHub, Jira or Slack base URL above with your key for it, and expect the tools here to answer from the shared data set alone.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_commits_by_author Search commits by author ~167
Find commits authored by a given login in a repo. Returns SHAs (identical across GitHub and GitLab, invariant #5) with a REST path to fetch each, so you can cross-reference against either provider.
| Name | Type | Req | Description |
|---|---|---|---|
| author | string | yes | The author's login, matched without regard to case, e.g. 'athena'. |
| provider | string | – | The git host whose REST path each returned commit carries, 'github', 'gitlab', 'bitbucket' or 'ado', defaulting to 'github'; commits are read from GitHub either way, because the SHAs are identical on… |
| repo | string | – | The repository name without the organisation, e.g. 'parthenon', the flagship repo, which is used when omitted. |
No output schema declared.
No examples provided.
How do I install the SandboxAPIs MCP server?
SandboxAPIs runs locally as an npm package, launched with npx -y @sandboxapis/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 · @sandboxapis/mcp
claude mcp add dev-sandboxapis-mcp -- npx -y @sandboxapis/mcp
What is the SandboxAPIs MCP server?
SandboxAPIs is an MCP server listed in the public MCP registry as dev.sandboxapis/mcp. Drop-in read-only replicas of GitHub, Jira, Slack and 22 more, preloaded with one fake company. This page covers its npm package (@sandboxapis/mcp).
Is the SandboxAPIs MCP server safe to use?
SandboxAPIs scores 73 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. 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 SandboxAPIs MCP server expose?
SandboxAPIs exposes 10 tools: orient, check_budget, list_repositories, get_repository, list_pull_requests, and 5 more. Their descriptions and schemas cost roughly 1,306 tokens of context every time the server is loaded.
Is the SandboxAPIs MCP server still maintained?
SandboxAPIs is still listed as active in the MCP registry. We last reached this channel on 5 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 SandboxAPIs MCP server under?
SandboxAPIs declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.