mcpbeat

Self Inspect MCP Server

io.github.ejentum/self-inspect-mcp
answering

Self Inspect MCP is answering right now. Last checked 3 min ago. 20 installs a week from npm. It exposes 1 tools. Last commit 13 Jun 2026.

Send a thought, get one metathought that makes your agent inspect its own assumptions. Keyless.

Installs per day peak 23 · avg 6 · -13% w/w
a month agotoday
Uptime history 41 hours of history
41 hours agonow
100.0%
Uptime 24h
91 of 91 checks
1
Tools
read from the server
278 ms
Response time
average over 24h
20
Installs / week
npm and PyPI

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

run in your terminal
claude mcp add self-inspect-mcp --transport http https://api.ejentum.com/self-inspect-mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "self-inspect-mcp": {
      "url": "https://api.ejentum.com/self-inspect-mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.self-inspect-mcp]
url = "https://api.ejentum.com/self-inspect-mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "self-inspect-mcp": {
      "url": "https://api.ejentum.com/self-inspect-mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "self-inspect-mcp": {
      "url": "https://api.ejentum.com/self-inspect-mcp"
    }
  }
}

Available tools 1

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

self
self_inspect
Self-Inspect. Express a thought, or describe the task you are working on, and you always get back ONE metathought: a short abstract question that makes you inspect your own task and assumptions before continuing. Use it whenever you want a self-check: after forming a hypothesis, before committing to an answer, when a long chain feels like it has drifted, when you notice you are agreeing to please, or when you are about to assert something from memory. There is no failure case: it always returns a metathought to question yourself with, selected by a transparent heuristic over an open CSV (no LLM). Keyless and free. DO NOT call for factual lookups or as a substitute for doing the task. Absorb the question and act on it; do not echo it verbatim to the user.

Endpoints

URLTransportStateLatencyChecked
https://api.ejentum.com/self-inspect-mcp streamable-http answering 425 ms 3 min ago

Self Inspect MCP — questions

Answers built from our own checks of this server.

What can Self Inspect MCP do?
It exposes 1 tools, read directly from the server on our last check. Among them: self_inspect. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Self Inspect MCP working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 278 ms. The bar chart above shows every period we have measured.
How do I connect Self Inspect MCP?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Self Inspect MCP need an API key?
No. Self Inspect MCP completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Self Inspect MCP?
It answers our handshake in 278 ms on average, which is faster than 49% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use Self Inspect MCP?
The npm package self-inspect-mcp was installed 20 times in the last week. Week over week that is -13%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Self Inspect MCP open source?
Yes — it is published under the MIT licence, written in JavaScript and 7 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.