mcp server
gittr-mcp
Git on Nostr via gittr.space: repos, push, issues, PRs, stars, bounties. Nostr identity (NIP-34).
Description as published by the maintainer. Source
- version 1.0.2
- active
active — Most recent push to the repository was 2026-08-06.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| GitHub stars | 1 | Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. | cumulative, all time | GitHub | |
| Last commit | 2026-08-06 | Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. | point in time | GitHub | |
| Open issues | 12 | Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. | as of fetch | GitHub | |
| Latest published version | 1.0.2 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-13 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-07-13 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | active | The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. | as of fetch | GitHub |
Where to get it
Related, by what their authors tagged them
-
SatRank — Lightning trust + audit oracle
— last commit 2026-07-13, shares autonomous-agents, bitcoin, lightning
Lightning trust + audit oracle. Score, pay, and audit L402 endpoints with Ed25519 receipts.
-
dev.forgesworn/bray
— last commit 2026-08-06, shares lightning, nostr
Trust-aware Nostr for AI agents -- 235 tools covering social, DMs, zaps, trust, and identity
-
ArcAgent MCP
— last commit 2026-03-08, shares bounties
ArcAgent MCP server for bounty discovery, workspace execution, and verified coding submissions.
-
io.github.archimedes-market/mcp-archimedes
— last commit 2026-07-12, shares bounties
Discover verified deep-tech engineering bounties from any AI agent.
-
Maximum Sats
— last commit 2026-03-10, shares bitcoin, nostr
Bitcoin AI + Nostr WoT scoring (12 tools). L402 pay-per-call. 50 free WoT/day.
-
dev.forgesworn/402-mcp
— last commit 2026-07-29, shares bitcoin, lightning
AI agents discover, pay for, and consume any Lightning-gated API autonomously
-
app.anakior/atlas-mind
— last commit 2026-06-30, shares git
Self-hosted git-native knowledge base with an MCP endpoint your AI reads, writes and rewinds
-
com.gitkraken/gk-cli
— last commit 2026-08-04, shares git
The GitKraken MCP Server for managing repos, PRs, issues across GitHub, GitLab, Bitbucket and more.
-
Oh My Posh Validator
— last commit 2026-08-06, shares git
Validate oh-my-posh configurations and segment snippets against the official schema.
-
io.github.Alejandro-M-P/git-courer
— last commit 2026-07-31, shares git
Full git MCP server for LLM agents — 17 tools, AST annotator, auto-backups, real plumbing.
These share tags the maintainers applied themselves, such as autonomous-agents, bitcoin, lightning, nostr. Common tags like "mcp" or "ai" are ignored for this: agreeing with six hundred other projects is not a similarity.
This is not a recommendation and not a test result. It is a map of what the authors said their work is about.
How the author describes it
Topics the maintainer set on GitHub: agent-tools, ai-agents, anthropic, autonomous-agents, bitcoin, bounties, claude, decentralized-git, git, gittr, lightning, llm-tools, mcp, model-context-protocol, nip-34, nostr, openai.
Bring your own setup
We take apart real AI setups every week and show what broke, what cost too much, and what the trace actually said. If you run agents on real work, that is where the useful conversation is.
Join ZBS AI Practice Lab