Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/nks-hub/nks-osticket-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/nks-hub/nks-osticket-mcp/osticket-mcp)<a href="https://agentmods.dev/mcp/nks-hub/nks-osticket-mcp/osticket-mcp"><img src="https://agentmods.dev/badge/mcp/nks-hub/nks-osticket-mcp/osticket-mcp/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/nks-hub/nks-osticket-mcp/osticket-mcp"><img src="https://agentmods.dev/badge/mcp/nks-hub/nks-osticket-mcp/osticket-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
osticket-mcp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{ "osticket-mcp": { "command": "npx", "args": [ "-y", "@nks-hub/osticket-mcp" ] } }
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 9 lines scan A 49d0e342d049
osticket-mcp is an MCP server published in the GitHub repository nks-hub/nks-osticket-mcp (3 stars, last pushed 17d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
simple-support-system-mcp
MCP server for the Simple Support System helpdesk API: read, answer and move tickets. Runs locally from the simple-support-system-mcp npm package. Needs 3 environment variables to run.
amazing-clickup-mcp
MCP server for the ClickUp public API (v2 + v3, stdio). Runs locally from the amazing-clickup-mcp Python package.
xalantis-mcp
MCP server for Xalantis — tickets, CRM, contracts, projects and the whole public API from Claude, Cursor, and other AI tools. Runs locally from the @xalantis/mcp-server npm package. Needs 2 environment variables to run.
harvest-mcp
Model Context Protocol server for Harvest API integration. Runs locally from the @standardbeagle/harvest-mcp npm package.
mcp-server
Taskade projects, tasks and AI agents. Hosted OAuth server or local stdio package. Runs locally from the @taskade/mcp-server npm package. Needs 1 environment variable to run.
lain
High-performance knowledge graph MCP server for AI coding agents with semantic search. Runs locally from the @spuentesp/lain-mcp npm package.