MCP server for Hasura: metadata export, SQL passthrough. Works with any self-hosted instance.
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
export_metadataHasura metadata: sources and tracked tables. Needs HASURA_ADMIN_SECRET.Hasura metadata: sources and tracked tables. Needs HASURA_ADMIN_SECRET.
No input schema was published for this tool.
run_sqlprivilegedRun read-only SQL against a Hasura Postgres source. Only SELECT/WITH queries are sent.Run read-only SQL against a Hasura Postgres source. Only SELECT/WITH queries are sent.
No input schema was published for this tool.
metadata_censusCensus of a Hasura metadata document you supply as JSON: every object kind it holds and its size, the sources, the relationship and action kind breakdown, the tables touched by the most relationships and the permission entry count. Computed locally, so it also works on a metadata file that is not a…Census of a Hasura metadata document you supply as JSON: every object kind it holds and its size, the sources, the relationship and action kind breakdown, the tables touched by the most relationships and the permission entry count. Computed locally, so it also works on a metadata file that is not a…
No input schema was published for this tool.
sql_auditprivilegedStatic audit of a SQL statement with no database connection: what it starts with, whether it is read only under a SELECT/WITH rule, the tables it names, and how many joins, subqueries, CTEs, aggregates and window functions are in it, plus what to review before running it.Static audit of a SQL statement with no database connection: what it starts with, whether it is read only under a SELECT/WITH rule, the tables it names, and how many joins, subqueries, CTEs, aggregates and window functions are in it, plus what to review before running it.
No input schema was published for this tool.
graphql_builderBuild a GraphQL document for a Hasura schema from the tables and fields you name, with a depth budget, an operation type and an optional alias, so the query can be reviewed before it is sent.Build a GraphQL document for a Hasura schema from the tables and fields you name, with a depth budget, an operation type and an optional alias, so the query can be reviewed before it is sent.
No input schema was published for this tool.
5 of 5 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
MCP server for Hasura: metadata export, SQL passthrough. Works with any self-hosted instance.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
The crawl stopped at the depth-4 limit. Anything below that level was never resolved.
The crawl stopped at the 60-package limit. The rest of the tree was never resolved.
36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)
54 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.
+42 more not listed. The counts by reason above cover all of them.
Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.