wecom-bot-mcp-server-remotefile

An MCP server package ("wecom-bot-mcp-server-remotefile") intended to expose functionality for a WeCom (WeChat Work) bot and provide remote-file related operations via the Model Context Protocol (MCP).

Evaluated Apr 04, 2026 (17d ago)
Homepage ↗ Communication mcp wecom wechat-work agents remote-files integration bot
⚙ Agent Friendliness
35
/ 100
Can an agent use this?
🔒 Security
46
/ 100
Is it safe for agents?
⚡ Reliability
20
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
55
Documentation
40
Error Messages
0
Auth Simplicity
50
Rate Limits
10

🔒 Security

TLS Enforcement
60
Auth Strength
40
Scope Granularity
30
Dep. Hygiene
50
Secret Handling
50

No concrete details were provided about TLS enforcement, auth mechanism, scope granularity, dependency hygiene, or secret redaction/logging. Scores are conservative defaults based on uncertainty; review the repository code/manifests and deployment configuration before use.

⚡ Reliability

Uptime/SLA
0
Version Stability
45
Breaking Changes
0
Error Recovery
35
AF Security Reliability

Best When

You need an agent-friendly MCP tool surface for WeCom-bot-related remote file operations and can deploy/host the MCP server in a controlled environment.

Avoid When

You cannot verify the MCP tool set, authentication model, and logging/redaction behavior, or you require strong audited compliance guarantees.

Use Cases

  • Enable an AI agent to interact with a WeCom bot workflow
  • Let an agent upload/process or retrieve remote files through MCP tools (e.g., fetch file contents needed to answer queries)

Not For

  • Direct replacement for a full WeCom integration SDK/UI
  • High-sensitivity production workloads without reviewing authentication/transport and tool permissions
  • Serving as a general-purpose file storage service without explicit access controls

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

OAuth: No Scopes: No

Authentication details were not provided in the given input. MCP servers frequently require tokens/secrets (e.g., WeCom credentials), but this cannot be confirmed here.

Pricing

Free tier: No
Requires CC: No

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • Remote file operations can be non-idempotent (e.g., create/upload) if the tools don’t support deterministic request IDs.
  • Agents may attempt to exfiltrate sensitive file contents if tool scopes are not tightly limited.
  • Large files may hit timeouts/memory limits; agents should stream/chunk if tools support it.

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for wecom-bot-mcp-server-remotefile.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-04-04.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered