Juhe Mobile Phone Location MCP Server

Created By
juhemcpa year ago
Overview

What is Juhe Mobile Phone Location MCP Server?

Juhe Mobile Phone Location MCP Server is a Model Context Protocol server that provides the functionality to query the location information of mobile phone numbers, including details such as province, city, and carrier.

How to use Juhe Mobile Phone Location MCP Server?

To use the server, you can either run it using the recommended uv tool or install it via pip. After installation, you need to set up your API key for mobile location queries.

Key features of Juhe Mobile Phone Location MCP Server?

  • Queries mobile phone number location information.
  • Provides details such as province, city, and carrier.
  • Supports asynchronous queries for efficient processing.

Use cases of Juhe Mobile Phone Location MCP Server?

  1. Determining the location of a mobile phone number for customer service.
  2. Verifying the origin of phone numbers in fraud detection.
  3. Enhancing user experience by providing location-based services.

FAQ from Juhe Mobile Phone Location MCP Server?

  • What programming language is the server built with?

The server is built using Python 3.10 or higher.

  • How do I obtain the API key?

You can get the API key from Juhe Data API.

  • Can I run the server on different operating systems?

Yes, the server can be run on both MacOS and Windows.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
juhemcp
Star
0
Language
Python
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
Crevio

2 days ago