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/arclabs-studio/ARCLinearGitHub-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/arclabs-studio/arclineargithub-mcp/arc-linear-github-mcp)<a href="https://agentmods.dev/mcp/arclabs-studio/arclineargithub-mcp/arc-linear-github-mcp"><img src="https://agentmods.dev/badge/mcp/arclabs-studio/arclineargithub-mcp/arc-linear-github-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/arclabs-studio/arclineargithub-mcp/arc-linear-github-mcp"><img src="https://agentmods.dev/badge/mcp/arclabs-studio/arclineargithub-mcp/arc-linear-github-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
arc-linear-github-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
{
"arc-linear-github-mcp": {
"command": "uvx",
"args": [
"arc-linear-github-mcp"
],
"env": {
"LINEAR_API_KEY": "",
"GITHUB_TOKEN": "",
"GITHUB_ORG": "",
"DEFAULT_PROJECT": "",
"DEFAULT_REPO": "",
"LINEAR_WORKSPACES": ""
}
}
}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 · 16 lines scan A 4bf1ec03068a
arc-linear-github-mcp is an MCP server published in the GitHub repository arclabs-studio/ARCLinearGitHub-MCP (0 stars, last pushed 4mo 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
okffs
MCP server connecting Claude Code to GitHub for an issue to branch to PR to close workflow. Runs locally from the @neturely/okffs npm package. Needs 3 environment variables to run.
baron
Let your coding agent write to your work tracker: issues, branches, PRs and CI, one contract. Runs locally from the @lonca/baron-mcp-server npm package.
linear-mcp-lean
Self-hosted MCP server wrapping Linear's GraphQL API with response-shape control — lean reads, minimal write acks, drop-in tool names. Runs locally from the linear-mcp-lean npm package.
gitlab
GitLab MCP — wraps the GitLab REST API v4 (BYO API key). Remote server at gateway.pipeworx.io.
linear
Linear MCP — wraps the Linear GraphQL API (OAuth). Remote server at gateway.pipeworx.io.
mcp-git-issue-priority
MCP server for GitHub issue prioritization and workflow management. Runs locally from the mcp-git-issue-priority npm package.