MCP Demo

Created By
tanjibpaa year ago
Overview

What is MCP Demo?

MCP Demo is a demonstration implementation of a Model Context Protocol (MCP) server designed to manage organizations and devices, calculate distances between devices and their associated organizations, and provide tools for data interaction.

How to use MCP Demo?

To use MCP Demo, clone the repository, set up a virtual environment, configure the database connection in a .env file, and run the server using the provided commands.

Key features of MCP Demo?

  • Database Integration: Connects to a PostgreSQL database for managing organizations and devices.
  • Distance Calculation: Utilizes the Haversine formula for calculating distances between devices and organizations.
  • MCP Tools: Offers tools to fetch organizations, devices, and calculate distances.

Use cases of MCP Demo?

  1. Managing organizational data and device information.
  2. Calculating geographical distances for logistics and planning.
  3. Providing a backend service for applications requiring device management.

FAQ from MCP Demo?

  • What technologies are used in MCP Demo?

MCP Demo is built using Python and integrates with PostgreSQL for database management.

  • How can I set up the database?

You can set up the database by running the SQL script provided in the repository after configuring your environment variables.

  • Is there any support for additional features?

Yes, the MCP framework allows for extensibility, and additional features can be implemented as needed.

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