Skip to content

Hokmah MCP server

io.github.davidangularme/hokmahdavidangularmestreamable-httpv1.0.0Scanned

AI Agent with Architectural Memory. Impact analysis (free), tests and code from the graph (pro).

8 tools: 4 change things and 4 only read.

Tools: 0 delete, 0 irreversible, 4 write, 4 read.
  • Reads private data · 4
  • Reads text others write · 8
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

4 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Hokmah MCP server can do

The Hokmah MCP server is published by the GitHub account davidangularme. It has 8 tools. It can create or change data (4 tools: hokmah_connect_project, hokmah_zone_health, hokmah_overview and hokmah_seams), but cannot delete data. 4 tools only read.

4 tools read private data (hokmah_analyze, hokmah_compare, hokmah_similar_fixes and 1 more); 8 tools bring in text other people can write (hokmah_analyze, hokmah_connect_project, hokmah_zone_health and 5 more).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 19, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

8 tools

Changes things 4Claude Code: ask
  • hokmah_connect_projectImports a public GitHub repository so it can be analyzed: indexes its source files (.py .js .ts .jsx .tsx .vue .mjs .mts .rs .go .java) and its latest commits (up to 500) from the …Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "import": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Imports a public GitHub repository so it can be analyzed: indexes its source files (.py .js .ts .jsx .tsx .vue .mjs .mts .rs .go .java) and its latest commits (up to 500) from the default branch into a dependency and change-history graph. `repo_url` is https://github.com/<owner>/<repository>; `branch` is accepted for compatibility. A repository already imported is not imported again. Returns the project id and the number of commits and files ingested.

    Annotations the server declares

    • title: Import Public GitHub Repository
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • hokmah_overviewOverview of an imported repository: the most fragile areas (fixes per feature over 12 months), the fastest growing and the new ones, the busiest, the largest files, the most co-cha…Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Overview of an imported repository: the most fragile areas (fixes per feature over 12 months), the fastest growing and the new ones, the busiest, the largest files, the most co-changed files, and how many internal imports could be resolved.

    Annotations the server declares

    • title: Repository Health Overview
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • hokmah_seamsArchitecture seams of an imported repository: a DISTINCT axis from risk — not "where is the code fragile?" but "where does the code fight its own structure?".Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Architecture seams of an imported repository: a DISTINCT axis from risk — not "where is the code fragile?" but "where does the code fight its own structure?". A seam is a source of truth split across module boundaries: files in different packages that keep being edited together over the history (e.g. the same list enumerated in two packages). Read from the co-change history alone, scored by near-inseparability (jaccard) with a hub penalty, so wanted shared contracts (api-types/dto/schema...) are listed apart, never counted as debt. Each seam carries its evidence (shared identifiers, co-commits, span) and a confidence; the tool proposes, it does not decide — a seam is not a bug and never appears in the risk axis. `scope` = actionable (default) | all | expected; `min_jaccard` filters weaker seams; `zone` (path prefix or words) narrows to seams touching that zone. Backed by a retrospective bench (backtest_coupling): on the reference repo a flagged seam predicts future co-change with a lift of several times over a random previously-coupled pair.

    Annotations the server declares

    • title: Architecture Seams
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • hokmah_zone_healthSays how well a part of an imported repository is doing and what to do about it.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Says how well a part of an imported repository is doing and what to do about it. `zone` is a path prefix (packages/cli/src/webhooks) or a few words ("MFA recovery codes"). Returns, from the last 12 months of history and the current code: a verdict (stable, active, growing, maintenance, fragile), fixes per feature and per 1000 lines, the recurring fix themes specific to the zone, giant files and functions, files often changed without tests, coupled areas, parallel implementations, and recommendations with the numbers behind each one. No language model is involved.

    Annotations the server declares

    • title: Assess a Feature Zone
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 4Show 4 read-only tools
  • hokmah_analyzeEstimates the impact of a described code change on an imported public GitHub repository.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "hokmah_analyze" says "analyze": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "repository": it reads repositories.
    • private-dataThe input names a repo (input.repo_url), and the tool reads: it reads repositories.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Estimates the impact of a described code change on an imported public GitHub repository. `repo_url` is https://github.com/<owner>/<repository> and `query` describes the change in plain language; `branch` is accepted for compatibility, the analysis uses the history imported from the default branch. Returns a risk assessment with the files, symbols and modules likely to be affected and related commits, computed from the repository graph without a language model.

    Annotations the server declares

    • title: Analyze Change Impact
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • hokmah_compareRanks 2 to 8 zones of an imported repository from the one that works worst to the one that works best, with the reasons: fixes per feature, fixes per 1000 lines and tests, over the…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "hokmah_compare" says "compare": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "repository": it reads repositories.
    • private-dataThe input names a repo (input.repo_url), and the tool reads: it reads repositories.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Ranks 2 to 8 zones of an imported repository from the one that works worst to the one that works best, with the reasons: fixes per feature, fixes per 1000 lines and tests, over the last 12 months. Each zone is a path prefix or a few words.

    Annotations the server declares

    • title: Compare Feature Zones
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • hokmah_risky_codeLists current code of an imported repository that lacks a protection the project's own fixes keep adding, learned from the diffs of its past fixes: unguarded access to structures f…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The description's first verb is "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "repository": it reads repositories.
    • private-dataThe input names a repo (input.repo_url), and the tool reads: it reads repositories.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Lists current code of an imported repository that lacks a protection the project's own fixes keep adding, learned from the diffs of its past fixes: unguarded access to structures fixes had to guard, including an entry checked to exist but read at [0] without checking it has an element, or passed to a function that dereferences it (R1); results of functions that fixes had to null-check, called the way the fixes checked them and declared nullable, used unchecked (R7); plain objects used as dictionaries keyed by request input and written through the looked-up value, obj[k].x = v (R2, prototype pollution; a one-level write is only a hardening note); template variables inserted unescaped where another file sanitizes them (R3). Optional `zone` (path prefix or words) and `kind` (R1, R2, R3, R7). kind="UI" lists the interface instead: translation keys missing from the base locale or called without the values their text needs (U1), screens that await a request on opening without handling its failure (U4), and, not validated on history, accessibility notes (U5). Each site says why it was flagged; `measured_on_history` gives, per kind, how often such sites turned out to need a fix when the detectors were run on the code of a year earlier. Candidates are not confirmed bugs.

    Annotations the server declares

    • title: Find Code Missing a Protection
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • hokmah_similar_fixesFinds past fixes of a kind of bug ("null run data guard", "prototype pollution", "race condition on resume") in an imported repository, and the current files where the same defect …Reads private dataReads text others writeNo findings

    Why it is in this group

    • The description's first verb is "find": a word for reading.

    What it can reach

    • private-dataThe input names a repo (input.repo_url), and the tool reads: it reads repositories.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Finds past fixes of a kind of bug ("null run data guard", "prototype pollution", "race condition on resume") in an imported repository, and the current files where the same defect may still exist: files of the same kind next to the fixed ones, files that usually change with them but were left out, and files that contain the identifiers the fix changed. Read each candidate with the fix in mind; a candidate is not a confirmed bug.

    Annotations the server declares

    • title: Find Where a Past Bug May Still Hide
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data4
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write8
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:03 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
4
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://hokmah.dev/mcp: tools/list returned 8 tools to an anonymous client, including hokmah_connect_project (write), hokmah_zone_health (write), hokmah_overview (write), hokmah_seams (write)

    What this check looks for

Posture changes

  1. Nov 13, 2026
    • Tools that change things, listed without credentials: 3 to 4
  2. Nov 6, 2026
    • Tools that change things, listed without credentials: 1 to 3

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 added.+1 addedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 3 -> 4.View diff
    • Tools that change things, listed without credentials: 3 to 4
  3. PostureRemote posture changed. Tools that change things, listed without credentials: 1 -> 3.View diff
    • Tools that change things, listed without credentials: 1 to 3
  4. Tools5 added, 1 changed.+5 added~1 changedView diff

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http hokmah https://hokmah.dev/mcp
claude mcp add --transport http hokmah https://hokmah.dev/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__hokmah__hokmah_analyze",
      "mcp__hokmah__hokmah_compare",
      "mcp__hokmah__hokmah_similar_fixes",
      "mcp__hokmah__hokmah_risky_code"
    ],
    "ask": [
      "mcp__hokmah__hokmah_connect_project",
      "mcp__hokmah__hokmah_zone_health",
      "mcp__hokmah__hokmah_overview",
      "mcp__hokmah__hokmah_seams"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as hokmah. Review it before you use it.

Capability tags behind 8 rules
  • mcp__hokmah__hokmah_analyze private-data, untrusted-input
  • mcp__hokmah__hokmah_connect_project untrusted-input
  • mcp__hokmah__hokmah_zone_health untrusted-input
  • mcp__hokmah__hokmah_compare private-data, untrusted-input
  • mcp__hokmah__hokmah_similar_fixes private-data, untrusted-input
  • mcp__hokmah__hokmah_risky_code private-data, untrusted-input
  • mcp__hokmah__hokmah_overview untrusted-input
  • mcp__hokmah__hokmah_seams untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.davidangularme/hokmah/verify?hash=e97b730d24bf8e4bfcc2c5d14bb778fc85bfdd0ca5f2c5695aa77b0453218d2e" | jq -e '.changed == false'

Pinned hash e97b730d24bf, from Nov 19, 2026, 13:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.davidangularme/hokmah/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.davidangularme/hokmah
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.davidangularme/hokmah.svg)](https://radar.anlyon.com/servers/io.github.davidangularme/hokmah)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:31 UTC.

Hokmah MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Hokmah MCP server safe?

No scan can promise that. What its definitions show: 8 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Hokmah MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Hokmah MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Hokmah MCP server have?

8 tools: 4 write, 4 read. hokmah_connect_project, hokmah_zone_health, hokmah_overview, hokmah_seams, hokmah_analyze, hokmah_compare, hokmah_similar_fixes and hokmah_risky_code.

Does the Hokmah MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Hokmah MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Hokmah MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 19, 2026. Every change is on this page and in its Atom feed.