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.

io.github.craft-agent/github-tools

NPM · @CRAFTSAMO/GITHUB-TOOLS

GitHub tools for coding agents: issues, boards, pull requests, repositories, releases and Actions.

+3 this week 83 Trust /100

Last scanned (21 hours ago)

Scores higher than 73% of npm servers

Category Version Control

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 & Transparency87
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to craft-agent/github-tools). View diagnostics → Pass
  • License check failed: the license (LicenseRef-AGPL-3.0-Commons-Clause) isn't a recognized OSI-approved license. See how to fix → Fail
  • Actively maintained (last published 4 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability56
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 14518 tokens (~453/item across 32 items; 32 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 Management57
  • Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 96% 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
  • All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 32 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 20 Nov 26 +1

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

  • 18 Nov 26 +1

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

  • 16 Nov 26 0
    • Stability: 0.37 → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
    • Package version: 0.15.0 → 0.16.0 functional
    • Package version: 0.15.0 → 0.15.1 functional
  • 15 Nov 26 +1

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

  • 14 Nov 26 +11
    • Known CVEs: unverified → pass ▲ security
    • Dependency health: unverified → pass ▲ functional
  • 13 Nov 26 +8
    • Stability: 0.27 → unverified ▼ security
    • Known CVEs: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Malware scan: unverified → pass ▲ security
    • Install scripts: fail → pass ▲ security
    • The code this package runs automatically changed: postinstall security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Dependency health: pass → unverified ▼ functional
    • First check of Schema quality: unverified functional
    • Package version: 0.13.0 → 0.15.0 functional
    • Package version: 0.13.0 → 0.14.0 functional
  • 12 Nov 26 −17
    • Malware scan: pass → unverified ▼ security
    • License: pass → fail ▼ functional
    • Licence: MIT → LicenseRef-AGPL-3.0-Commons-Clause functional
    • Package version: 0.12.0 → 0.13.0 functional
  • 11 Nov 26 +1
    • Package version: 0.11.0 → 0.12.0 functional
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 21 Nov 2026 · Analysed npm/@craftsamo/github-tools@0.16.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 craft-agent/github-tools
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/craft-agent/github-tools/.github/workflows/release-publish.yml@refs/heads/main
Rekor log index 3929606482
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:c550f3b4cb67b2b13b6003d32809edc09f0e27944c3c8287532bb7fd4f7cc5bc1a91e4b27b842140a2c607bc4ceb51a8e29144fc797079a4f031d1ebd

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 · 32 exposed · ~14,518 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
github_stack_unlink ~210

Take the pull requests out of a native stack, named by its number or by a pull request in it. Every unmerged pull request leaves (open, draft and closed ones); merged and queued ones stay in the stack, and remaining shows what is left, null when the stack is gone. The pull requests stay open with their branches and bases as they were, and nothing is deleted: github_stack_link can build the stack again. A pull request in no stack is left alone: nothing is sent and changed is false. A pull request is 12, #12, owner/repo#12 or its URL.

NameTypeReqDescription
prstring–A pull request in the stack. The pull request, as 12, #12, owner/repo#12 or its URL.
repostring–owner/name; defaults to the working tree's repository (its origin). Used for a bare number.
stackinteger–The stack's number (not a pull request's).
NameTypeReqDescription
changedbooleanyesFalse when the pull request was in no stack, or none of the stack's pull requests could leave.
foreignbooleanyes–
remaining–yesWhat is left of the stack (merged and queued pull requests stay); null when it is gone.
removedarrayyesThe pull requests that left the stack.
repostringyes–
stack_number–yesThe stack that was taken apart; null when the pull request was in none.

No examples provided.

Install

How do I install the io.github.craft-agent/github-tools MCP server?

io.github.craft-agent/github-tools runs locally as an npm package, launched with npx -y @craftsamo/github-tools. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @craftsamo/github-tools

# add to Claude Code
claude mcp add craft-agent-github-tools -- npx -y @craftsamo/github-tools
Common questions

What is the io.github.craft-agent/github-tools MCP server?

io.github.craft-agent/github-tools is an MCP server listed in the public MCP registry as io.github.craft-agent/github-tools. GitHub tools for coding agents: issues, boards, pull requests, repositories, releases and Actions. This page covers its npm package (@craftsamo/github-tools).

Is the io.github.craft-agent/github-tools MCP server safe to use?

io.github.craft-agent/github-tools scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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 io.github.craft-agent/github-tools MCP server expose?

io.github.craft-agent/github-tools exposes 32 tools: github_issue_read, github_issue_create, github_issue_edit, github_issue_comment, github_issue_close, and 27 more. Their descriptions and schemas cost roughly 14,518 tokens of context every time the server is loaded.

Is the io.github.craft-agent/github-tools MCP server still maintained?

io.github.craft-agent/github-tools is still listed as active in the MCP registry. We last reached this channel on 21 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 io.github.craft-agent/github-tools MCP server under?

io.github.craft-agent/github-tools declares the LicenseRef-AGPL-3.0-Commons-Clause licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.

What did VerifyMCP test on the io.github.craft-agent/github-tools MCP server?

VerifyMCP ran 16 checks on io.github.craft-agent/github-tools, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.