io.github.ejentum/self-inspect-mcp

Name: io.github.ejentum/self-inspect-mcp
Author: io.github.ejentum

MCPcommunitylive

v0.1.1io.github.ejentumUnknownUpdated 3mo agonpm GitHub

Send a thought, get one metathought that makes your agent inspect its own assumptions. Keyless.

MCP server exposing one tool, . The agent passes a one or two sentence description of what it is doing; the tool returns a single self-inspection metathought (a concrete self-check) or a no-match note. Keyless and free. What it does, measured: in a 30-turn design session (Claude Sonnet 4.6), agents calling each turn surfaced ~3.5x more decision-forks (assumptions, edge cases, preconditions) than…

Endpoint healthlive

checked 9 days ago · 521ms

100% of the last 5 checks reached this endpoint

Works in

ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

8GitHub stars

2Forks

3mo agoLast update

Package

Authorio.github.ejentum

LicenseUnknown

Version0.1.1

Sourcemcp-registry

npmself-inspect-mcp

GitHubejentum/self-inspect-mcp

SBOMCycloneDX 1.6 ↓

Trust Status

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/20

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/5

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

—npm Trusted Publishing (Sigstore)+0/5

→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo

—npm maintainer match+0/5

→ Earned once your identity is verified above and that login is an npm maintainer of this package

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

Provenance—

Dependencies✓ 60 resolved+ · none vulnerable

Tool surface1 tool · none privileged

Security scan✓ Cleanv0.1.1 · 3mo agoHow well does this scan work?

EvalsNone

IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

1 tool · none privileged

Statically extracted from the published packagev0.1.1 · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

self_inspectNo description published

This tool published no description. Forge does not invent one.

0 of 1 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Keywords

mcp

Alternatives

Comparing tool surfaces…

io.github.ejentum/self-inspect-mcp

Tools

Tools exposed

No dependency coverage