A Simple MCP weather Server written in TypeScript

Created By
phatpham-katalona year ago
Overview

what is MCP Server Demo?

MCP Server Demo is a simple weather server built using TypeScript that demonstrates the Model Context Protocol (MCP) for weather data.

how to use MCP Server Demo?

To use the MCP Server Demo, follow the Quickstart tutorial to set up the server and start retrieving weather data.

key features of MCP Server Demo?

  • Built with TypeScript for type safety and modern development practices.
  • Demonstrates the Model Context Protocol for weather data retrieval.
  • Easy to set up and use with a quickstart guide.

use cases of MCP Server Demo?

  1. Integrating weather data into applications using the MCP.
  2. Learning how to implement a server using TypeScript.
  3. Experimenting with weather data APIs.

FAQ from MCP Server Demo?

  • What is the Model Context Protocol (MCP)?

The Model Context Protocol is a standard for exchanging context information between systems, particularly useful for weather data.

  • Is MCP Server Demo free to use?

Yes! MCP Server Demo is open-source and free to use.

  • Can I contribute to the MCP Server Demo?

Yes! Contributions are welcome, and you can find more information in the repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
phatpham-katalon
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Voyei

3 hours 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.

13 hours ago