Gitea MCP Tool (SupenBysz/gitea-mcp-tool) is an MCP server listed on the M8ven Trust Index. It scores 50 out of 100, grade D. It declares 22 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
D
Caution
50/100

Gitea MCP Tool

Enables AI assistants to interact with Gitea repositories through intelligent tools for issue/PR management, workflow analysis, compliance checking, and content generation, plus 200+ CLI commands for complete CRUD operations.

→ SupenBysz/gitea-mcp-tool· listed on glama

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

SupenBysz

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Known vulnerabilities in dependencies: 1 critical, 3 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 3 credentials: GITEA_API_TOKEN, GITEA_PASSWORD, GITEA_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes22 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

gitea_init

Initialize project configuration files (.gitea-mcp.json). Auto-detects Git repository info if available.

gitea_mcp_upgrade

Upgrade Gitea MCP tool to the latest version. Downloads and installs from the latest release.

gitea_context_get

Get current default context (owner, repo, org, project)

gitea_context_set

Set default context for subsequent operations. All parameters are optional.

gitea_user_current

Get information about the currently authenticated user

gitea_compliance_check_branch

Check if branch name complies with naming conventions. Returns compliance status and suggestions.

gitea_compliance_check_commit

Check if commit message complies with Conventional Commit format. Can check by SHA or message directly.

gitea_compliance_check_pr

Check if PR description complies with format requirements (sections, issue links, etc.).

gitea_compliance_check_all

Run comprehensive compliance check on branch, commits, and/or PR. Returns detailed report.

gitea_compliance_init

Initialize compliance configuration file (.gitea/compliance.yaml) with default rules.

gitea_issue_create

Create a new issue. Use this tool for AI-assisted issue creation with smart content generation.

gitea_pr_create

Create a new pull request. Use this tool for AI-assisted PR creation with smart content generation.

gitea_workflow_init

Initialize Issue workflow configuration for a project. Generates .gitea/issue-workflow.yaml with labels, board columns, and automation rules based on project type.

gitea_workflow_load_config

Load and parse the workflow configuration from .gitea/issue-workflow.yaml. Returns the parsed config and validation results.

gitea_workflow_sync_labels

Sync repository labels based on workflow configuration. Creates status/*, priority/*, type/* and other labels defined in the config.

gitea_workflow_sync_board

Create or update project board with columns mapped to status labels. Columns: Backlog, In Progress, Review, Testing, Done.

gitea_workflow_check_issues

Check all open issues against workflow rules. Identifies missing labels, conflicts, and provides suggestions for improvement.

gitea_workflow_infer_labels

Infer labels for an issue based on title and body content. Uses keyword matching and pattern recognition to suggest type, priority, and area labels.

gitea_workflow_check_blocked

Detect issues that are blocked or exceeding SLA. Checks for stale issues based on priority-specific time limits.

gitea_workflow_escalate_priority

Automatically escalate priority for aged issues. P3→P2 after 30 days, P2→P1 after 14 days, P1→P0 after 3 days. Security issues are always P0.

gitea_workflow_sync_status

Synchronize issue status labels with project board column positions. Supports label-to-board, board-to-label, or bidirectional sync.

gitea_workflow_generate_report

Generate a comprehensive workflow report including issue statistics, health score, and recommendations. Output in JSON and Markdown formats.

// known CVEs in dependencies1 critical3 high3 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

criticalvitest@2.1.9GHSA-5xrq-8626-4rwp

When Vitest UI server is listening, arbitrary file can be read and executed

high@modelcontextprotocol/sdk@1.23.0GHSA-345p-7cg4-v4c7

@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse

high@modelcontextprotocol/sdk@1.23.0GHSA-8r9q-7v3j-jr4g

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

high@modelcontextprotocol/sdk@1.23.0GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

lowuuid@13.0.0GHSA-w5hq-g745-h8pq

uuid: Missing buffer bounds check in v3/v5/v6 when buf is provided

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
🔐 secretGITEA_API_TOKEN在运行前，请在环境变量中提供 ，否则服务器会因缺少认证而启动失败。
configGITEA_BASE_URL
configGITEA_DEFAULT_ORG
configGITEA_DEFAULT_OWNER
configGITEA_DEFAULT_PROJECT
configGITEA_DEFAULT_REPO
🔐 secretGITEA_PASSWORD
configGITEA_SERVER_URL
configGITEA_TIMEOUT
🔐 secretGITEA_TOKEN
configGITEA_URL
configGITEA_USERNAME
configLOG_LEVEL
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

22/22 tools missing one or more hints — gitea_init (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); gitea_mcp_upgrade (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); gitea_context_get (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +19 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool inputs are validated

20/22 tool handlers declare input schemas (91%)

Declare an inputSchema with zod/joi/yup on every tool definition.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tool test coverage

Only 0/22 tools referenced in tests (0%)

Write tests that reference each tool by name so every tool has at least one test.

Shell command execution

18 calls in production code run through a shell (src/utils/git-detector.ts:63, src/utils/git-detector.ts:173, src/utils/git-detector.ts:194)

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Production dependencies are patched

0 critical, 3 high severity in production deps — @modelcontextprotocol/sdk@1.23.0 (high), @modelcontextprotocol/sdk@1.23.0 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Dev dependencies

1 critical/high in dev-only deps (does not ship to users)

Upgrade dev dependencies when convenient.

Dependency freshness

1/10 production deps stale: prompts@2023-10-21 (2.9y)

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 8 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/supenbysz/gitea-mcp-tool?variant=verified)](https://m8ven.ai/mcp/supenbysz/gitea-mcp-tool)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 714df440c5ca246c4e0fd48c1cefc1eaf3aec640
code hash: bf5499242c46168844ce176b30dd3da37080307a937eb92a612f150768073cdf
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client