Self Inspect MCP Server

by ejentum Your server? Claim it

not responding

Self Inspect MCP is listed as active in the registry but did not answer our last check. 41 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 8 · avg 4 · +30% w/w

a month agotoday

Uptime history 91 days of history · worst day 0%

91 days agonow

0.0%

Uptime 24h

0 of 91 checks

Tools

read from the server

349 ms

Response time

average over 24h

Installs / week

npm and PyPI

Self Inspect MCP does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 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

Settings → Connectors → Add custom connector, then paste this address

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

{
  "servers": {
    "self-inspect-mcp": {
      "type": "http",
      "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	349 ms	14 min ago

Alternatives to Self Inspect MCP

same job, measured the same way

Muscle Memory

by johannesloor

MCP server that gives your agent a library of its own tested, reusable scripts.

896 installs/wk local only

Assistable

by assistable

Give any AI agent a phone: make and answer calls, get through phone menus, and send texts.

16 tools answering

Orquesta

by getorquesta

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

answering

Keyframer Inspector

by keyframer

Give your agent eyes for motion: record, slow down and test animations in mobile apps

111 installs/wk local only

SPR (Sealed Payment Record)

by luca

Seal every payment your AI agent makes as a signed record, on your own machine, with your key.

1 550 installs/wk local only

tell.dev

by tell

Message someone through your coding agent. Their agent gets your note and explains it.

answering

Master CSS

by master-co

Inspect Master CSS classes, generated CSS, and project stylesheets from your AI client.

323 installs/wk local only

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

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 0 of 91 checks got a reply (0.0%), average response time 349 ms. The bar chart above shows every period we have measured.

The registry lists Self Inspect MCP as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

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 in the form 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 many people use Self Inspect MCP?

The npm package self-inspect-mcp was installed 41 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?

The code is open source: it is published under the MIT licence, written in JavaScript and 7 stars on GitHub. The licence covers the code in the repository, not the hosted service at api.ejentum.com, which runs on its operator's own terms.