Developer · Remote MCP server
Litmus
Grade MCP servers A to F with the open behavioral litmus. npm: full toolset; hosted: lookups only.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.polygraphso/litmus- Version
- 0.36.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-07-20
- Updated
- 2026-07-20
- Publisher
- polygraphso (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/polygraphso) · how
- Website
- polygraph.so
- Repository
- github.com/polygraphso/litmus
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://polygraph.so/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 200)
- Handshake
- polygraph 1.0.0 · protocol 2025-06-18
- Tools discovered
- 3:
check_server,list_servers,request_grade - Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @polygraphso/litmus | 0.36.0 | stdio |
How to connect Litmus
Litmus is a remote MCP server: there is nothing to install. Its endpoint is https://polygraph.so/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: @polygraphso/litmus version 0.36.0. 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 @polygraphso/litmus@0.36.0. It reads these environment variables: POLYGRAPH_API_URL and NEXT_PUBLIC_POLYGRAPH_NETWORK; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"litmus": {
"command": "npx",
"args": [
"-y",
"@polygraphso/litmus@0.36.0"
],
"env": {
"POLYGRAPH_API_URL": "<value>",
"NEXT_PUBLIC_POLYGRAPH_NETWORK": "<value>"
}
}
}
}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 |
|---|---|
| Liongard MCPLiongard config visibility: sync your estate offline, then drift-check and search it from one CLI. | Local · stdio |
| Liquibase Changelog MCP ServerConvert natural language into validated Liquibase XML or SQL changesets. 19 tools, 12 databases. | Local · stdio |
| LiquidConnect your AI agent to anything - APIs, databases, and agents; read and write, auto-discovered. | Local · stdio |
| LiteLLM Multi-Model APIAccess 100+ LLMs with one API: GPT-4, Claude, Gemini, Mistral, and more. | Local · stdio |
| Lium DocsSearch and read the Lium GPU rental docs: pods, CLI, SDK, REST API and agent guides. | Remote · HTTPLive check: ✓ handshake |
| Live MemoryPersistent, read-only codebase memory for Claude Code; ask it instead of re-reading files. | Local · HTTP |
| Live TribeJapan's largest live house show database: search shows, artists, and venues. | Remote · HTTPLive check: sign-in required |
| LiveCheck AISecure MCP runtime server for scanning and autofixing code issues. | Remote · HTTP, SSELive check: sign-in required |