HTTP Server with MCP Support

Created By
jhgaylora year ago
Overview

what is example-candidate-mcp-server?

example-candidate-mcp-server is an HTTP server built with Express and TypeScript that serves both a webpage and a Model Context Protocol (MCP) endpoint.

how to use example-candidate-mcp-server?

To use the server, clone the repository, install the dependencies, and start the HTTP transport using npm commands. Customize the candidate data by setting environment variables or updating the configuration file.

key features of example-candidate-mcp-server?

  • HTTP server with both web and MCP functionality
  • Stateless MCP server implementation with modern Streamable HTTP transport
  • TypeScript for type safety
  • Express.js for HTTP handling

use cases of example-candidate-mcp-server?

  1. Serving candidate information through a web interface.
  2. Providing a Model Context Protocol (MCP) endpoint for integration with other services.
  3. Customizing candidate data for different applications.

FAQ from example-candidate-mcp-server?

  • What are the requirements to run the server?

Node.js 18+ and npm or yarn are required to run the server.

  • How can I customize the candidate data?

You can set environment variables or update the configuration file to customize the candidate data.

  • How do I run the server in development mode?

Use the command npm run dev to run the server in development mode with auto-reloading.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
jhgaylor
Star
0
Language
TypeScript
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.

16 hours ago
Voyei

6 hours ago