MODEL CONTEXT PROTOCOL

Created By
arkapatra31a year ago
Implementation of Anthropic's Model Context Protocol
Overview

What is Model Context Protocol?

Model Context Protocol is a service that allows users to query real-time weather information for any city and access internet usage data by country using the Model Context Protocol (MCP) with FastMCP.

How to use Model Context Protocol?

To use the Model Context Protocol, set up the environment using Poetry, install the dependencies, and configure the MCP server. Users can then query weather data or internet usage data through the respective services.

Key features of Model Context Protocol?

  • Real-time weather information for any city
  • Internet usage data by country
  • Asynchronous API for efficient processing
  • MCP-based protocol for standardized communication
  • MongoDB integration for storing internet usage data

Use cases of Model Context Protocol?

  1. Fetching current weather conditions for travel planning.
  2. Analyzing internet usage trends by country for research.
  3. Integrating weather data into applications for enhanced user experience.

FAQ from Model Context Protocol?

  • What programming language is used?

The project is built using Python.

  • Is there a license for this project?

Yes, it is licensed under the Apache-2.0 license.

  • How can I contribute to the project?

Contributions are welcome! Please check the GitHub repository for guidelines.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
arkapatra31
Star
0
Language
Python
License
Apache-2.0 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.

17 hours ago
Voyei

7 hours ago