Developer Launches Free Client-Side Toolkit With 52+ Privacy-First Utilities

·2 views

A developer has built OmniTool Hub, a browser-based suite of over 52 developer and AI utilities that runs entirely on the client side with no server-side data transmission. The tool addresses privacy concerns with traditional online utilities, which often send sensitive payloads to remote servers or display intrusive ads. It leverages the W3C WebCrypto API and WebAssembly to process data locally, enabling full offline functionality. Utilities include a JWT decoder, RSA key generator, AI prompt security scanner, DeepSeek-R1 reasoning chain extractor, and CSS design tools. The platform requires no sign-up and is freely accessible, with the developer inviting community feedback for future improvements.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

AWS Expands Aurora DSQL to 5 New Regions, Adds PHP Connector and New Relic MCP Integration

Amazon Web Services has expanded Aurora DSQL, its distributed serverless SQL database, to five additional regions including São Paulo, Mumbai, Singapore, Stockholm, and Hong Kong, bringing total coverage to 19 regions. The expansion addresses a key adoption barrier — high latency — for developers and businesses outside previously supported geographies, particularly in Latin America and Asia Pacific. AWS also released an official Aurora DSQL connector for PHP, which natively handles IAM authentication, token renewal, and retry logic with exponential backoff, eliminating the need for developers to build these mechanisms manually. Additionally, Amazon Q can now interface with New Relic's AI agents via the Model Context Protocol, enabling incident investigation, root cause analysis, and NRQL queries directly within the Q chat interface. Despite these advances, Aurora DSQL still carries compatibility limitations compared to full PostgreSQL, meaning regional and language support improvements do not resolve underlying feature-set maturity concerns.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Nabu.NET library converts ASP.NET Core Web APIs into MCP servers with one attribute

A new open-source library called Nabu.Mcp.AspNetCore allows developers to expose existing ASP.NET Core Web API endpoints as Model Context Protocol (MCP) tools by adding a single [McpTool] attribute. The library preserves the full ASP.NET Core middleware pipeline, meaning authentication, authorization, validation, and rate limiting remain fully enforced on every MCP call. Tool descriptions are automatically derived from XML documentation, while input schemas are generated from CLR types, reducing the need for manual configuration. Per-caller tool visibility is supported, so the tools/list response is filtered according to each caller's authorization policies. The package is MIT licensed, targets netstandard2.0 through net10.0, and is available on NuGet under the name Nabu.Mcp.AspNetCore.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How to Build a .NET MCP Client That Connects to and Calls MCP Servers

A developer tutorial on DEV Community explains how to consume Model Context Protocol (MCP) servers from a .NET application, positioning the app itself as the client rather than relying on tools like Claude Desktop. The guide uses the ModelContextProtocol.Core SDK to establish a connection via stdio transport, which launches the MCP server as a child process and performs a protocol handshake. Three core steps are outlined: connecting through a transport layer, discovering available tools and their schemas at runtime, and invoking those tools by name with arguments. The tutorial highlights that runtime tool discovery distinguishes MCP clients from standard API clients, since no pre-generated proxy classes are involved. It also warns developers to properly dispose of the client object to avoid orphaned child processes, and recommends listing available tools before making any calls to avoid debugging mismatched tool names.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Microsoft MCP SDK lets .NET apps act as MCP clients to consume tool servers

Developers building .NET applications can now use the ModelContextProtocol SDK to connect their apps directly to MCP servers as clients, rather than relying on third-party tools like Claude Desktop. The process involves three core steps: connecting to a server via stdio or HTTP transport, discovering available tools at runtime, and invoking them by name with arguments. Unlike traditional API clients, there are no pre-generated proxy classes — tools and their schemas are received dynamically, requiring code that adapts at runtime. The stdio transport works by launching the MCP server as a child process, with the SDK handling the protocol handshake automatically. A key practical tip highlighted is to always print the discovered tool list before making calls, since tool names are SDK-derived and may differ from the original C# method names in the server code.

0 comments Read more at DEV Community