Developer · Remote MCP server
Graneth
Pre-flight check for AI coding agents: hallucinated packages + secrets, 6 ecosystems, no account.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.graneth/mcp-server- Version
- 0.7.1
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-08-07
- Updated
- 2026-08-07
- Publisher
- com.graneth
- Namespace
- Namespace verified by the MCP Registry via the domain graneth.com · how
- Listed under
- Flights MCP servers
- Website
- graneth.com/docs
- Repository
- github.com/zubovartemiy/graneth-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://graneth.com/api/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 404)
- Handshake
- HTTP 404
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @graneth/mcp-server | 0.7.1 | stdio |
How to connect Graneth
Graneth is a remote MCP server: there is nothing to install. Its endpoint is https://graneth.com/api/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: @graneth/mcp-server version 0.7.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @graneth/mcp-server@0.7.1.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@graneth/mcp-server@0.7.1"
]
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| GRAFOMEM CGR CaptureRecord agent judgments and their real outcomes on GRAFOMEM Cloud. Capture now, score later. | Local · stdio |
| GrafyxReal-time codebase graph for AI assistants: call graphs, dependencies, symbol lookup. | Local · stdio |
| GrainRun SQL queries and inspect database schemas through safe, visible MCP tools. | Local · stdio |
| GramClawManage Telegram outreach, campaigns, follow-ups, conversations, and pipelines from an MCP client. | Remote · HTTP |
| GraphifySearch indexed code, trace dependencies, assess change impact, and recall repository memory. | Remote · HTTPLive check: sign-in required |
| GraphkeeperMines git history for file co-change patterns into a queryable knowledge graph via MCP. | Local · stdio |
| GraphPilotStructural memory for coding agents: callers, callees, blast radius and symbols over MCP. | Local · stdio |
| GraphqlTurn any GraphQL API into MCP tools. Zero config, zero code. | Local · stdio |