Hokmah
REMOTE · HOKMAH.DEV
AI Agent with Architectural Memory. Impact analysis (free), tests and code from the graph (pro).
Available components
Last scanned (12 hours ago)
Scores higher than 87% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Code Search and Documentation
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 Security80
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1080 tokens (~154/item across 7 items; 7 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 Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
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.
- 5 Nov 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “hokmah_connect_project” rewrote its description, which is the text the model reads security
- Schema quality: 187 → 154 ▲ functional
- New tool “hokmah_compare” functional
- New tool “hokmah_overview” functional
- New tool “hokmah_risky_code” functional
- New tool “hokmah_similar_fixes” functional
- New tool “hokmah_zone_health” functional
- 2 Nov 26 +9
- Stability: fail → pass ▲ security
- 3 Oct 26 75
- Stability: pass → fail ▼ security
- A breaking change shipped without a version bump: still 3.4.2 ▼ security
- Tool “hokmah_connect_mcp” was removed ▼ security
- Tool “hokmah_generate_code” was removed ▼ security
- Tool “hokmah_generate_tests” was removed ▼ security
- Authorization: unverified → partial ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “hokmah_analyze” rewrote its description, which is the text the model reads security
- Tool “hokmah_connect_project” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Tool “hokmah_analyze” changed its title: Analyze Change Impact cosmetic
- Tool “hokmah_connect_project” changed its title: Import Public GitHub Repository cosmetic
- 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
- 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 5 Nov 2026 · Probed https://hokmah.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=hokmah.dev | CN=YE1,O=Let's Encrypt,C=US | 8 Oct 2026 | 6 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 63778f8e2e4bbbe3299a54a041d074c98cf |
| SANs: *.hokmah.dev, hokmah.dev | ||||||
| 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 insecure
Validation of hokmah.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| hokmah.dev. | absent | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://hokmah.dev/mcp | Verified | 200 | |
| http (plaintext) | http://hokmah.dev/mcp | HTTPS enforced | 308 | https://hokmah.dev/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 →
hokmah_analyze Analyze Change Impact ~124
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.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | – | – |
| query | string | yes | – |
| repo_url | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
hokmah_compare Compare Feature Zones ~85
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.
| Name | Type | Req | Description |
|---|---|---|---|
| repo_url | string | yes | – |
| zones | array | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
hokmah_connect_project Import Public GitHub Repository ~137
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.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | – | – |
| repo_url | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
hokmah_overview Repository Health Overview ~71
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.
| Name | Type | Req | Description |
|---|---|---|---|
| repo_url | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
hokmah_risky_code Find Code Missing a Protection ~236
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, used unchecked (R7); plain objects used as dictionaries keyed by request input (R2, prototype pollution); template variables inserted unescaped where another file sanitizes them (R3). Optional `zone` (path prefix or words) and `kind` (R1, R2, R3, R7). 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.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | – |
| repo_url | string | yes | – |
| zone | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
hokmah_similar_fixes Find Where a Past Bug May Still Hide ~120
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
| repo_url | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
hokmah_zone_health Assess a Feature Zone ~151
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.
| Name | Type | Req | Description |
|---|---|---|---|
| repo_url | string | yes | – |
| zone | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Hokmah MCP server?
Hokmah is a hosted endpoint at https://hokmah.dev/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 · hokmah.dev
claude mcp add --transport http davidangularme-hokmah 'https://hokmah.dev/mcp'
What is the Hokmah MCP server?
Hokmah is an MCP server listed in the public MCP registry as io.github.davidangularme/hokmah. AI Agent with Architectural Memory. Impact analysis (free), tests and code from the graph (pro). This page covers its hosted endpoint (https://hokmah.dev/mcp).
Is the Hokmah MCP server safe to use?
Hokmah scores 83 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 Hokmah MCP server expose?
Hokmah exposes 7 tools: hokmah_analyze, hokmah_connect_project, hokmah_zone_health, hokmah_compare, hokmah_similar_fixes, and 2 more. Their descriptions and schemas cost roughly 924 tokens of context every time the server is loaded.
Does the Hokmah MCP server require authentication?
No. We connected to Hokmah without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Hokmah MCP server still maintained?
Hokmah is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.