An ASP.NET Core MCP server framework that automatically exposes HTTP endpoints, OData queries, and SignalR hub methods as MCP tools
Nabu.NET is an HTTP-based MCP server framework that discovers tools dynamically from ASP.NET Core OData endpoints and SignalR hubs via attribute-based decoration. The two advertised tool sources demonstrate good naming conventions and structured schemas for OData query options, but lack explicit per-tool descriptions in the source code provided. The OData tool exposes well-structured parameters with clear descriptions (filter, select, orderby, expand, top, skip, count, search, apply, compute) following OData standards. However, the tool registration mechanism relies on reflection and attribute discovery, making it difficult to verify complete schema definitions for all dynamically discovered tools. The SignalR hub tool source exists but lacks implementation details visible in the provided code. Tool composition is sound, separate tools for OData queries vs. SignalR invocations, but per-tool error handling and recovery guidance are not evident in the discovery layer.
Discovers MCP tools from the application's OData endpoints (Microsoft.AspNetCore.OData 8+). OData-routed actions are found through the MVC action table and invoked through the standard HTTP pipeline replay with authentication, authorization, [EnableQuery] and OData formatters.
Discovers MCP tools from SignalR hubs the application has mapped. Hub methods are published with [McpTool] / [McpIgnore] / [McpParameter] attributes and dispatched to SignalRHubToolInvoker through a synthetic in-process connection.
SignalR tool source lacks visible schema and input parameter documentation in source code. Tool definition appears to rely entirely on runtime reflection of hub method signatures, making it impossible to verify that schemas are properly documented or that parameters have descriptions.
No evidence of per-tool error handling guidance or recovery instructions in the discovery layer. When a tool fails (e.g., OData filter syntax error, SignalR method not found), the error response type and guidance mechanism are not documented, making it difficult for LLMs to determine next steps.
OData tool description is operational (explains what happens) but lacks guidance on WHEN to use it vs. other tools, and does not explain downstream usage. When should I use it? What does it return?' The current description covers operational flow but not selection criteria.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 53 | 2026-07-28+ | v2 |
SignalR tool description is minimal and does not adequately convey what the tool does or when to use it. At 'Discovers MCP tools from SignalR hubs...' the description lacks sufficient detail for LLM selection and usage planning.
Pagination and result limiting not explicitly documented for OData tool. If a queryable OData endpoint can return thousands of items, the tool must enforce a reasonable cap (20-50) and expose limit/offset parameters. The 'top' parameter exists but guidance on default/max limits is missing from the description.
Output schema documentation is not visible for either tool in the provided source. Tools must document what fields are returned so LLMs can plan downstream tool calls and extract data correctly. OData tool output depends on the endpoint's EDM, but guidance on structure is missing.