wechat_astrbot (inmostfly/wechat_astrbot) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 7 tools. No publisher has claimed this listing.

C
Emerging
74/100
11 days ago

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

inmostfly

Source: github_code

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Secret credentials may flow to a network call
2 flows detected: TAVILY_API_KEY, BAIDU_CLIENT_SECRET. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 8 credentials: EMAIL_IMAP_PASSWORD, EMAIL_IMAP_OAUTH_ACCESS_TOKEN, QWEATHER_API_KEY, TAVILY_API_KEY, SEARXNG_API_KEY, API_KEY, BAIDU_CLIENT_SECRET, OPENAI_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configPAUSE_ON_ERROR
configDOCUMENT_MCP_MAX_BYTES
configDOCUMENT_MCP_MAX_CHARS
configDOCUMENT_MCP_MAX_PAGES
configDOCUMENT_MCP_MAX_SHEET_ROWS
configEMAIL_IMAP_HOST
configEMAIL_IMAP_USERNAME
configEMAIL_IMAP_AUTH
🔐 secretEMAIL_IMAP_PASSWORD
🔐 secretEMAIL_IMAP_OAUTH_ACCESS_TOKEN
configEMAIL_IMAP_PORT
configEMAIL_IMAP_FOLDER
configEMAIL_IMAP_TIMEOUT_SECONDS
configEMAIL_IMAP_MAX_DOWNLOAD_BYTES
configEMAIL_MAX_BODY_CHARS
🔐 secretQWEATHER_API_KEY
configQWEATHER_API_HOST
configWEB_SEARCH_PROVIDER
🔐 secretTAVILY_API_KEY
configSEARXNG_URL
configTAVILY_API_URL
🔐 secretSEARXNG_API_KEY
configILINK_MCP_CONFIG
configAPI_KEY_2
configMODEL_2
configAPI_URL_2
configILINK_MAX_HISTORY
configILINK_API_BASE_URL
configILINK_BOT_TYPE
configREMINDER_TIMEZONE
configILINK_MAX_REPLY_CHARS
configILINK_MAX_IMAGES_PER_MESSAGE
configILINK_MAX_IMAGE_BYTES
configILINK_MAX_FILES_PER_MESSAGE
configILINK_MAX_FILE_BYTES
configILINK_MAX_DOCUMENT_CHARS
configILINK_MAX_DOCUMENT_TOTAL_CHARS
configREMINDER_ACTIVE_HOURS
configREMINDER_OUTBOUND_LIMIT
configREMINDER_CHECK_INTERVAL_SECONDS
configCHECKIN_AFTER_HOURS
configEMAIL_POLL_INTERVAL_SECONDS
configEMAIL_BATCH_SIZE
🔐 secretAPI_KEY
configMODEL
configAPI_URL
configQQ_APPID
configQQ_APPKEY
configBAIDU_CLIENT_ID
🔐 secretBAIDU_CLIENT_SECRET
configWECHAT_TARGET
configWECHAT_EXE
configProgramFiles
🔐 secretOPENAI_API_KEY
configOPENAI_BASE_URL
configHTTP_PROXY
configHTTPS_PROXY
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

7/7 tools missing one or more hints — extract_document (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); mailbox_status (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); check_new_mail (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +4 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool test coverage

4/7 tools referenced in tests (57%)

Write tests that reference each tool by name so every tool has at least one test.

Secrets not logged

1 secret value sent to print

Redact or omit secret values from log output.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 4 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/inmostfly/wechat_astrbot)](https://m8ven.ai/mcp/inmostfly/wechat_astrbot)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 94e7bb0af916e3a992c2e244a2163975a7deda4e
code hash: 2b20f79a5ea1b00c19c962b53127f72caec9f057b06f1fc37e3bc76ce47b4be6
verified: 9/1/2026, 5:39:47 PM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client