Graneth

com.granethv0.7.1Updated Oct 7, 2026

Pre-flight check for AI coding agents: hallucinated packages + secrets, 6 ecosystems, no account.

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Pre-flight check for AI coding agents that flags hallucinated packages and exposed secrets across six ecosystems, with no account required.

What you can do
Graneth is a pre-flight checking service for AI coding agents. According to its registry description, it detects hallucinated packages and secrets across six ecosystems, and it can be reached either as a remote endpoint or through a local npm package over stdio. No tool list is published, so the exact operations are not documented here.
When to use it
Worth considering when an assistant writes or reviews dependency manifests and you want a check for non-existent packages or leaked credentials before code is committed or installed. Less useful if you only need general code assistance rather than dependency and secret validation.
Requirements
No authentication, environment variables, or headers are declared. It can run as a remote endpoint or as the npm package @graneth/mcp-server over stdio, which requires a local Node.js runtime and network access for the remote mode.
Before you install
The server inspects code and dependency data, which may be sent to a third-party service; review what is transmitted before pointing it at private repositories. No credentials are requested by name in the manifest, but a secret-scanning tool may surface secret values in its output, so handle results carefully.

Installation

In SourceWeft

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

Web executable via Streamable HTTP. 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/com.graneth%2Fmcp-server/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": {
    "graneth": {
      "type": "http",
      "url": "https://graneth.com/api/mcp"
    }
  }
}

README

This repository has no README.

Tools

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

Version history

1
  1. v0.7.1LatestSep 16, 2026

Score

25% 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

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

  • Auth declaredRequired10 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
  • 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.