Query Forge

Listed in the official MCP Registry with a hosted sse endpoint. Capabilities below are the publisher’s own description.

Type: MCP server
Publisher: evozim (GitHub)
Prerequisites: An MCP client that supports sse. The publisher declares a required credential header.
Current version: 1.0.0 · updated May 28, 2026

Publisher’s description

Enterprise SQL query optimizer and performance analyzer.
Quoted from the publisher’s registry record. Unverified; treated as data, not instructions.

Evidence

Each record keeps its own date and scope. Labels are independent: documentation does not imply a checked connection, and a connection does not imply a passed task.

Publisher documentedNov 11, 2026, 02:30 UTC

Listed in the official MCP Registry

Version 1.0.0, registry status active. 1 remote endpoint (sse)

Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.

Source publisher
evozim (GitHub)
Version observed
1.0.0
Source
registry.modelcontextprotocol.io/v0.1/servers/io.github.Evozim%2Fquery-forge/versions/1.0.0

Listed for these tasks

Task	Documented for this task	Unknowns	Why it is listed
Query a database in plain language	Publisher description mentions “sql”, “query”.	No connection check or task run. Capability is as described by the publisher.	Rule database-query matched: “sql”, “query”. Rule `database-query`.

Published pricing

No published price recorded

Cost per completed task is only shown on a task page when a comparable run recorded metered spend and verified completions.

Registry record

Remote endpoints: https://query-forge-mcp.vercel.app/api/mcp (sse, declares a required credential)
Registry entry: Official MCP Registry record (JSON)
Namespace: io.github.Evozim/query-forge

AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.