{"id":"ivanmurzak-mcp-plugin-dotnet","name":"MCP-Plugin-dotnet","af_score":58.8,"security_score":47.5,"reliability_score":41.2,"what_it_does":"Provides a bridge between MCP clients (via stdio/http) and in-process .NET apps by exposing .NET methods as MCP tools/prompts/resources. The .NET app hosts an in-app SignalR client that connects to a standalone MCP bridge server (McpPlugin.Server), which then serves MCP over stdio/http transports. Tools/prompt/resource schemas are generated from C# types using ReflectorNet, with attribute-based registration and optional fuzzy method matching.","best_when":"You have a long-running .NET process (e.g., Unity Editor or desktop app) and want MCP clients to interact with that live instance through a persistent bridge and strongly-typed tool schemas.","avoid_when":"You cannot reliably secure SignalR and MCP endpoints (e.g., no TLS/auth, no allowlists, or fail-open authorization).","last_evaluated":"2026-03-30T15:40:26.098558+00:00","has_mcp":true,"has_api":false,"auth_methods":["Bearer token (server-side 'token' / MCP_PLUGIN_TOKEN) for connecting plugins","Authorization webhook gating (webhook-authorization-url) with fail-open/fail-closed behavior","Webhook token for analytics/authorization webhooks (webhook-token) via header (webhook-header default X-Webhook-Token)"],"has_free_tier":false,"known_gotchas":["Fuzzy method matching (method name match level) can lead to unexpected tool selection if multiple similar method names exist","Tool side effects may not be idempotent; callers should consider retry safety","Transport configuration matters: client-transport=stdio vs streamableHttp impacts how the bridge accepts MCP clients","Authorization webhook may be configured fail-open; for security-sensitive deployments prefer fail-closed (fail-open=false)"],"error_quality":0.0}