{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"awesome-gotoolkits-wecombot","slug":"gotoolkits-wecombot","name":"gotoolkits/wecombot","type":"mcp","url":"https://github.com/gotoolkits/mcp-wecombot-server.git","page_url":"https://unfragile.ai/gotoolkits-wecombot","categories":["mcp-servers"],"tags":[],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"awesome-gotoolkits-wecombot__cap_0","uri":"capability://tool.use.integration.wecom.group.robot.message.routing.via.mcp.protocol","name":"wecom group robot message routing via mcp protocol","description":"Routes structured messages from MCP clients to WeCom (WeChat Work) group robots through a standardized server interface. Implements the Model Context Protocol as a transport layer, translating MCP tool calls into WeCom API HTTP requests with webhook URL-based delivery. The server acts as a protocol adapter, accepting MCP-formatted requests and marshaling them into WeCom's proprietary message format for group chat delivery.","intents":["Send notifications from AI agents to WeCom group chats without direct API integration","Integrate WeCom messaging into MCP-compatible AI workflows and multi-tool orchestration","Decouple message sending logic from application code via standardized MCP interface"],"best_for":["Teams building MCP-native AI agents that need WeCom group notifications","Organizations standardizing on MCP for tool integration across multiple services","Developers migrating from direct WeCom API calls to MCP-based orchestration"],"limitations":["Requires valid WeCom group robot webhook URL — no fallback to direct API authentication","Message delivery is asynchronous via HTTP webhooks — no guaranteed delivery confirmation or retry logic visible in MCP interface","Limited to WeCom's message type constraints (text, markdown, image, file) — no custom payload passthrough","Single-threaded or limited concurrent request handling — performance under high message volume unknown"],"requires":["WeCom (WeChat Work) group with robot webhook URL configured","MCP client implementation (Claude Desktop, custom MCP host, or compatible tool)","Network connectivity from MCP server to WeCom webhook endpoint","Go runtime (artifact is Go-based MCP server)"],"input_types":["MCP tool call with message parameters (text, title, markdown content)","Structured JSON payloads conforming to MCP schema"],"output_types":["HTTP POST to WeCom webhook","MCP tool result with delivery status (success/failure)","WeCom group chat message"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-gotoolkits-wecombot__cap_1","uri":"capability://tool.use.integration.text.message.delivery.to.wecom.groups","name":"text message delivery to wecom groups","description":"Sends plain text messages to WeCom group robots via MCP tool interface. Accepts text content as MCP tool parameters, constructs WeCom API-compliant JSON payload with message type 'text', and POSTs to the configured webhook URL. Supports optional message mentions and formatting directives within the text payload.","intents":["Send simple text alerts and notifications from AI agents to team WeCom groups","Deliver log messages, status updates, or plain-text reports to group chats","Trigger group notifications as part of automated workflows or agent decision chains"],"best_for":["Teams needing lightweight notification delivery without rich formatting","Agents generating text-only status reports or alerts","High-volume notification scenarios where text is sufficient"],"limitations":["No built-in text formatting beyond WeCom's native text capabilities","Message length constrained by WeCom API limits (typically 2000 characters)","No message threading or reply context — each message is independent","No delivery receipts or read confirmations returned via MCP interface"],"requires":["WeCom group robot webhook URL","MCP client capable of calling tools with string parameters","Text content < 2000 characters"],"input_types":["string (plain text message body)"],"output_types":["WeCom group message (text type)","MCP tool result with HTTP status code"],"categories":["tool-use-integration","text-generation-language"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-gotoolkits-wecombot__cap_2","uri":"capability://tool.use.integration.markdown.formatted.message.delivery.to.wecom.groups","name":"markdown-formatted message delivery to wecom groups","description":"Sends markdown-formatted messages to WeCom group robots, converting markdown syntax into WeCom's markdown message type. Accepts markdown content as MCP tool parameter, validates markdown structure, and POSTs to webhook with message type 'markdown'. Supports WeCom-compatible markdown features including headers, bold, italic, links, and code blocks.","intents":["Deliver formatted reports, documentation, or structured data from agents to group chats","Send code snippets, technical documentation, or formatted logs with syntax preservation","Create visually organized notifications with headers, emphasis, and links"],"best_for":["Technical teams receiving code, logs, or structured documentation","Agents generating formatted reports or analysis output","Scenarios requiring visual hierarchy and emphasis in group notifications"],"limitations":["Markdown support limited to WeCom's subset — not all standard markdown features supported","No syntax highlighting for code blocks — language specification may be ignored","Message length constrained by WeCom API limits","No client-side markdown validation — invalid markdown may fail silently at WeCom endpoint"],"requires":["WeCom group robot webhook URL","MCP client capable of passing markdown string parameters","Markdown content compatible with WeCom's markdown parser"],"input_types":["string (markdown-formatted text)"],"output_types":["WeCom group message (markdown type)","MCP tool result with HTTP status"],"categories":["tool-use-integration","text-generation-language"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-gotoolkits-wecombot__cap_3","uri":"capability://tool.use.integration.image.message.delivery.to.wecom.groups","name":"image message delivery to wecom groups","description":"Sends image messages to WeCom group robots by accepting image URLs or base64-encoded image data via MCP tool parameters. Constructs WeCom image message payload with media_id or base64 content, POSTs to webhook endpoint. Supports common image formats (JPEG, PNG, GIF) within WeCom's size constraints.","intents":["Deliver generated images, charts, or visual reports from agents to group chats","Send screenshots, diagrams, or visual analysis output to teams","Include visual context in automated notifications and alerts"],"best_for":["Agents generating charts, graphs, or visual analysis","Workflows requiring visual evidence or screenshots in group notifications","Teams needing image-based alerts or status dashboards"],"limitations":["Image size constrained by WeCom API limits (typically < 10MB)","No image processing or transformation — must provide pre-formatted images","Base64 encoding increases payload size — URL-based delivery preferred for large images","No image metadata or caption support beyond WeCom's native image message type"],"requires":["WeCom group robot webhook URL","Image URL accessible from MCP server OR base64-encoded image data","Image format supported by WeCom (JPEG, PNG, GIF)"],"input_types":["string (image URL or base64-encoded image data)"],"output_types":["WeCom group message (image type)","MCP tool result with HTTP status"],"categories":["tool-use-integration","image-visual"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-gotoolkits-wecombot__cap_4","uri":"capability://tool.use.integration.file.message.delivery.to.wecom.groups","name":"file message delivery to wecom groups","description":"Sends file messages to WeCom group robots by accepting file URLs or file metadata via MCP tool parameters. Constructs WeCom file message payload with media_id or file reference, POSTs to webhook. Supports arbitrary file types within WeCom's constraints (documents, archives, executables).","intents":["Deliver generated reports, logs, or data exports from agents to group chats","Share downloadable artifacts, backups, or processed files with teams","Include file attachments in automated workflow notifications"],"best_for":["Workflows generating downloadable artifacts or reports","Agents producing logs, exports, or data files for team distribution","Scenarios requiring file sharing without external storage setup"],"limitations":["File size constrained by WeCom API limits (typically < 20MB)","No file validation or virus scanning — WeCom performs server-side checks","File must be accessible via URL or pre-uploaded to WeCom media server","No file metadata (description, tags) support beyond WeCom's native file message type"],"requires":["WeCom group robot webhook URL","File URL accessible from MCP server OR file media_id from WeCom upload","File size within WeCom limits"],"input_types":["string (file URL or media_id)"],"output_types":["WeCom group message (file type)","MCP tool result with HTTP status"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-gotoolkits-wecombot__cap_5","uri":"capability://tool.use.integration.batch.message.delivery.with.error.handling","name":"batch message delivery with error handling","description":"Sends multiple messages to WeCom groups in sequence via repeated MCP tool calls, with per-message error handling and status reporting. Each tool invocation is independent, allowing partial success scenarios where some messages deliver while others fail. MCP server returns individual status for each message delivery attempt.","intents":["Send multiple notifications or reports in a single workflow without stopping on first failure","Deliver batched alerts or status updates with granular error visibility","Implement retry logic at the client level based on per-message delivery status"],"best_for":["Workflows requiring multiple message types or destinations","Agents generating multi-part notifications or reports","Scenarios where partial delivery is acceptable"],"limitations":["No built-in batching or atomic multi-message delivery — each message is independent","No server-side retry logic — client must implement retries if needed","Rate limiting not visible in MCP interface — WeCom webhook may throttle rapid requests","No transaction semantics — cannot rollback or coordinate delivery across messages"],"requires":["MCP client capable of sequential tool calls","WeCom group robot webhook URL","Tolerance for partial delivery (some messages may fail)"],"input_types":["multiple MCP tool calls with message parameters"],"output_types":["array of MCP tool results with per-message HTTP status codes","multiple WeCom group messages"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-gotoolkits-wecombot__cap_6","uri":"capability://tool.use.integration.mcp.server.lifecycle.management.and.configuration","name":"mcp server lifecycle management and configuration","description":"Manages MCP server initialization, configuration loading, and webhook URL setup for WeCom group robot integration. Reads configuration from environment variables or config files, validates WeCom webhook URLs, and exposes MCP tool definitions for client discovery. Implements MCP server protocol handshake and tool schema advertisement.","intents":["Configure WeCom webhook URL and server settings without code changes","Enable MCP clients to discover available message delivery tools","Manage server startup, shutdown, and graceful error handling"],"best_for":["DevOps teams deploying MCP servers in containerized environments","Organizations standardizing on MCP infrastructure","Developers integrating WeCom messaging into MCP-native applications"],"limitations":["Configuration via environment variables only — no dynamic runtime reconfiguration","No built-in secret management — webhook URLs stored in plaintext or environment","Single webhook URL per server instance — no multi-group or multi-robot support","No health checks or monitoring endpoints exposed"],"requires":["Go runtime and MCP server dependencies","WeCom group robot webhook URL in environment variable","MCP client implementation compatible with server protocol version"],"input_types":["environment variables (WECOM_WEBHOOK_URL, etc.)","MCP protocol handshake messages"],"output_types":["MCP tool schema definitions","MCP server capability advertisement","configuration validation status"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":25,"verified":false,"data_access_risk":"high","permissions":["WeCom (WeChat Work) group with robot webhook URL configured","MCP client implementation (Claude Desktop, custom MCP host, or compatible tool)","Network connectivity from MCP server to WeCom webhook endpoint","Go runtime (artifact is Go-based MCP server)","WeCom group robot webhook URL","MCP client capable of calling tools with string parameters","Text content < 2000 characters","MCP client capable of passing markdown string parameters","Markdown content compatible with WeCom's markdown parser","Image URL accessible from MCP server OR base64-encoded image data"],"failure_modes":["Requires valid WeCom group robot webhook URL — no fallback to direct API authentication","Message delivery is asynchronous via HTTP webhooks — no guaranteed delivery confirmation or retry logic visible in MCP interface","Limited to WeCom's message type constraints (text, markdown, image, file) — no custom payload passthrough","Single-threaded or limited concurrent request handling — performance under high message volume unknown","No built-in text formatting beyond WeCom's native text capabilities","Message length constrained by WeCom API limits (typically 2000 characters)","No message threading or reply context — each message is independent","No delivery receipts or read confirmations returned via MCP interface","Markdown support limited to WeCom's subset — not all standard markdown features supported","No syntax highlighting for code blocks — language specification may be ignored","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.24,"ecosystem":0.39999999999999997,"match_graph":0.25,"freshness":0.52,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-06-17T09:51:03.041Z","last_scraped_at":"2026-05-03T14:00:15.503Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=gotoolkits-wecombot","compare_url":"https://unfragile.ai/compare?artifact=gotoolkits-wecombot"}},"signature":"JqO60kvxMJvdSW05awTkV0YDg7OZ7oAHRnB1ift22H9xzwMqOqR+JiOPkFhqyKxb+xer57BRiKStABYd8j1XBw==","signedAt":"2026-06-21T21:25:19.025Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/gotoolkits-wecombot","artifact":"https://unfragile.ai/gotoolkits-wecombot","verify":"https://unfragile.ai/api/v1/verify?slug=gotoolkits-wecombot","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}