McpServer

Created By
Adriano-Severinoa year ago
Overview

What is McpServer?

McpServer is an implementation server of the Model Context Protocol (MCP) designed for integrating AI models and managing books.

How to use McpServer?

To use McpServer, clone the repository, set up the environment, and run the server using Docker Compose or locally. Access the API endpoints for managing books and executing AI models.

Key features of McpServer?

  • Integration with Ollama AI models via HTTP API
  • Management of book data through a dedicated API
  • Tools for executing various functions related to books and AI models

Use cases of McpServer?

  1. Managing a library of books with CRUD operations.
  2. Generating responses using AI models for various prompts.
  3. Integrating with web interfaces for enhanced user interaction.

FAQ from McpServer?

  • What are the system requirements for McpServer?

Requires Docker, .NET 9.0, and at least 8GB of RAM.

  • How can I contribute to McpServer?

Fork the repository, create a feature branch, and submit a pull request.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Adriano-Severino
Star
0
Language
C#
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.

35 minutes ago