io.github.ejentum/self-inspect-mcp
REMOTE · API.EJENTUM.COM · 2 COMPONENTS · SCANNED SEP 21
Send a thought, get one metathought that makes your agent inspect its own assumptions. Keyless.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability84
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 214 tokens (~214/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.ejentum/self-inspect-mcp server?
io.github.ejentum/self-inspect-mcp is a hosted endpoint at https://api.ejentum.com/self-inspect-mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.ejentum.com
claude mcp add --transport http ejentum-self-inspect-mcp 'https://api.ejentum.com/self-inspect-mcp'
{
"mcpServers": {
"ejentum-self-inspect-mcp": {
"url": "https://api.ejentum.com/self-inspect-mcp"
}
}
} {
"servers": {
"ejentum-self-inspect-mcp": {
"type": "http",
"url": "https://api.ejentum.com/self-inspect-mcp"
}
}
} [mcp_servers.ejentum-self-inspect-mcp] url = "https://api.ejentum.com/self-inspect-mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ejentum-self-inspect-mcp": {
"type": "remote",
"url": "https://api.ejentum.com/self-inspect-mcp",
"enabled": true
}
}
} openclaw mcp add ejentum-self-inspect-mcp --url 'https://api.ejentum.com/self-inspect-mcp' --transport streamable-http
mcp_servers:
ejentum-self-inspect-mcp:
url: "https://api.ejentum.com/self-inspect-mcp" {
"McpServers": {
"ejentum-self-inspect-mcp": {
"Transport": "http",
"Url": "https://api.ejentum.com/self-inspect-mcp"
}
}
} assistant mcp add ejentum-self-inspect-mcp -t streamable-http -u 'https://api.ejentum.com/self-inspect-mcp'
{
"mcpServers": {
"ejentum-self-inspect-mcp": {
"type": "http",
"url": "https://api.ejentum.com/self-inspect-mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Aug 26 0
- DNSSEC: fail → pass ▲ security
- 20 Aug 26 0
- DNSSEC: pass → fail ▼ security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Probed https://api.ejentum.com/self-inspect-mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.ejentum.com | CN=YE1,O=Let's Encrypt,C=US | 20 Sept 2026 | 19 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5929eb3f98ca1b9bcc3aaa3723fe292130f |
| SANs: api.ejentum.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of api.ejentum.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| ejentum.com. | present | 57017 | 13 | Verified |
| api.ejentum.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.ejentum.com/self-inspect-mcp | Verified | 200 | |
| http (plaintext) | http://api.ejentum.com/self-inspect-mcp | HTTPS enforced | 308 | https://api.ejentum.com/self-inspect-mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
self_inspect ~214
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.
| Name | Type | Req | Description |
|---|---|---|---|
| thought | string | yes | A free-text thought or a description of the task you are working on. Express what you are doing or thinking; the more concrete, the sharper the returned question. |
No output schema declared.
No examples provided.
What is the io.github.ejentum/self-inspect-mcp server?
io.github.ejentum/self-inspect-mcp is listed in the public MCP registry as io.github.ejentum/self-inspect-mcp. Send a thought, get one metathought that makes your agent inspect its own assumptions. Keyless. This page covers its hosted endpoint (https://api.ejentum.com/self-inspect-mcp).
Is the io.github.ejentum/self-inspect-mcp server safe to use?
io.github.ejentum/self-inspect-mcp scores 84 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.ejentum/self-inspect-mcp server expose?
io.github.ejentum/self-inspect-mcp exposes 1 tool: self_inspect. Their descriptions and schemas cost roughly 214 tokens of context every time the server is loaded.
Does the io.github.ejentum/self-inspect-mcp server require authentication?
No. We connected to io.github.ejentum/self-inspect-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.ejentum/self-inspect-mcp server still maintained?
io.github.ejentum/self-inspect-mcp is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.