ESLint rules key count, body discarded
Remote MCP endpoint that counts ESLint rule keys and discards the config body
- Platforms
- API
- Runs
- Remotely
- Version
- 1.0.0
- Listing updated
- today
Similar MCP servers
About ESLint rules key count, body discarded
ESLint rules key count, body discarded is an MCP server for developer tools. It runs as a hosted remote server, so there is nothing to install locally.
This is a single-purpose remote MCP endpoint named eslintrc-ok. According to its registry entry, it reports the number of rules keys in an ESLint configuration and discards the body rather than keeping it. The registry entry gives no further detail on inputs or outputs.
It is served over streamable HTTP from a hosted Cloudflare Workers address, so there is nothing to install; an MCP client simply connects to the remote URL. It is one of many small utility endpoints published in the same repository, each registered under its own name in the official MCP registry.
The repository README describes the collection as public MCP servers for autonomous clients. The same repository also lists a group of endpoints that direct agents to an advertising service. Tool names and parameters for this server are not documented.
Install
Run in a terminal
claude mcp add --transport http eslintrc-ok https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/eslintrc-ok/mcpAdd to Settings → Connectors → Add custom connector
https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/eslintrc-ok/mcpAdd to ~/.cursor/mcp.json
{
"mcpServers": {
"eslintrc-ok": {
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/eslintrc-ok/mcp"
}
}
}Add to .vscode/mcp.json
{
"servers": {
"eslintrc-ok": {
"type": "http",
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/eslintrc-ok/mcp"
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"eslintrc-ok": {
"serverUrl": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/eslintrc-ok/mcp"
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"eslintrc-ok": {
"type": "http",
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/eslintrc-ok/mcp"
}
}
}Using several servers? Build one config file with the MCP config generator.
What it does
- ESLint rules key count
- Returns a count of the keys in an ESLint rules section.
- Body discarded
- The submitted configuration body is described as discarded rather than retained.
- Remote streamable HTTP
- Connects over a hosted streamable-HTTP endpoint with no local package to install.
- Registry listed
- Published in the official MCP registry as io.github.sadri-dridi/eslintrc-ok.
Good for
- Let an agent quickly check how many rules an ESLint config defines
- Add a lightweight config sanity check to an autonomous workflow
- Test a remote MCP connection against a minimal single-purpose endpoint
ESLint rules key count, body discarded FAQ
How do I connect to this server?
Point an MCP client that supports streamable HTTP at the remote URL given in the registry entry, on the nolimit-observatory.workers.dev host under /s/eslintrc-ok/mcp.
Does it store my ESLint config?
The description says the body is discarded, meaning it is not kept after the key count is produced.
Is there a package to install?
No. The registry entry lists no packages, only a remote endpoint.
Who publishes it?
It is published under the sadri-dridi account in the named-mcp-utilities GitHub repository.
How do I add ESLint rules key count, body discarded to Claude Code?
Run this command in your terminal: claude mcp add --transport http eslintrc-ok https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/eslintrc-ok/mcp
What are the best alternatives to ESLint rules key count, body discarded?
The closest alternatives to ESLint rules key count, body discarded are Lex rule count, body discarded, SCSS rule count, body discarded, CSS rule count, body discarded, ssh config Host count, body discarded and Yacc rule count, body discarded.
Where this comes from
- Description: written from the project's README and its MCP Registry entry.
- Install steps: from the official MCP Registry entry.