{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"smithery_adnocad-hady-mcp","slug":"adnocad-hady-mcp","name":"hady_mcp","type":"mcp","url":"https://github.com/adnocad/hady_mcp","page_url":"https://unfragile.ai/adnocad-hady-mcp","categories":["mcp-servers"],"tags":["mcp","model-context-protocol","smithery:adnocad/hady_mcp"],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"smithery_adnocad-hady-mcp__cap_0","uri":"capability://tool.use.integration.mcp.server.protocol.implementation.and.endpoint.exposure","name":"mcp server protocol implementation and endpoint exposure","description":"Implements the Model Context Protocol (MCP) server specification, exposing a standardized interface that allows Claude and other MCP-compatible clients to discover and invoke server capabilities through JSON-RPC 2.0 message passing. The server handles protocol negotiation, capability advertisement via the initialize handshake, and request/response routing according to MCP specification, enabling bidirectional communication between AI clients and local/remote tools.","intents":["I want to expose my local tools and data sources to Claude so it can use them autonomously","I need to create a standardized interface that multiple AI clients can connect to without custom integration code","I want to implement a server that follows the MCP spec so it's compatible with the growing MCP ecosystem"],"best_for":["AI application developers building Claude integrations","Teams standardizing on MCP for tool orchestration across multiple AI models","Developers creating reusable tool servers for the Smithery marketplace"],"limitations":["Limited to MCP-compatible clients — cannot be used with non-MCP AI platforms without adapters","Protocol overhead adds latency compared to direct function calls — each request involves JSON-RPC serialization/deserialization","Requires proper error handling and timeout management — malformed requests or slow tool responses can block the client"],"requires":["MCP client library or compatible AI client (Claude, etc.)","Network connectivity if server runs remotely","Understanding of JSON-RPC 2.0 protocol basics"],"input_types":["JSON-RPC 2.0 requests","MCP protocol messages","Tool invocation parameters"],"output_types":["JSON-RPC 2.0 responses","MCP capability advertisements","Tool execution results"],"categories":["tool-use-integration","mcp-server"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_adnocad-hady-mcp__cap_1","uri":"capability://tool.use.integration.tool.capability.registration.and.schema.advertisement","name":"tool capability registration and schema advertisement","description":"Provides a mechanism to register discrete tools/functions with the MCP server and automatically generate JSON Schema descriptions that advertise tool signatures, parameters, and documentation to connected clients. The server maintains a capability registry that clients query during initialization, enabling Claude and other AI clients to discover available tools and understand their input/output contracts without hardcoded knowledge.","intents":["I want to register my custom functions so Claude knows what tools are available and how to call them","I need to generate and maintain tool schemas automatically so they stay in sync with my implementation","I want clients to discover my tools dynamically without me having to manually document their signatures"],"best_for":["Developers building extensible tool servers with dynamic capability loading","Teams maintaining multiple tools that need consistent schema documentation","Builders creating plugin systems where tools are registered at runtime"],"limitations":["Schema generation accuracy depends on implementation — complex types or custom validation rules may not translate to JSON Schema automatically","No built-in versioning for tool schemas — breaking changes require careful client coordination","Limited to tools that can be expressed as JSON Schema — some complex type systems may require manual schema definition"],"requires":["Tool implementation in supported language/runtime","JSON Schema understanding for complex parameter definitions","MCP server instance to register tools with"],"input_types":["Function/method definitions","Parameter type annotations","Tool metadata (name, description, examples)"],"output_types":["JSON Schema definitions","Tool capability listings","Parameter validation schemas"],"categories":["tool-use-integration","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_adnocad-hady-mcp__cap_2","uri":"capability://tool.use.integration.request.routing.and.tool.invocation.orchestration","name":"request routing and tool invocation orchestration","description":"Routes incoming MCP tool call requests to registered handler functions, managing parameter binding, execution context, and response serialization. The server parses tool invocation messages, validates parameters against registered schemas, executes the corresponding handler with proper error isolation, and returns results or errors back to the client in MCP-compliant format, enabling reliable tool execution with proper error propagation.","intents":["I want Claude to call my tools reliably with proper parameter validation and error handling","I need to execute multiple tools in sequence and have errors handled gracefully without crashing the server","I want to track which tools are being called and log their execution for debugging"],"best_for":["Production MCP servers handling multiple concurrent tool invocations","Developers building fault-tolerant tool orchestration systems","Teams needing audit trails and execution logging for tool calls"],"limitations":["Synchronous tool execution blocks the server — long-running tools will delay other requests unless async patterns are implemented","Parameter validation only checks schema compliance — semantic validation or business logic errors must be handled by tool implementations","No built-in retry logic — failed tool calls require client-side retry implementation or explicit tool-level retry handling"],"requires":["Tool handlers implemented and registered with the server","Parameter types matching registered JSON Schema","Error handling in tool implementations to prevent server crashes"],"input_types":["MCP tool call requests with tool name and parameters","Serialized parameter values matching schema definitions"],"output_types":["Tool execution results","Error responses with error codes and messages","Execution metadata (timing, status)"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_adnocad-hady-mcp__cap_3","uri":"capability://tool.use.integration.client.connection.lifecycle.management","name":"client connection lifecycle management","description":"Manages the full lifecycle of MCP client connections including initialization handshake, capability negotiation, session state tracking, and graceful disconnection. The server implements the MCP initialize/initialized protocol sequence, maintains per-client context, handles connection timeouts and unexpected disconnections, and ensures proper resource cleanup when clients disconnect, enabling reliable long-lived connections between clients and the tool server.","intents":["I want my MCP server to properly initialize with Claude and negotiate capabilities on connection","I need to track which clients are connected and manage per-client state or rate limits","I want the server to handle client disconnections gracefully without leaving orphaned resources"],"best_for":["Developers building production MCP servers handling multiple concurrent clients","Teams needing per-client state management or authentication","Builders creating long-lived tool servers that must handle connection churn"],"limitations":["No built-in authentication — connection security must be implemented separately (TLS, API keys, etc.)","Limited to stateless or simple stateful patterns — complex session management requires custom implementation","Connection pooling and load balancing not built-in — scaling to many clients requires external infrastructure"],"requires":["MCP-compatible client","Network connectivity (TCP/HTTP/WebSocket depending on transport)","Proper timeout configuration for your use case"],"input_types":["MCP initialize requests","Client capability declarations","Connection parameters"],"output_types":["MCP initialized responses","Server capability advertisements","Connection acknowledgments"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_adnocad-hady-mcp__cap_4","uri":"capability://tool.use.integration.smithery.marketplace.integration.and.server.registration","name":"smithery marketplace integration and server registration","description":"Integrates with the Smithery MCP server marketplace, enabling the server to be discovered, installed, and managed through Smithery's package management system. The server includes metadata (name, description, version, author) and follows Smithery conventions for packaging and distribution, allowing developers to install hady_mcp via Smithery CLI and automatically configure it in their MCP client setup.","intents":["I want to install hady_mcp from Smithery without manually cloning and configuring the repository","I need to discover what tools hady_mcp provides before installing it","I want to manage hady_mcp versions and updates through Smithery's package management"],"best_for":["Developers using Smithery as their MCP package manager","Non-technical users installing pre-built MCP servers","Teams standardizing on Smithery for MCP ecosystem management"],"limitations":["Requires Smithery CLI to be installed and configured","Limited to Smithery's supported platforms and installation methods","Version management and dependency resolution handled by Smithery — custom version pinning requires Smithery configuration"],"requires":["Smithery CLI installed","Smithery account or local Smithery configuration","Compatible platform (OS/architecture supported by Smithery)"],"input_types":["Smithery package manifest","Server metadata (name, version, description)"],"output_types":["Installed server binary/package","Configuration files","Smithery registry entries"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":25,"verified":false,"data_access_risk":"moderate","permissions":["MCP client library or compatible AI client (Claude, etc.)","Network connectivity if server runs remotely","Understanding of JSON-RPC 2.0 protocol basics","Tool implementation in supported language/runtime","JSON Schema understanding for complex parameter definitions","MCP server instance to register tools with","Tool handlers implemented and registered with the server","Parameter types matching registered JSON Schema","Error handling in tool implementations to prevent server crashes","MCP-compatible client"],"failure_modes":["Limited to MCP-compatible clients — cannot be used with non-MCP AI platforms without adapters","Protocol overhead adds latency compared to direct function calls — each request involves JSON-RPC serialization/deserialization","Requires proper error handling and timeout management — malformed requests or slow tool responses can block the client","Schema generation accuracy depends on implementation — complex types or custom validation rules may not translate to JSON Schema automatically","No built-in versioning for tool schemas — breaking changes require careful client coordination","Limited to tools that can be expressed as JSON Schema — some complex type systems may require manual schema definition","Synchronous tool execution blocks the server — long-running tools will delay other requests unless async patterns are implemented","Parameter validation only checks schema compliance — semantic validation or business logic errors must be handled by tool implementations","No built-in retry logic — failed tool calls require client-side retry implementation or explicit tool-level retry handling","No built-in authentication — connection security must be implemented separately (TLS, API keys, etc.)","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.2,"ecosystem":0.48999999999999994,"match_graph":0.25,"freshness":0.5,"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-05-24T12:16:25.062Z","last_scraped_at":"2026-05-03T15:19:37.910Z","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=adnocad-hady-mcp","compare_url":"https://unfragile.ai/compare?artifact=adnocad-hady-mcp"}},"signature":"5z5hi35dee4qlH5fog0fLt4+5vnEApP6iV9QBbuUqx/hue1fyQCR3RBKWyHKISD44xGQg7pfNg3gWaueiVtCCA==","signedAt":"2026-06-20T04:26:54.725Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/adnocad-hady-mcp","artifact":"https://unfragile.ai/adnocad-hady-mcp","verify":"https://unfragile.ai/api/v1/verify?slug=adnocad-hady-mcp","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"}}