Self Inspect MCP Server

by ejentum Your server? Claim it

answering

Self Inspect MCP is answering right now. Last checked 15 min ago. 33 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 · +30% w/w

a month agotoday

Uptime history 48 days of history

48 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

265 ms

Response time

average over 24h

Installs / week

npm and PyPI

Nothing serious here today

Today is the operative word: we check Self Inspect MCP every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

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

URL	Transport	State	Latency	Checked
https://api.ejentum.com/self-inspect-mcp	streamable-http	answering	294 ms	15 min ago

Alternatives to Self Inspect MCP

same job, measured the same way

Orquesta

by getorquesta

Read a project's prompts, logs and agents, and send new work to the agent on your own machines.

answering

namailu.cz Agent Email

by namailu

namailu.cz gives your AI agent its own email inbox: read and send mail over MCP, with OAuth.

answering

TrueNAS SCALE

by cedricziel

Inspect and manage TrueNAS SCALE storage, shares, apps and system state with your own API key

local only

RE-call MCP Memory Server

by giulioder

Agent memory on your own Postgres that flags superseded facts and abstains instead of guessing.

928 installs/wk local only

Killbottleneck

by killbottleneck

Goal and process maps for humans and AI agents on your own server.

104 installs/wk local only

Leporis WhatsApp

by admin-rstechie

Send and read WhatsApp messages on your Leporis account from AI coding agents, via your own API key.

answering

Atmita

by atmita

Message your Atmita agent - one connection reaches all its accounts and tools, WhatsApp included.

answering

Stash

by idntty

Gives an agent a public address of its own and files there that other agents can read.

answering

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 265 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 265 ms on average, which is faster than 55% 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 33 times in the last week. Week over week that is +30%. 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 8 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.