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
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