MCP-Server

Created By
fmpoliveiraa year ago
Overview

what is MCP-Server?

MCP-Server is a server application that utilizes the Meteostat API to fetch and provide meteorological data from around the world.

how to use MCP-Server?

To use MCP-Server, install the necessary dependencies using npm, build the project, and start the server. You can then make POST requests to retrieve weather data for specific locations.

key features of MCP-Server?

  • Fetches global meteorological data using the Meteostat API.
  • Built with Express.js for easy server management.
  • Supports POST requests to retrieve data based on geographical coordinates.

use cases of MCP-Server?

  1. Retrieving weather data for specific locations.
  2. Integrating weather data into applications for analysis or display.
  3. Supporting research projects that require historical weather data.

FAQ from MCP-Server?

  • What technologies does MCP-Server use?

MCP-Server is built using Node.js and TypeScript, leveraging the Express.js framework.

  • How can I retrieve weather data?

You can make a POST request to the server with the latitude and longitude of the desired location.

  • Is there any documentation available?

Yes, you can find the documentation and source code on the project's GitHub page: MCP-Server GitHub.

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

Recommend Servers

View All
Payai X402 Tools

6 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.

a day ago