SqlCertForge

com.detentpointPublished by detentpoint.comv2.0.2Updated Oct 29, 2026

SQL Server and SSRS TLS certificate binding, rotation and audit. Read-only tools free.

VerifiedSTDIODesktop onlyDatabasesSecurity & Monitoring

Overview

AI-generated overview

Local MCP server for SQL Server and SSRS TLS certificate binding, rotation and audit, with free read-only tools.

What you can do
  • Inspect TLS certificate bindings for SQL Server and SSRS instances.
  • Rotate and rebind certificates as part of certificate lifecycle work.
  • Audit certificate configuration and report on it.
  • Read-only tools are available without a license; the remaining tools require a license file.
When to use it
Useful when you administer SQL Server or SSRS over TLS and want an assistant to inspect, rotate or audit certificate bindings instead of doing it by hand. Start with the free read-only tools to check whether it fits your environment.
Requirements
Runs as a local stdio process installed from the NuGet package DetentPoint.SqlCertForge.Mcp, so a .NET runtime and a Windows desktop environment are needed. A license file is required for the non-read-only tools, supplied via the SQLCERTFORGE_LICENSE_FILE environment variable; leave it unset for the free read-only tools.
Before you install
The server can rotate and rebind TLS certificates, which changes live SQL Server and SSRS configuration and can break connections if done incorrectly; test before using it on production. The license file path is passed through SQLCERTFORGE_LICENSE_FILE, so keep that file protected. It is desktop-only and not available as a web executable.

Installation

In SourceWeft

  1. Open SqlCertForge in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v2.0.2LatestOct 29, 2026

Score

15% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.