Other · Remote MCP server
Self Inspect MCP
Send a thought, get one metathought that makes your agent inspect its own assumptions. Keyless.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.ejentum/self-inspect-mcp- Version
- 0.1.1
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-06-11
- Updated
- 2026-06-11
- Publisher
- ejentum (GitHub) · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/ejentum) · how
- Repository
- github.com/ejentum/self-inspect-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://api.ejentum.com/self-inspect-mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- No - no answer within 15 s
- Handshake
- -
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | self-inspect-mcp | 0.1.1 | stdio |
How to connect Self Inspect MCP
Self Inspect MCP is a remote MCP server: there is nothing to install. Its endpoint is https://api.ejentum.com/self-inspect-mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: self-inspect-mcp version 0.1.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y self-inspect-mcp@0.1.1.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"self-inspect-mcp": {
"command": "npx",
"args": [
"-y",
"self-inspect-mcp@0.1.1"
]
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from ejentum (GitHub)
| Server | Runs |
|---|---|
| Ejentum MCPReasoning, code, anti-deception, memory harness MCP tools. Stdio or HTTPS api.ejentum.com/mcp. | Remote & Local · HTTP, stdioLive check: ✗ no handshake |
More other servers
| Server | Runs |
|---|---|
| SeglySplit character art into named layers and export PSDs for Live2D and Spine. | Remote · HTTPLive check: sign-in required |
| SegmentSegment MCP Pack - wraps the Segment Public API (https://api.segmentapis.com). | Remote · HTTPLive check: ✓ handshake |
| segment-mcpRead-first MCP server for Twilio Segment: routing, stale sources, delivery health, governance. | Local · stdio |
| Seismicportal MCPEarthquakes from the EMSC seismic portal. No key required. | Local · stdio |
| SelfpingText your own phone when a run finishes or needs you. A key can only message its own number. | Remote · HTTPLive check: ✓ handshake |
| SellbaseOpen source commerce in your own Supabase: catalog, checkout, orders and bookings, run by your AI. | Local · stdio |
| Seller AssistantConnect AI clients to Seller Assistant workflows for Amazon wholesale operations. | Remote · HTTPLive check: sign-in required |
| SemahashContent-addressed semantics: fail-closed handshakes over 457 cognitive patterns. | Local · stdio |