$ loading_
Explore weclapp API entities, endpoints, and relationships with optional live GET checks.
This MCP tool is described as an offline knowledge server for the weclapp REST API v2, with optional live GET probes against a tenant. It is open source under MIT and does not declare fixed remote endpoints or required secrets; no clear high-risk red flags are evident, but local execution capability and optional live probing warrant caution.
The materials explicitly state that no keys or environment variables are required; based on available facts, it does not require preconfigured sensitive credentials, so credential exposure appears limited. However, the description mentions live GET probes against a tenant, which may involve tenant access credentials at runtime; the lack of documentation leaves this detail unconfirmed.
No fixed remote host is declared in the system metadata, but the feature description includes 'optional live GET probes against a tenant,' indicating the ability to make network requests to a user-specified weclapp tenant when enabled. This is a normal capability for such a tool, and there is no clear evidence of data being sent to unknown or unrelated endpoints.
The system marks it as executes-code, meaning this MCP runs local service code/processes. That is an inherent capability of MCP tools; the materials do not show requests for unusual system privileges, unrelated command execution, or clearly deceptive behavior, so this is caution rather than high risk.
The description emphasizes 'offline knowledge about entities, endpoints, and relationships,' suggesting it mainly accesses bundled local knowledge data; if live probing is enabled, it would also read tenant-related API response data. The available materials do not indicate broad file scanning, local file writes, or data access beyond its API exploration purpose, but the missing README makes the exact access scope less transparent.
Positive factors include an auditable open-source repository and an MIT license, which materially reduce supply-chain risk. Caution remains because the source is a third-party registry, community adoption is 0 stars, maintenance status is unknown, and documentation is minimal, so trust and ongoing maintenance evidence are limited.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "weclapp-api-knowledge-mcp" yet — see the docs or source repo.
Please find the entities, available GET endpoints, and relationships related to sales orders in weclapp REST API v2, and organize them into a clear list.
A structured list of sales-order-related entities, endpoints, and their relationships.
Please inspect the article entity in weclapp, identify its REST API v2 endpoint, and run a live GET probe if available to verify whether it can be read successfully.
Entity details, endpoint information, and the live GET probe result with read-access status.
Using the weclapp API knowledge, map the relationships between customer, contact, and salesOrder, and explain the key fields to watch during integration development.
An explanation of entity relationships and key field recommendations for integration development.
Lets LLMs manage WeCom customers, tags, group chats, and mass messaging.
Manage files, monitor systems, keep notes, and fetch weather via MCP.
Manage WEEEK tasks, projects, boards, and time tracking via API.
Production-ready MCP server for query normalization, retrieval, and RAG prompt building.
Load and explore OpenAPI specs to inspect endpoints, parameters, and schemas.
Discover APIs from codebases, run tests, and generate role-based QA audit reports.