d1jiema-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@d1jiema-mcp Check my D1Jiema balance."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
d1jiema-mcp
d1jiema-mcp 是 D1Jiema data.php API 的 Codex/MCP 插件,支持余额、取号、取码、释放、拉黑、发送短信和历史记录。
一句话安装
从 GitHub 安装并运行
guangfuhao/d1jiema-mcp插件;首次使用打开本地 D1Jiema 配置页让我输入 API Token,然后查询余额确认连接。
Related MCP server: SimRelay MCP Server
首次配置
官方入口:
API 基础地址:
https://api.d1jiema.com/zc/data.php
获取 API Token:打开 API Token 创建页面,登录 D1Jiema 后进入【个人中心】→【创建 API Token】,复制生成的 Token。插件使用这个 Token 访问 API,不需要在插件中重复登录账户。
宿主支持原生设置页时,可直接填写;当前 Codex 本地插件页如果只显示技能,d1jiema-setup 会调用 d1jiema_setup_local,启动只监听 127.0.0.1 的临时配置页。保存后服务自动关闭,Token 写入当前用户的本地配置并设置为 0600。
无图形界面的环境使用 D1JIEMA_API_TOKEN,可选 D1JIEMA_BASE_URL。Token 不写入代码、README、GitHub、日志或普通聊天消息。
能力
d1jiema_balance:查询余额;d1jiema_login:打开本地 Token 配置流程(Token 在 D1Jiema 网页个人中心创建);d1jiema_get_phone:按关键词、指定号码、省份、实卡/虚卡/全部取号;d1jiema_get_sms:按手机号和关键词取码;d1jiema_release:释放号码,需要confirm=true;d1jiema_block:拉黑号码,需要confirm=true;d1jiema_send_sms:发送短信,需要confirm=true;d1jiema_history:查询最近 24 小时历史,需要确认一分钟频率限制;d1jiema_request:调用文档中的其他 GET code。
所有接口都使用 https://api.d1jiema.com/zc/data.php,参数会自动进行 URL 编码。上游返回 ERROR: 时,工具返回结构化错误,不会把 Token 返回给调用方。
安全边界
发送短信、拉黑、释放会改变账户或产生实际通信行为,插件默认拒绝,只有明确传入确认参数才会发出请求。queryUsed 按文档限制每分钟最多调用一次。
English documentation: README.en.md
Available Tools
12 toolsd1jiema_balanceB
Read the D1Jiema account balance using leftAmount.
Inputs: no named parameters. Returns: result
d1jiema_blockA
Block a D1Jiema phone. This is irreversible account state; set confirm=true explicitly.
Inputs: phone (required), confirm. Returns: result
d1jiema_get_phoneC
Get a D1Jiema phone number. Optional keyword, exact phone, province, and card type filters are passed through.
Inputs: phone, key_word, province, card_type. Returns: result
d1jiema_get_smsC
Fetch the SMS containing the required keyword for a phone number.
Inputs: phone (required), key_word (required). Returns: result
d1jiema_historyA
Read the last 24 hours of D1Jiema history. The API allows at most one call per minute; set confirm_rate_limit=true.
Inputs: confirm_rate_limit. Returns: result
d1jiema_loginConfigure D1Jiema tokenC
Open the local D1Jiema token configuration flow. D1Jiema creates API tokens from its web personal center.
Inputs: open_browser. Returns: result
d1jiema_releaseB
Release a D1Jiema phone. This changes account state; set confirm=true explicitly.
Inputs: phone (required), confirm. Returns: result
d1jiema_requestB
Call any documented D1Jiema GET operation by code. Write-like codes require confirm=true.
Inputs: code (required), params, confirm. Returns: result
d1jiema_send_smsB
Send an SMS through D1Jiema. Use only for an explicitly authorized recipient and content; set confirm=true.
Inputs: phone (required), content (required), to_phone (required), confirm, +1 more. Returns: result
d1jiema_settings_readD1Jiema settingsARead-only
Read D1Jiema settings. The API token is always masked.
Inputs: no named parameters. Returns: layout, schema, values
d1jiema_settings_updateSave D1Jiema settingsC
Save the D1Jiema token from the settings page.
Inputs: set (required). Returns: values
d1jiema_setup_localOpen D1Jiema local setupA
Launch a one-shot localhost form for entering the D1Jiema API token. The form closes after saving.
Inputs: open_browser. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 12 tools
The set includes four token/config tools (settings_read, settings_update, setup_local, login) whose boundaries are fuzzy—especially setup_local vs login, both of which open a local token flow. The generic d1jiema_request also overlaps with all specific read tools, though it is clearly marked as a catch-all.
All tools share the d1jiema_ prefix and snake_case, but the verb/noun pattern is inconsistent: some use verb_noun (get_phone, send_sms), some noun_verb (settings_read), and others are bare verbs or nouns (login, balance, history). The style is readable but not predictable.
12 tools is within a reasonable range for an SMS/phone service. However, four tools for token configuration alone feels slightly over-provisioned, keeping it from a perfect score.
Core lifecycle operations—phone acquisition, SMS retrieval, release, block, send, balance, history—are covered, and the generic request tool extends read coverage to any documented GET operation. Minor gaps remain (e.g., explicit phone status check or token deletion), but agents have workarounds.
Maintenance
Related MCP Connectors
Create and manage DialNexa AI voice agents, campaigns, calls, phone numbers, workflows, and more.
Rent real and virtual phone numbers in 14 countries and read their SMS from your AI agent.
Send and schedule SMS and WhatsApp messages, manage contacts and templates, and track delivery.
Virtual phone numbers for SMS verification, OTP receipt, and number management.
Related MCP Servers
- AlicenseAqualityBmaintenanceVirtual phone number platform for AI agents — rent numbers across 200+ countries, receive SMS, and manage the full activation lifecycle.662 npm4MIT

SimRelay MCP Serverofficial
AlicenseAqualityDmaintenanceEnables AI agents to manage SimRelay SIMs: list, lock, release, read SMS history, and stream incoming messages in real-time via WebSocket.1110 npmISC
VoidMob MCPofficial
AlicenseAqualityBmaintenancePhone numbers, mobile IPs and eSIMs for your AI agent.28181 npm22MIT- AlicenseAqualityCmaintenanceEnables AI agents to purchase phone numbers and retrieve one-time SMS/OTP verification codes via the CODASMS API, with support for 700+ services and 180+ countries including automatic refunds if no code arrives.732 npmMIT