# io.github.arbadacarbaYK/gittr-mcp

Git on Nostr via gittr.space: repos, push, issues, PRs, stars, bounties. Nostr identity (NIP-34).

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the content rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 1.0.2
- **Author:** io.github.arbadacarbaYK
- **License:** Unknown
- **Source:** https://github.com/arbadacarbaYK/gittr-mcp

## Trust

60/100 (B), scored on the content rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: clean
- Obfuscation scan: clean
- Evidence age: 14 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-08-15T01:47:45.380Z
- **Version scanned:** HEAD
- **CVEs:** no coverage — this entry has no package coordinates to query OSV against, so "no known CVEs" is NOT asserted for it.

## Tools

40 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `bitcoin`
- `lightning`
- `nostr`
- `defi`
- `tools`
- `cli`
- `mobile`
- `listRepos`
- `getRepo`
- `resolveRepoByNostrId`
- `searchRepos`
- `findReposBySource`
- `findReposByGithub`
- `myRepos`
- `pushToBridge`
- `publishRepoAnnouncement`
- `publishRepoState`
- `createRepo`
- `describeAgentAuth`
- `setupTestKeypair`
- `forkRepo`
- `mirrorRepo`
- `listBounties`
- `getFile`
- `addCollaborator`
- `listIssues`
- `createIssue`
- `listIssueComments`
- `createIssueComment`
- `listPRComments`
- `createPRComment`
- `listPRs`
- `createPR`
- `createPRViaGittrCLI`
- `getPublicKey`
- `loadCredentials`
- `submitBounty`
- `starRepo`
- `unstarRepo`
- `listStars`

## Install

This entry has no npm package and no hosted endpoint, so there is nothing for an MCP client to launch or connect to. It is indexed as source only.

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: read-only tool surface.
- Floor 3, ceiling 33 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/io.github.arbadacarbaYK%2Fgittr-mcp
- Install plan: https://forgeregistry.com/api/v1/packages/io.github.arbadacarbaYK%2Fgittr-mcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/io.github.arbadacarbaYK%2Fgittr-mcp
- HTML page: https://forgeregistry.com/registry/io.github.arbadacarbaYK%2Fgittr-mcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.