ai.smithery/DynamicEndpoints-autogen_mcp
Create and manage AI agents that collaborate and solve problems through natural language interacti…
Installation
Claude Desktop config (remote)
{
"mcpServers": {
"ai-smithery-dynamicendpoints-autogen-mcp": {
"type": "streamable-http",
"url": "https://server.smithery.ai/@DynamicEndpoints/autogen_mcp/mcp"
}
}
}Cursor config
{
"mcpServers": {
"ai-smithery-dynamicendpoints-autogen-mcp": {
"url": "https://server.smithery.ai/@DynamicEndpoints/autogen_mcp/mcp"
}
}
}Security Report
Score Breakdown
Findings (6)
Truncated and Vague Server Description
The server description is incomplete (ends with '…') and provides minimal clarity about actual functionality. 'Create and manage AI agents that collaborate' is extremely broad and doesn't specify what operations are performed, what data is accessed, or what constraints exist.
Remote HTTP Endpoint Without Visible Authentication
Server operates via streamable-http on a remote URL (https://server.smithery.ai/@DynamicEndpoints/autogen_mcp/mcp). Remote endpoints are inherently higher risk as they accept connections from the internet. No authentication mechanism is documented.
Overly Broad Capability Claims
The server claims to 'create and manage AI agents' and facilitate 'collaboration' and 'problem solving' - this is extremely broad scope. Without tool definitions visible, it's impossible to verify what actual capabilities exist or if they're proportional to the stated purpose.
Tool Definitions Unavailable for Audit
Tool definitions were not fetched from the server, making it impossible to audit for prompt injection, input validation, data exfiltration patterns, or hidden instructions. This is a significant gap in security assessment.
Positive Trust Signal: Repository Available
The server has an associated GitHub repository (https://github.com/DynamicEndpoints/Autogen_MCP), which provides some transparency and allows for source code review.
Semantic Analysis Summary
This server presents moderate-to-high risk due to its remote HTTP endpoint, vague and truncated description, and overly broad capability claims without visible constraints. The unavailability of tool definitions prevents thorough security analysis. While the GitHub repository is a positive trust signal, the combination of remote exposure, unclear scope, and inability to audit actual tools warrants caution before deployment.
Last scanned 1h ago
Details
- Version
- 0.3.0
- Transport
- streamable-http
- Capabilities
- Repository
- DynamicEndpoints/Autogen_MCP