io.github.ejentum/self-inspect-mcp
REMOTE · API.EJENTUM.COM · 2 COMPONENTS · SCANNED OCT 15
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 Security60
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 404. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 10 Oct 26 −60
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- HSTS header: pass → fail ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- First check of Schema quality: unverified functional
- 28 Sept 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
- 25 Sept 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
- 26 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
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 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
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 15 Oct 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=WE1,O=Google Trust Services,C=US | 9 Oct 2026 | 7 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | b7c913808903e6600e717e5f81f46a1d |
| SANs: api.ejentum.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
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 Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 404 |
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 | HTTP error | 404 | |
| http (plaintext) | http://api.ejentum.com/self-inspect-mcp | HTTPS enforced | 301 | 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 24 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?
Its publisher declares no required credentials for io.github.ejentum/self-inspect-mcp. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
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 15 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.