MCP-Server (OnePieceServer & Geolocalizar)

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is MCP-Server?

MCP-Server is a project that contains two MCP servers developed with the @modelcontextprotocol/sdk. These servers provide useful tools that can be integrated by AI clients compatible with MCP.

How to use MCP-Server?

To use MCP-Server, install the necessary dependencies and run the server scripts using Node.js. You can execute the OnePieceServer or Geolocalizar server by running specific commands in your terminal.

Key features of MCP-Server?

  • OnePieceServer: Query information about characters from the anime/manga One Piece.
  • Geolocalizar: Obtain geographical information based on public IP addresses.
  • Easy integration with AI clients via MCP protocol.

Use cases of MCP-Server?

  1. Retrieving character details from One Piece for fan applications.
  2. Geolocating users based on their IP addresses for location-based services.
  3. Integrating with AI systems for enhanced data retrieval and processing.

FAQ from MCP-Server?

  • Can MCP-Server handle multiple requests simultaneously?

Yes! MCP-Server is designed to handle multiple requests efficiently.

  • What are the system requirements?

You need Node.js version 18 or higher and npm version 9 or higher to run MCP-Server.

  • Is there any documentation available?

Yes! Detailed documentation is provided in the README file of the project.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
TypeScript
License
MIT 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