Self Inspect MCP

A question your agent would not think to ask itself. An agent sends a thought, or a description of the task it is working on. It gets back one metathought: a short, abstract question that turns the agent's attention back onto its own task and assumptions before it continues. Not advice, not an answer. A question.

People connecting productivity tools to Claude, Cursor, VS Code, or another MCP client. The project is written in JavaScript.

VERIFIED ACTIVE

LAST COMMIT 2026-06-13 · ★ 7 · #94 OF 139 MAINTAINED PRODUCTIVITY · VERIFIED 2026-08-25

MIT · JavaScript servers · how we verify → /methodology

01 · Install Self Inspect MCP

Claude Code

claude mcp add ejentum-self-inspect-mcp --transport http https://api.ejentum.com/self-inspect-mcp

Claude Desktop / Cursor / VS Code - add to config

{
  "mcpServers": {
    "ejentum-self-inspect-mcp": {
      "url": "https://api.ejentum.com/self-inspect-mcp"
    }
  }
}

Same JSON for Cursor. For VS Code, rename the top-level key from `mcpServers` to `servers`.

Using another client? Same JSON, different key

Claude Desktop · mcpServers

Cursor · mcpServers

VS Code · servers

Windsurf · mcpServers

Zed · context_servers

Cline · mcpServers

Roo Code · mcpServers

Continue · mcpServers

LibreChat · mcpServers

Gemini CLI · mcpServers

Codex CLI · mcp_servers

Full setup guides: every client.

02 · Evidence

https://api.ejentum.com/self-inspect-mcp

transport: streamable-http

endpoint alive - responded to MCP initialize · probed 2026-08-25

Security posture

What to check before giving this server access to your agent - from the registry, GitHub, and our own probes. We don't score safety; we show what's verifiable.

runs as local process (stdio) - runs on your machine with your user's permissions · remote - your agent's requests go to api.ejentum.com

endpoint auth accepted our unauthenticated MCP initialize - no credentials needed to connect

license MIT - declared in the repository

npm package self-inspect-mcp - unscoped; check the name against the project README before installing

registry namespace io.github.ejentum is GitHub-verified and matches the repo owner

03 · Who maintains Self Inspect MCP

self-inspect-mcp is maintained by ejentum. We track 2 MCP servers from ejentum - 2 actively maintained, 23 combined GitHub stars, oldest repo from May 2026. Full record: all servers from ejentum.

ejentum-mcp Reasoning, code, anti-deception, memory harness MCP tools. Stdio or HTTPS api.ejentum.com/mcp ★ 16

04 · Facts

repository: github.com/ejentum/self-inspect-mcp
category: productivity - ranked #94 of 139 actively-maintained productivity servers as of 2026-08-25.
registry: io.github.ejentum/self-inspect-mcp (active, first published 2026-06-11)
packages: npm:self-inspect-mcp

05 · Self Inspect MCP FAQ

What is Self Inspect MCP?

Is Self Inspect MCP still maintained?

Yes - as of 2026-08-25, its last commit was 2026-06-13. We re-verify nightly.

How do I install Self Inspect MCP?

Run `npx -y self-inspect-mcp`. You can also paste the ready-made client config above.

Does Self Inspect MCP require authentication?

No - the endpoint accepted our unauthenticated MCP initialize when probed on 2026-08-25; you can connect without credentials.

06 · Alternatives to Self Inspect MCP

Alternatives to Self Inspect MCP

Maintained productivity servers if Self Inspect MCP isn't the fit.

Pairs well with

Servers that cover what Self Inspect MCP doesn't - only shown when the pairing reason fits the companion.

More productivity MCP servers · Kitty Claw · Evc Team Relay MCP · Obsidian Sync MCP · LTD MCP · Dida365

More JavaScript MCP servers · Magpipe · Kie MCP · Taskbounty Check · ellmos FileCommander · Ux MCP Server · see all