Juhe Mobile Phone Location MCP Server
一个提供手机号码(段)所属归属地查询功能的模型上下文协议(Model Context Protocol)服务器。该服务器使大型语言模型(LLMs)能够获取手机号码段归属地信息,如:省份、城市、运营商。
Components
Tools
服务器实现了一个工具:
- get_mobile_phone_location: 根据手机号码查询其所属地信息。
- 需要传入 "phone"(手机号码)作为必须的字符串参数。
async def get_mobile_location(phone: str = "") -> list[types.TextContent | types.ImageContent | types.EmbeddedResource]:
Install
This server requires Python 3.10 or higher. Install dependencies using uv (recommended) or pip
Using uv (recommended)
When using uv no specific installation is needed. We will use uvx to directly run jmobile-location-mcp-server.
uvx jmobile-location-mcp-server
Using PIP
Alternatively you can install jmobile-location-mcp-server via pip:
pip install jmobile-location-mcp-server
After installation, you can run it as a script using:
python -m jmobile_location_mcp_server
Configuration
Environment Variables
JUHE_MOBILE_LOCATION_API_KEY: 聚合数据的手机归属地查询API密钥。获取:https://www.juhe.cn/docs/api/id/11
JUHE_MOBILE_LOCATION_API_KEY=your_api_key
Claude Desktop
- On MacOS:
~/Library/Application\ Support/Claude/claude_desktop_config.json - On Windows:
%APPDATA%/Claude/claude_desktop_config.json
Using uvx
"mcpServers": {
"jmobile-location-mcp-server": {
"command": "uvx",
"args": [
"jmobile-location-mcp-server"
],
"env": {
"JUHE_MOBILE_LOCATION_API_KEY": "your_api_key"
}
}
}
Using pip installation
"mcpServers": {
"jmobile-location-mcp-server": {
"command": "python",
"args": [
"-m",
"jmobile_location_mcp_server"
],
"env": {
"JUHE_MOBILE_LOCATION_API_KEY": "your_api_key"
}
}
}
Debugging
You can use the MCP inspector to debug the server. For uvx installations:
npx @modelcontextprotocol/inspector uvx jmobile-location-mcp-server
Or if you've installed the package in a specific directory or are developing on it:
cd path/to/servers/src/jmobile-location-mcp-server
npx @modelcontextprotocol/inspector uv run jmobile-location-mcp-server
Examples of Questions for Cline
- "查询下这个手机号码的归属地信息 18912341234"
Metadata
Release files for jmobile-location-mcp-server 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| jmobile_location_mcp_server-0.1.1.tar.gz | 16.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| jmobile_location_mcp_server-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 21.2 kB
Release files / jmobile_location_mcp_server-0.1.1.tar.gz
| Download URL | jmobile_location_mcp_server-0.1.1.tar.gz |
|---|---|
| Size | 16.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2ad373c6d905f52a4e3a5367afbbbe47e25c3ff66340ada518b8a5d7d95741f4
|
|
BLAKE2b-256 checksum How to use checksums |
6ece845b55b2609c3c77675919907214499e9d0f235644312f600034383bc366
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 18, 2025.
Transparency logRelease files / jmobile_location_mcp_server-0.1.1-py3-none-any.whl
| Download URL | jmobile_location_mcp_server-0.1.1-py3-none-any.whl |
|---|---|
| Size | 4.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3a3fbb51c586473b0295a6ef3064a2fc8d736e2e1662ca867672acb8a5a0d327
|
|
BLAKE2b-256 checksum How to use checksums |
493bad3bc2044e6d1ed65de27f7c675c59bec94439db8547297bd21c673afac7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 18, 2025.
Transparency log