74
/ 100
11 days ago
glama

gitea-mcp

MCP server for managing Gitea repositories via the Gitea API, enabling operations on issues, comments, labels, milestones, and repository info.

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.

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 1 credential: GITEA_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// required environment variables
This server reads these from process.env. You'll be asked to provide them before it can run.
configGITEA_BASE_URLYes Gitea instance URL (e.g. https://gitea.example.com)
configGITEA_DEFAULT_OWNERNo Default repository owner — skip passing owner on every call
configGITEA_DEFAULT_REPONo Default repository name — skip passing repo on every call
🔐 secretGITEA_TOKENYes Gitea API access token
// full audit trail
The full breakdown of what we checked, the deductions that landed, the network hosts, the dependency advisories, and concrete fix guidance is available to verified publishers.
// improvement guidance — verified publishers only
We have 5 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 Score](https://m8ven.ai/badge/mcp/amonstack-gitea-mcp-htdqfs)](https://m8ven.ai/mcp/amonstack-gitea-mcp-htdqfs)
commit: c96d1ea8d0c8e753d2c99b51662fc19a227ff0fb
code hash: e9a1919620618328c6e84d320172f4fb82fa06316f06c321e0c7eb431793ef6c
verified: 7/1/2026, 10:05:22 AM
view raw JSON →