Home / MCP registry index / com.mianlingai/mianling
面灵AI 面试助手
com.mianlingai/mianling in the official MCP registry.
Endpoint https://api.mianlingai.com/agent/mcp.
The registry describes it as: 面灵AI:查面试与笔试记录和报告、管理简历、搜索校招岗位与面试题、跟进网申进度,OAuth 授权访问个人账户
We read its 148 tools on 2026-11-17. Nothing in them matched our tool-poisoning rules.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again about every two weeks.
Connect it
The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:
claude mcp add --transport http mianling https://api.mianlingai.com/agent/mcp{
"mcpServers": {
"mianling": {
"url": "https://api.mianlingai.com/agent/mcp"
}
}
}code --add-mcp '{"name":"mianling","type":"http","url":"https://api.mianlingai.com/agent/mcp"}'Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.
Let Claude Code check servers as it adds them
With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.
claude plugin marketplace add lazaretto-ai/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-pluginsTools it advertises
get_product_overview list_plans get_purchase_link get_campus_job_filters search_campus_jobs search_interview_questions get_account list_interviews get_interview_report get_interview_transcript list_resumes get_resume list_job_applications get_login_devices redeem_credits get_gift_code_info redeem_gift_code list_pending_subscription_cards activate_subscription_card refund_subscription_card list_agent_grants revoke_agent_grant check_order_status create_payment_order preview_coupon get_upgrade_offer submit_feedback list_my_feedbacks get_my_feedback reply_to_my_feedback update_feedback_notify_email get_wechat_support_link upload_resume create_resume_from_text delete_resume rename_interview delete_interview retry_interview_report generate_interview_experience export_interview_markdown list_answer_style_sources learn_answer_style get_voiceprint_status list_exams get_exam update_exam delete_exam export_exam_markdown start_exam end_exam list_interview_targets create_interview_target start_interview get_live_session_status end_live_interview set_live_interview_options ask_live_interview answer_live_interview_now interrupt_live_interview_answer answer_mock_interview and 88 more
Tool changes
We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.
Fingerprint of its tools at our last full read (2026-11-17):
d2e28cfd36accb7c. A client can hash the tools it is served the same way and compare;
the full value and a hash per tool are in this page as JSON.
Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.
Run this server? Show the check in your README
The badge reflects the latest read:
[](https://lazaretto.dev/mcp-registry/com-mianlingai-mianling)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. How tool poisoning works. What we found across the registry. Check another server.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.