# MobTech Platform MCP > MobTech Platform brings China's mobile development SDK tools into your AI workflow. Your agent can automatically verify SMS 2FA codes, check phone number limits, and analyze social sharing data from platforms like WeChat or Weibo. It also checks the OAuth authentication status for user accounts. ## Overview - **Category:** communication-messaging - **Price:** Free - **Tags:** sms-verification, 2fa, social-sharing, mobile-sdk, user-authentication, engagement-analytics ## Description Your agent talks straight to MobTech’s APIs through this server. It gives your AI client core mobile functions, like SMS verification and social analytics, without you having to write a single custom REST query. You're working with China's mobile development SDK tools right inside your workflow. When you need to verify an activation code, your agent calls **`verify_sms_code`**. This checks whether the SMS activation code matches what MobTech's backend expects for a specific phone number. It’s how you confirm a user is legit using that number. For checking numbers and limits, you use **`check_phone_status`**. You pass it a mobile number, and the tool tells you if that number has hit its operational or delivery limit within their system. This means your agent knows right away if you’re running into rate limits or if the service itself is maxed out for that account. If you're dealing with user accounts, **`get_social_auth_status`** handles the OAuth binding. You feed it a user ID, and it confirms the current social authentication status. It tells you if the user’s profile is properly linked to a major social platform—it verifies that connection. When tracking how widely your app spreads, **`get_share_analytics`** pulls in all the data. Your agent runs this tool to get aggregated analytics. This shows exactly how often your app was shared across various social networks using ShareSDK, giving you a clear picture of user sharing patterns. ## Tools ### check_phone_status Checks if a specified mobile number has reached its operational or delivery limit within the system. ### get_share_analytics Retrieves aggregated analytics data detailing how often your app was shared through various social networks via ShareSDK. ### get_social_auth_status Checks the current OAuth binding status to confirm if a user's account is properly linked to a social platform. ### verify_sms_code Verifies an SMS activation code by checking it against the MobTech backend for a given phone number. ## Prompt Examples **Prompt:** ``` Verify the SMS code 582910 for phone number +86 13800000000. ``` **Response:** ``` I've contacted MobTech. The verification code 582910 is valid for this phone number. You can proceed with logging the user in. ``` **Prompt:** ``` Check the share analytics for WeChat for the last 7 days. ``` **Response:** ``` According to the ShareSDK data, there were 4,210 WeChat session shares and 1,200 Moments shares tracked in the last 7 days. ``` ## Capabilities ### Verify SMS Codes Your agent calls `verify_sms_code` to check if an SMS activation code matches a given phone number. ### Check Phone Number Limits The `check_phone_status` tool determines if a specified mobile number has reached its operational or delivery limit. ### Analyze Social Shares Your agent runs `get_share_analytics` to pull aggregated data on how often your app was shared via social platforms. ### Check OAuth Status The `get_social_auth_status` tool verifies the current social authentication binding status for a user ID. ## Use Cases ### New User Onboarding Flow A new user signs up and needs to verify their identity. Your agent first uses `get_social_auth_status` to confirm the user is linked via WeChat, then runs `verify_sms_code` when they submit an OTP for phone backup. The result tells your system if both paths are valid. ### Marketing Campaign Analysis A growth marketer needs campaign data. Instead of downloading CSVs from three different dashboards, the agent runs `get_share_analytics`. It instantly provides aggregated metrics on total shares across all monitored social platforms, proving immediate ROI. ### Preventing Service Outages Your service needs to send a bulk notification. Before attempting sends, the agent first calls `check_phone_status` for the target list of numbers. This prevents your system from failing and wasting credits because too many numbers hit a temporary rate limit. ### Post-Launch Feature Audit After releasing an app update, you need to measure buzz. The agent calls `get_share_analytics` for the last 7 days. This gives you concrete data on social engagement (WeChat/QQ shares) that proves users are adopting the new feature. ## Benefits - Verification is immediate. You stop writing code to handle 2FA logic; just call `verify_sms_code` when a user submits an OTP, and you get a clean pass/fail status back. - Audit phone numbers before use. The `check_phone_status` tool prevents your service from failing due to rate limits or delivery status issues on specific carriers. - Get real social data. Instead of manual reports, `get_share_analytics` pulls aggregated metrics showing how often users shared the app across WeChat and Weibo. - Confirm account linkage fast. You can use `get_social_auth_status` to validate if a user's OAuth binding is active before allowing them into premium features. - Reduce backend complexity. All these mobile SDK interactions—SMS, social, phone checks—are encapsulated in dedicated tools, keeping your core codebase clean. ## How It Works The bottom line is, you run complex backend mobile checks using simple tool calls rather than managing API keys and endpoints yourself. 1. Subscribe to this server and get your credentials. 2. Insert your unique `AppKey` and `AppSecret` into the agent context from your MobTech Dashboard. 3. Start calling tools like `verify_sms_code` directly from your agent's workflow. ## Frequently Asked Questions **How do I use the verify_sms_code tool?** You provide the user's phone number and the specific activation code. The agent calls `verify_sms_code` to check if that OTP is valid for that line at this time. **Can I use get_share_analytics for platforms other than WeChat?** The tool aggregates data from multiple social networks, including Weibo and QQ. Check the tool documentation for a full list of supported sharing platforms. **Is check_phone_status necessary before sending an SMS code?** Yes, it's critical. Running `check_phone_status` tells you if the target number has hit rate limits or delivery caps, preventing your service from failing and wasting credits. **Does get_social_auth_status handle token expiry?** The tool checks the binding status. If the account is no longer properly linked (e.g., due to an expired OAuth token), it reports that status, guiding you on what needs refreshing. **What specific information does `check_phone_status` give if I hit a service limit?** It returns an explicit status code indicating quota exhaustion. The tool doesn't just fail; it tells you exactly which type of rate limit was reached, allowing your agent to pause or retry later. **Can I restrict the date range when running `get_share_analytics`?** Yes, you pass start and end dates as parameters. This lets you analyze social sharing metrics for a specific window—say, just last week—instead of pulling all historical data. **Does `get_social_auth_status` require the user's unique ID?** Yes, checking the OAuth binding status requires a unique identifier for the user. The tool needs this specific ID to accurately check which social platforms are bound to that account. **What happens if I run `verify_sms_code` with an incorrect phone number format?** The server will immediately reject the request before contacting the backend. It sends a specific error message detailing the formatting issue, so you don't waste API calls on bad inputs. **Where do I find my AppKey?** Log into the MobTech official dashboard at mob.com, access your App settings, and your AppKey will be displayed at the top of the interface. **Can I completely bypass the Mobile SDK?** This backend MCP wraps the API meant to *verify* SMS sent via your front-end Mobile App SDK. Your front-end app should still invoke the SDK for sending SMS and handling UI.