stack-exchange-mcp

Created By
jagreetdga year ago
MCP Server for interacting with StackExchange sites like StackOverflow
Overview

what is stack-exchange-mcp?

stack-exchange-mcp is a server designed to interact with StackExchange sites, such as StackOverflow, allowing developers to easily access and manipulate data from these platforms.

how to use stack-exchange-mcp?

To use stack-exchange-mcp, set up the server by following the installation instructions in the GitHub repository, and then use the provided API endpoints to interact with StackExchange data.

key features of stack-exchange-mcp?

  • Easy integration with StackExchange APIs
  • Ability to fetch questions, answers, and user data
  • Supports multiple StackExchange sites

use cases of stack-exchange-mcp?

  1. Building applications that require StackExchange data.
  2. Analyzing trends in questions and answers on StackOverflow.
  3. Creating bots that interact with StackExchange communities.

FAQ from stack-exchange-mcp?

  • What programming language is stack-exchange-mcp written in?

stack-exchange-mcp is written in JavaScript.

  • Is stack-exchange-mcp free to use?

Yes! stack-exchange-mcp is open-source and free to use.

  • How can I contribute to stack-exchange-mcp?

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

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
jagreetdg
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
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.

8 hours ago