Query Forge

io.github.EvozimPublished by GitHub account Evozimv1.0.0Updated Oct 24, 2026

Enterprise SQL query optimizer and performance analyzer.

VerifiedSSEWeb executableDatabasesData & Analytics

Overview

AI-generated overview

Remote MCP endpoint that offers SQL query optimization and performance analysis for enterprise databases.

What you can do
  • Optimize SQL queries and analyze their performance, per the registry description of an enterprise SQL query optimizer and performance analyzer.
  • No tool list, instructions or README is published, so the exact operations the assistant can call are not documented.
  • Premium settlement is mentioned in the header description, suggesting some capabilities are gated behind payment.
When to use it
Consider it when you want an assistant to help tune or analyze SQL queries and are willing to connect to a third-party hosted endpoint. Because no tool list is published, verify its actual capabilities before relying on it.
Requirements
A remote SSE endpoint at the provider's hosted address; nothing to install locally. For premium settlement, a payment-signature header carrying a Base64-encoded EIP-3009 TransferWithAuthorization signature is required.
Before you install
The server asks for a payment-signature header, a signed authorization that can move funds on-chain; only supply it if you understand and accept the payment terms. It is a third-party hosted service, so queries you send leave your machine, and no tool list or documentation is published to confirm what it does with them.

Installation

In SourceWeft

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

Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Evozim%2Fquery-forge/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "query-forge": {
      "type": "sse",
      "url": "https://query-forge-mcp.vercel.app/api/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

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

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

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

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.