INDIVIDUAL MCP TOOL

naming-obviousness

Reviews naming quality and code obviousness via the isolation test, scope-length principle, and consistency audit.

clairvoyance.fyinone authenticationAvailability not checked

LIVE ENDPOINT

https://clairvoyance.fyi/mcp

No auth detected

Connect to this endpoint to inspect the live schema for naming-obviousness and invoke it with your own arguments.

{}

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

CONNECT WITH APPROVAL

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.fyi-clairvoyance-mcp]
url = "https://clairvoyance.fyi/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "fyi-clairvoyance-mcp": {
      "type": "http",
      "url": "https://clairvoyance.fyi/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: fyi-clairvoyance-mcp
Remote MCP URL: https://clairvoyance.fyi/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "fyi-clairvoyance-mcp": {
      "url": "https://clairvoyance.fyi/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "fyi-clairvoyance-mcp": {
      "type": "http",
      "url": "https://clairvoyance.fyi/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "fyi-clairvoyance-mcp",
  "transport": "streamable-http",
  "url": "https://clairvoyance.fyi/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

deep-modules — Measures module depth: whether the interface is simple relative to the implementation behind it.
module-boundaries — Evaluates where module boundaries are drawn and whether modules should be merged or split.
information-hiding — Checks for information leakage across module boundaries, including temporal decomposition and false encapsulation.
pull-complexity-down — Checks whether complexity is pushed to callers or absorbed by implementations — the direction complexity flows.
general-vs-special — Evaluates whether interfaces are appropriately general-purpose.
error-design — Reviews error handling and exception design, applying the "define errors out of existence" principle.
abstraction-quality — Evaluates whether abstractions provide a genuinely different way of thinking or are structurally shallow.
comments-docs — Reviews comment quality and documentation practices: the four comment types, comments-first workflow, and comment rot.