Test d'intégration MCP Server GitHub

Created By
Erkkula year ago
Référentiel de test pour l'intégration MCP server GitHub
Overview

What is MCP Server Test?

MCP Server Test is a repository designed for testing the integration with the MCP server on GitHub.

How to use MCP Server Test?

To use MCP Server Test, clone the repository from GitHub and run the integration tests to verify that all GitHub operations can be performed through the MCP server.

Key features of MCP Server Test?

  • Integration testing for GitHub operations
  • Easy setup and execution of tests
  • Supports various GitHub functionalities

Use cases of MCP Server Test?

  1. Verifying the functionality of GitHub API calls through the MCP server.
  2. Ensuring that all GitHub operations are compatible with the MCP server.
  3. Testing new features or updates in the MCP server integration.

FAQ from MCP Server Test?

  • What programming language is used in this project?

The project is developed in Python.

  • Is this repository official?

No, this repository is not an official project.

  • How can I contribute to this project?

You can contribute by submitting issues or pull requests on GitHub.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Erkkul
Star
0
Language
Python
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year 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.

5 hours ago