Is io.github.seayniclabs/mooring safe to use?

io.github.seayniclabs/mooring has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.

How do I install io.github.seayniclabs/mooring?

io.github.seayniclabs/mooring supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.

What can io.github.seayniclabs/mooring do?

io.github.seayniclabs/mooring provides 12 tools: repo_status, repo_log, repo_diff, repo_blame, repo_branches and 7 more. See the full tools list on the server page for descriptions and parameters.

What AI clients work with io.github.seayniclabs/mooring?

io.github.seayniclabs/mooring is compatible with claude-desktop, cursor, claude-code. It uses stdio and sse and http transport.

Is io.github.seayniclabs/mooring actively maintained?

io.github.seayniclabs/mooring is recently maintained — last commit was 67 days ago.

io.github.seayniclabs/mooring

mooring-mcp

Git and GitHub operations — repo status, diffs, branches, PRs, issues, and Actions.

12 tools GitHub PyPI

No known CVEs

No license

Maintained

Last commit 67d ago

Works with most clients

Transport: stdio, sse, http

12 tools · ~860 tok

Grade B · 0.4% of 200K ctx

MCPpedia last refreshed this data 3d ago

Edit this pageView history

Developer Tools

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio, sse, http · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "mooring": {
      "env": {
        "GITHUB_TOKEN": "your-github-personal-access-token"
      },
      "command": "mooring"
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-seayniclabs-mooring)](https://mcppedia.org/s/io-github-seayniclabs-mooring)

Read me

What io.github.seayniclabs/mooring does

Mooring lines for your code — Git and GitHub operations for AI tools.

Test This Server

Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.

uvx 'mooring-mcp' 2>&1 | head -1 && echo "✓ Server started successfully"

After testing, let us know if it worked:

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

78/100across 5 weighted dimensions

How we score →

0255075100

−22

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

Checked mooring-mcp against OSV.dev.

Inventory

Tools (12)

Click any tool to inspect its schema.

~860 tokens total

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.seayniclabs/mooring safe to use?: io.github.seayniclabs/mooring has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.
How do I install io.github.seayniclabs/mooring?: io.github.seayniclabs/mooring supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What can io.github.seayniclabs/mooring do?: io.github.seayniclabs/mooring provides 12 tools: repo_status, repo_log, repo_diff, repo_blame, repo_branches and 7 more. See the full tools list on the server page for descriptions and parameters.
What AI clients work with io.github.seayniclabs/mooring?: io.github.seayniclabs/mooring is compatible with claude-desktop, cursor, claude-code. It uses stdio and sse and http transport.
Is io.github.seayniclabs/mooring actively maintained?: io.github.seayniclabs/mooring is recently maintained — last commit was 67 days ago.

Similar servers

Others in developer-tools

View all →

XcodeBuildMCP97

XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.

6.1k 1

Supabase MCP Server97

Manage Supabase projects — databases, auth, storage, and edge functions

2.8k 4

XcodeBuildMCP97

A Model Context Protocol (MCP) server and CLI that provides tools for agent use when working on iOS and macOS projects.

6.1k 2

Context797

Context7 Platform -- Up-to-date code documentation for LLMs and AI code editors

59.8k 2

MCP Security Weekly

Get CVE alerts and security updates for io.github.seayniclabs/mooring and similar servers.

Community

Discussion

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?

Edit this pageView history

Developer Tools

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio, sse, http · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "mooring": {
      "env": {
        "GITHUB_TOKEN": "your-github-personal-access-token"
      },
      "command": "mooring"
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-seayniclabs-mooring)](https://mcppedia.org/s/io-github-seayniclabs-mooring)

Read me

What io.github.seayniclabs/mooring does

Mooring lines for your code — Git and GitHub operations for AI tools.

Test This Server

Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.

uvx 'mooring-mcp' 2>&1 | head -1 && echo "✓ Server started successfully"

After testing, let us know if it worked:

README

Mooring — Git & GitHub MCP Server

Mooring lines for your code — Git and GitHub operations for AI tools.

Mooring is an MCP server that gives AI assistants structured access to local Git repositories and the GitHub API. Local operations use GitPython (no subprocess calls). GitHub operations use the PyGithub library with token masking and rate limit handling built in.

Tools

Local Git

Tool	Description	Key Parameters
`repo_status`	Branch, ahead/behind, stash count, staged/unstaged/untracked files	`repo_path`
`repo_log`	Commit log with optional filters	`repo_path`, `max_count`, `author`, `since`, `path`, `search`
`repo_diff`	Unified diff — working tree, staged, or between refs	`repo_path`, `staged`, `from_ref`, `to_ref`
`repo_blame`	Git blame with optional line range	`repo_path`, `file_path`, `start_line`, `end_line`
`repo_branches`	All branches with tracking info, last commit, ahead/behind	`repo_path`
`repo_stash`	Stash operations: list, push, pop, apply	`repo_path`, `action`, `message`

GitHub

Tool	Description	Key Parameters
`gh_pr_list`	List pull requests	`repo`, `state`, `author`, `label`
`gh_pr_detail`	PR detail with reviews, comments, and check runs	`repo`, `number`
`gh_pr_create`	Create a pull request	`repo`, `title`, `body`, `head`, `base`, `labels`, `reviewers`
`gh_issues`	List, create, or update issues	`repo`, `state`, `action`, `title`, `body`, `number`
`gh_actions`	List recent GitHub Actions workflow runs	`repo`, `workflow`, `status`

Utility

Tool	Description	Key Parameters
`health`	Server version and status check	(none)

Installation

# PyPI
pip install mooring-mcp

# Isolated install
pipx install mooring-mcp

Usage

Run the server directly:

mooring

Claude Code

claude mcp add mooring -- mooring

Claude Desktop

Add to your Claude Desktop configuration (claude_desktop_config.json):

{
  "mcpServers": {
    "mooring": {
      "command": "mooring",
      "env": {
        "GITHUB_TOKEN": "your-github-personal-access-token"
      }
    }
  }
}

The GITHUB_TOKEN environment variable is required for all GitHub tools (gh_*). Local Git tools work without it.

Security

Path traversal protection — file paths are resolved and validated against the repository root before any operation
Symlink escape detection — symlinks that resolve outside the repository are rejected
Ref validation — Git refs are checked against a safe character pattern and verified to exist before use
Token masking — error messages are scrubbed for GitHub token patterns (ghp_*, gho_*, github_pat_*) before being returned
Rate limit handling — GitHub 403 responses are caught and surfaced as clear messages instead of raw exceptions

Development

git clone https://github.com/seayniclabs/mooring.git
cd mooring
python -m venv .venv && source .venv/bin/activate
pip install -e ".[test]"
python -m pytest tests/ -q

Using with a Gateway

If you're running multiple MCP servers, route them through a gateway like tbxark/mcp-proxy to manage all child processes from a single persistent service. The proxy handles process lifecycle, centralized config, and crash recovery — each server still gets its own SSE endpoint but you manage everything from one config file instead of scattered Claude Code entries.

For a full walkthrough of how this works in practice, see The Hidden Cost of a Loaded MCP Stack on charlieseay.com.

License

MIT

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

78/100across 5 weighted dimensions

How we score →

0255075100

−22

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

Checked mooring-mcp against OSV.dev.

Inventory

Tools (12)

Click any tool to inspect its schema.

~860 tokens total

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.seayniclabs/mooring safe to use?: io.github.seayniclabs/mooring has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.
How do I install io.github.seayniclabs/mooring?: io.github.seayniclabs/mooring supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What can io.github.seayniclabs/mooring do?: io.github.seayniclabs/mooring provides 12 tools: repo_status, repo_log, repo_diff, repo_blame, repo_branches and 7 more. See the full tools list on the server page for descriptions and parameters.
What AI clients work with io.github.seayniclabs/mooring?: io.github.seayniclabs/mooring is compatible with claude-desktop, cursor, claude-code. It uses stdio and sse and http transport.
Is io.github.seayniclabs/mooring actively maintained?: io.github.seayniclabs/mooring is recently maintained — last commit was 67 days ago.