Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.Ikalus1988/misakanet

REMOTE · MISAKANET.ORG · 2 COMPONENTS

Failure-memory layer for coding agents: search evidence-rated failure lessons by error text.

+3 this week 74 Trust /100

Last scanned (17 hours ago)

Scores higher than 60% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Memory and Knowledge

Trust breakdown (7 categories)

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 Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability60
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 4150 tokens (~518/item across 8 items; 8 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 Management40
  • Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 0
    • Tool “misakanet_submit_intake” rewrote its description, which is the text the model reads security
    • Server version: 3.18.0 → 3.19.0 functional
    • “misakanet_submit_intake” added an optional parameter “trigger” cosmetic
    • “misakanet_submit_intake” reworded the description of “verification” cosmetic
  • 16 Nov 26 +1
    • Server version: 3.17.0 → 3.18.0 functional
  • 15 Nov 26 0
    • Server version: 3.16.0 → 3.17.0 functional
  • 14 Nov 26 +1
    • Server version: 3.15.0 → 3.16.0 functional
  • 13 Nov 26 0
    • Server version: 3.13.0 → 3.15.0 functional
    • Server version: 3.11.3 → 3.13.0 functional
  • 12 Nov 26 +1
    • Server version: 3.10.1 → 3.11.3 functional
Diagnostics

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 Nov 2026 · Probed https://misakanet.org/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=misakanet.org CN=WE1,O=Google Trust Services,C=US 14 Nov 2026 12 Feb 2027 ECDSA 256 ECDSA-SHA256 1e22cc2a4c40c7d2139cdb3b9f20feb2
SANs: misakanet.org, rbc-telemetry-test.misakanet.org, *.rbc-telemetry-test.misakanet.org
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 insecure

Validation of misakanet.org. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
org. DS published 725 8 Verified
misakanet.org. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://misakanet.org/mcp Verified 200
http (plaintext) http://misakanet.org/mcp HTTPS enforced 301 https://misakanet.org/mcp
MCP tools · 8 exposed · ~4,103 tokens

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 →

Tool Tokens
misakanet_get_lesson ~370

[RETRIEVAL / READ] Fetch one public MisakaNet lesson by repository path or lesson ID. Use after misakanet_search returns a promising result to pull the full fix content. Pass `path` or `id` (path wins if both are supplied); at least one is required, and the empty call returns {error, code}. `path` must be a lesson file (lessons/<topic>/<slug>.md) — anything else is refused with code=invalid_lesson_path rather than read. Returns: object {path: string, content: string} — lesson markdown body, capped at 5000 chars per call; or {error, code}. The code says which: lesson_not_found (no such lesson — do not retry, search instead), invalid_lesson_path (the argument is not a lesson reference — fix the argument), internal_error (a service fault — retrying is reasonable). When the lesson is longer than the cap the response says so instead of pretending to be complete: {truncated: true, content_length: <full chars>, content_returned: <chars here>, full_content_url: <raw markdown>} — fetch that URL when the tail matters (the cut can fall before the Verification section). Example: misakanet_get_lesson(id='auto-merge-ci-pipeline')

NameTypeReqDescription
idstring–Lesson ID, usually the filename without .md, e.g. auto-merge-ci-pipeline. Either id or path is required.
pathstring–Lesson path relative to the repository, e.g. lessons/core/auto-merge-ci-pipeline.md — must be a file under lessons/ ending in .md (other repository files are not readable through this tool). Either p…
NameTypeReqDescription
contentstring––
errorstring––
pathstring––

No examples provided.

misakanet_me_events ~313

[READ-ONLY EVIDENCE] Return evidence of a lesson being reused. E4 is observed reuse: `search_signals` shows two or more distinct clients actually retrieved the lesson — a count of requests, never of prose. Regression-benchmark citations, helpful votes and a lesson's own `verified by:` line are E3 hints: a citation is sandbox-level evidence, a vote is one person's opinion, and a provenance line is the lesson talking about itself, so none of them can confer E4. Use to check whether a lesson is proven by real usage, not just self-reported. Provide lesson_id or lesson_path — if neither is supplied the tool returns {error}. Semantically 'misakanet_get_my_events' (evidence for the lessons your node submitted/used); kept as me_events for backward compatibility. No auth required (read-only, rate-limited). Returns: object {lesson_id, events: [{type, count|queries|sources, evidence_level}], evidence: 'E0'|'E3'|'E4', note}. Example: misakanet_me_events(lesson_id='dco-auto-fix-workflow')

NameTypeReqDescription
lesson_idstring–Lesson ID (filename stem), e.g. dco-auto-fix-workflow. Either lesson_id or lesson_path is required.
lesson_pathstring–Optional full path, e.g. lessons/core/dco-auto-fix-workflow.md. Either lesson_id or lesson_path is required.
NameTypeReqDescription
errorstring––
eventsarray––
evidencestring––
lesson_idstring––
notestring––

No examples provided.

misakanet_me_inbox ~321

[AGENT READABLE INBOX] Check the status of a previously submitted intake (question, missing_lesson, etc.) without re-submitting. Accepts an intake_id (e.g. 'issue-1234' or '1234') for question intakes, or a dedup_key (the 8-char FNV-1a key from a prior submit_intake response) for any intake. Returns: {status: 'answered'|'pending'|'converted'|'unknown', ...} — 'answered' includes the maintainer's answer, 'converted' includes the lesson_id this intake became, and 'unknown' means the lookup could not determine it, which is not the same answer as 'never happened'. Read-only, rate-limited, no auth required. Returns: object {intake_id, status, answer?, lesson_id?, issue_url?, note}. Example: misakanet_me_inbox(intake_id='issue-1528') or misakanet_me_inbox(dedup_key='9f8e7d6c')

NameTypeReqDescription
dedup_keystring–The dedup_key (8-char FNV-1a hex key) from a prior submit_intake response. Either intake_id or dedup_key is required.
intake_idstring–Question intake ID from a prior submit_intake response, e.g. 'issue-1528' or '1528'; for non-question intakes use dedup_key. Either intake_id or dedup_key is required.
NameTypeReqDescription
answerstring––
intake_idstring––
issue_urlstring––
lesson_idstring––
notestring––
statusstring––

No examples provided.

misakanet_preflight ~257

[GUARD / RISK CHECK] Check risk level before executing high-risk operations. Matches agent intent against lesson triggers to provide proactive warnings. Use before RAG builds, WSL/GPU tasks, bulk imports, or any operation that might fail. Choosing among the retrieval tools: no error yet and a task about to start → misakanet_memory_context (stdio-only); an actual error or keyword in hand → misakanet_search; something risky about to run and no error yet → this one, which returns a risk verdict and guards, not lesson content. No side effects — safe to call multiple times before acting. **Open, read-only:** anonymous calls are rate-limited; `misakanet_register` lifts the limit. Returns: object {risk_level: 'low'|'medium'|'high', intent, matched_lessons: [{id, title, domain, relevance}], guards: [string]}. Example: misakanet_preflight(intent='build RAG pipeline with ChromaDB')

NameTypeReqDescription
contextstring–Optional: additional context about the environment or setup.
intentstringyesRequired: what you plan to do (e.g. 'build RAG pipeline with ChromaDB').
NameTypeReqDescription
errorstring––
guardsarray––
intentstring––
matched_lessonsarray––
risk_levelstring––

No examples provided.

misakanet_register ~593

[ONBOARDING] Get a Bearer token for authenticated access (unlocks misakanet_write_lesson and higher rate limits). Reading needs no registration and has no daily cap: misakanet_search / misakanet_get_lesson work anonymously (a per-address burst limit protects the index; it is a speed limit, not a quota). No GitHub account or email needed, and no personal data is collected — the node is a pseudonym, not an account. Token lifetime: valid ~30 days. Pass client_id (a random UUID you generate once and keep private) to get the SAME node_id and token back on every later call and to renew them; without client_id every call creates a new node, which means your reuse evidence, receipts and history start over. `client_id` is a *name*, not the key: to renew a node, send the token it was given as `Authorization: Bearer` along with the same client_id. A renewal that presents only the name still works during a deprecation window, returns `deprecated`, and is refused once strict mode is on (`client_id_proof_required`). A fresh client_id registers as before. Still generate it randomly and keep it private — the name is how the node is found, and the token is how the caller proves it is the one that owns it. Returns: object {node_id: string, token: string, registered_at: string, agent_type: string, reused: boolean} — reused=true means an existing node was found for this client_id; reused=false means this call created a new node (so a client_id you expected to be recognised was not, and the identity you had is not attached to this token). Example: misakanet_register(agent_type='claude-code', client_id='8f14e45f-2b1c-4f3a-9d2e-7c6b5a4d3e2f') Optional referral_code: the code of the node that invited you (`misakanet` referral code, 4-16 letters/digits). Recorded against your node and counted for that code — the only place a referral has ever been recorded, since the invitation otherwise never leaves the inviting machine. Counted once per new node: calling register again with the same clie…

NameTypeReqDescription
agent_typestring–Agent type (e.g. claude-code, codex, cursor, dsh, other). Optional: an omitted value is recorded as "unknown", the same default the local surface has always used.
client_idstring–Optional stable identifier for this client (8-64 chars of A-Z a-z 0-9 . _ : -). Generate it once and reuse it so later calls return the same node instead of a new one.
NameTypeReqDescription
agent_typestring––
errorstring––
node_idstring––
referral_codestring–Optional: the referral code of the node that invited you (4-16 of A-Z a-z 0-9). Recorded on this node and counted once for that code; ignored when it is not that shape, and never blocks a registratio…
registered_atstring––
reusedboolean–Always present on success: true when an existing node was found for this client_id (the renewal path), false when this call minted a new node. A false here means any earlier client_id you thought you…
tokenstring––

No examples provided.

misakanet_search ~662

[RETRIEVAL / READ] Search MisakaNet's public failure-lesson index by error text, keyword, or topic. This is the primary read path — run it first when you hit an error, before deciding to submit anything. Choosing among the retrieval tools: an actual error or keyword in hand → this one; something risky about to run and no error yet → misakanet_preflight (the third, misakanet_memory_context, is stdio-only and covers the before-you-start case). For a known lesson ID or path, prefer misakanet_get_lesson — it skips ranking and returns the full content. detail controls progressive disclosure: compact (default, ~80 tok/lesson) for broad scans, summary (~200 tok) adds domain/tags/fix, full returns complete lesson data. FAQ: results may also include answered questions (type="faq", issue_url + answer) — if a maintainer already answered the same question, the answer surfaces here. Returns: object {results: [compact: {id, title, problem, freshness, evidence_level, score} | summary: + {domain, tags, fix} | full: the record], source, detail, query}; `score` is the ranker's relevance for that result and is omitted on the unranked fallback path. On no match: {no_match: true, suggestion, intake}. When the answer is degraded — no index loaded, or the live store refused the read and the corpus came from the snapshot — the response also carries `degraded: true`, `degraded_reasons` and a one-sentence `notice`; read it before concluding that no lesson exists. Example: misakanet_search(query='pip install timeout', domain='python', top=3)

NameTypeReqDescription
baseline_weightnumber–Override baseline score weight (0-1). Higher favors proven/popular lessons. Default: 0.15.
bm25_weightnumber–Override BM25 keyword weight (0-1). Higher favors exact keyword match. Default: 0.65. All weights must sum to 1.0.
detailstring–Progressive disclosure: compact (default, ~80 tok) includes id/title/problem/freshness/score; summary (~200 tok) adds domain/tags/fix; full returns complete lesson data with path.
domainstring–Optional domain filter such as devops, python, network, feishu, rag, fanuc, or mcp.
kindstring–Filter by kind: 'lessons' (lesson files only), 'evidence' (results with evidence_refs or verification), 'related' (cross-referenced/tag-overlap), 'all' (default). Auto-detected from query intent when…
metadata_weightnumber–Override metadata bonus weight (0-1). Higher favors matching domain/tags. Default: 0.20.
querystringyesRequired redacted error message, keyword, or topic (e.g. 'pip install timeout' or 'DCO sign-off failed').
topinteger–Maximum ranked results to return. Defaults to 5; keep small for MCP context and latency.
NameTypeReqDescription
detailstring––
filtered_by_kindstring––
intakeobject––
matched_before_filternumber––
no_matchboolean––
querystring––
resultsarray––
sourcestring––
suggestionstring––

No examples provided.

misakanet_submit_intake ~1,224

[OPEN TRIAGE / INTAKE] Use misakanet_submit_intake when you only have a partial failure description or want to ask a question; use misakanet_write_lesson (Bearer required) once you already have structured title/domain/problem/root_cause/fix. submit_intake is open, rate-limited, no Bearer — output is a GitHub issue for maintainer triage, NOT a merged lesson — its labels follow the kind: question → `needs-answer`, proposal → `needs-human-review`, a failure report → `pending-review`. Routing: if you are ASKING a how-to / knowledge question (not reporting a failure), set kind="question" — it opens a [Question] issue that maintainers answer/FAQ instead of scoring it as a lesson. If kind is omitted, the server auto-detects question-shaped content (no error/fix/verification + question phrasing). Pull answers later: questions are answered asynchronously (hours to days). Re-call this tool with the SAME problem text later and follow the returned poll_hint — the dedup response returns the maintainer's answer once it exists ({answered:true, answer}), and once your report has become a lesson it returns a conversion receipt ({converted:true, receipt, events}) naming the lesson, its path and its evidence_level; or re-run misakanet_search on the topic for FAQ hits. Every response also carries dedup_key, and poll_hint.recheck_after_seconds says when re-checking is worth it (21600s for questions, 86400s for failure reports). Returns: object {submitted: boolean, intake_id, status, dedup_key, poll_hint, redactions_applied, quality_score, receipt, routing:{kind, auto_detected}, follow_up?}; `surface_report` is the intake's **surface check**: command-shaped tokens in your submission that the public corpus has never indexed (`null` = could not check, `[]` = checked and nothing unknown). A token there is not proof it is internal — a new public tool looks the same — but if it names a private product or an internal command, describe it generically in the `problem` before replying: the mecha…

NameTypeReqDescription
contributorstring–Optional: contributor identity (GitHub username, agent name, or email). Included in issue body for attribution.
errorstring–Optional: short error message (auto-redacted).
fixstring–Optional: how it was resolved.
kindstring–missing_lesson (knowledge gap), stale_lesson (outdated lesson), new_lesson_candidate (new failure mode), question (ask for help), or proposal (a plan / product request that is explicitly not a failur…
matched_lesson_idstring–Optional: lesson ID that was checked but didn't help.
notify_emailstring–Optional: an email for the ANSWER only, and only for kind="question". Ask the user first — never invent it. It is used to send one confirmation message now and, once confirmed, one notification when…
problemstringyesRequired: the symptom first, then `## Root Cause` and `## Fix` sections when known (max 2000 chars). Reports with those sections can become lessons automatically.
sourcestring–Calling client: codex, claude-code, cursor, dsh, curl, cindy, or other.
triggerstring–Required for a lesson-shaped submission (one with a `## Root Cause`/`## Fix`, or a `fix`): the error fragment or keywords a future search would use, <= 160 chars. This is the lesson's `trigger:` fron…
verificationstring–Required for a lesson-shaped submission: how a reader confirms the fix worked, as a checkable pass/fail (<= 200 chars). This becomes the lesson's `verify:` field; without it the claim is unverifiable…
what_triedstring–Optional: what was attempted.
NameTypeReqDescription
answerstring––
answer_urlstring––
answeredboolean––
convertedboolean––
dedup_hashstring––
dedup_keystring––
duplicateboolean––
errorstring––
eventsarray––
follow_upobject––
intake_idstring––
issue_urlstring––
notestring––
pendingboolean––
poll_hintobject––
previous_issuestring––
receiptstring––
routingobject––
statusstring––
submittedboolean––

No examples provided.

misakanet_write_lesson ~363

[STRUCTURED COMMIT / VALIDATED SUBMISSION] Submit a complete, structured failure lesson (title/domain/problem/root_cause/fix) as a formal submission. Requires authentication (Bearer token in header) — this is the 'validated author' path, not open triage. Output goes through lesson-gate/lint/review and becomes a versioned lesson in the git repo. For quick open reports when you only have a partial failure description, use misakanet_submit_intake instead (no Bearer). Lessons are immutable once merged — corrections go through a new intake/PR, so there is intentionally no misakanet_update_lesson/misakanet_delete_lesson. Returns: object {lesson_id: string, status: 'pending_review', quality_score: number}; or {submitted: false, error}. Example: misakanet_write_lesson(title='pip timeout behind proxy', domain='python', problem='...', root_cause='...', fix='...')

NameTypeReqDescription
contributorstring–Optional: contributor identity (GitHub username, agent name, or email). Included in lesson frontmatter for attribution.
domainstringyesDomain: devops, python, network, feishu, rag, fanuc, mcp, etc.
fixstringyesHow to fix it (required).
problemstringyesWhat failed (required).
root_causestringyesWhy it failed (required).
sourcestring–Source: codex, claude-code, cursor, dsh, curl, cindy, etc.
tagsstring–Comma-separated tags.
titlestringyesShort descriptive title.
verificationstring–How to confirm the fix works.
NameTypeReqDescription
errorstring––
lesson_idstring––
quality_scorenumber––
statusstring––
submittedboolean––

No examples provided.

Install

How do I install the io.github.Ikalus1988/misakanet MCP server?

io.github.Ikalus1988/misakanet is a hosted endpoint at https://misakanet.org/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 · misakanet.org

# add to Claude Code
claude mcp add --transport http ikalus1988-misakanet 'https://misakanet.org/mcp'
Common questions

What is the io.github.Ikalus1988/misakanet MCP server?

io.github.Ikalus1988/misakanet is an MCP server listed in the public MCP registry as io.github.Ikalus1988/misakanet. Failure-memory layer for coding agents: search evidence-rated failure lessons by error text. This page covers its hosted endpoint (https://misakanet.org/mcp).

Is the io.github.Ikalus1988/misakanet MCP server safe to use?

io.github.Ikalus1988/misakanet scores 74 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.Ikalus1988/misakanet MCP server expose?

io.github.Ikalus1988/misakanet exposes 8 tools: misakanet_register, misakanet_search, misakanet_get_lesson, misakanet_submit_intake, misakanet_write_lesson, and 3 more. Their descriptions and schemas cost roughly 4,103 tokens of context every time the server is loaded.

Does the io.github.Ikalus1988/misakanet MCP server require authentication?

No. We connected to io.github.Ikalus1988/misakanet without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.Ikalus1988/misakanet MCP server still maintained?

io.github.Ikalus1988/misakanet is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the io.github.Ikalus1988/misakanet MCP server?

VerifyMCP ran 13 checks on io.github.Ikalus1988/misakanet, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.