MyIP MCP Server

Created By
nikolaypavlova year ago
A Model Context Protocol (MCP) server for providing your public IP to LLMs
Overview

what is MyIP MCP Server?

MyIP MCP Server is a Model Context Protocol (MCP) server designed to provide your public IP address to Large Language Models (LLMs).

how to use MyIP MCP Server?

To use the MyIP MCP Server, you need to install it by following the provided installation instructions and then utilize the get_ip_info tool to retrieve your public IP address.

key features of MyIP MCP Server?

  • Exposes a get_ip_info tool for retrieving public IP addresses.
  • Simple installation process using MCP commands.

use cases of MyIP MCP Server?

  1. Providing public IP information to LLMs for context-aware responses.
  2. Integrating with applications that require public IP data.

FAQ from MyIP MCP Server?

  • What is the purpose of the MyIP MCP Server?

The MyIP MCP Server is used to provide public IP addresses to LLMs, enhancing their context awareness.

  • How do I install the MyIP MCP Server?

You can install it by following the installation instructions provided in the documentation.

  • Is there any cost associated with using the MyIP MCP Server?

No, the MyIP MCP Server is free to use.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
nikolaypavlov
Star
-
Language
-
License
-
Tags

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