Gitingest-MCP

Created By
opengiga year ago
Overview

what is Gitingest-MCP?

Gitingest-MCP is a server designed for the Gitingest project, enabling clients to extract detailed information about GitHub repositories efficiently.

how to use Gitingest-MCP?

To use Gitingest-MCP, install it via Smithery or GitHub, and configure your MCP client to connect to the Gitingest-MCP server.

key features of Gitingest-MCP?

  • Extract repository summaries
  • Retrieve project directory structures
  • Access file content from GitHub repositories

use cases of Gitingest-MCP?

  1. Quickly obtaining summaries of GitHub projects.
  2. Analyzing the structure of repositories for better understanding.
  3. Fetching specific file contents for review or modification.

FAQ from Gitingest-MCP?

  • What is the purpose of Gitingest-MCP?

It serves as a bridge for MCP clients to interact with GitHub repositories and extract relevant information.

  • Is Gitingest-MCP easy to install?

Yes! It can be installed via Smithery or manually through GitHub with clear instructions provided.

  • What programming language is Gitingest-MCP written in?

Gitingest-MCP is developed in Python.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
opengig
Star
0
Language
Python
License
MIT license

Recommend Servers

View All
Gpt Scrambler

2 days ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

2 hours ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago