Mcp Server Location

Created By
v5techa year ago
A location server based on MCP (Model Context Protocol) that provides IP address location and latitude/longitude query functionality.
Overview

What is Mcp Server Location?

Mcp Server Location is a location server based on the Model Context Protocol (MCP) that provides functionality for querying IP address locations and latitude/longitude coordinates.

How to use Mcp Server Location?

To use the Mcp Server Location, install it via npm and utilize its two main tools: IP Location and Latitude/Longitude Location.

Key features of Mcp Server Location?

  • Supports location queries by IP address.
  • Provides detailed address information based on latitude and longitude coordinates.
  • Developed with TypeScript for enhanced type safety.
  • Compliant with the MCP protocol standard.

Use cases of Mcp Server Location?

  1. Determining the geographical location of a user based on their IP address.
  2. Retrieving detailed address information from latitude and longitude coordinates.
  3. Integrating location services into applications that require geographical data.

FAQ from Mcp Server Location?

  • Can I use Mcp Server Location for any IP address?

Yes! It can provide location information for any valid IP address.

  • Is Mcp Server Location free to use?

Yes! The project is open-source and free to use under the MIT License.

  • What programming language is Mcp Server Location developed in?

It is developed in TypeScript.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
v5tech
Star
0
Language
JavaScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago