What did Hlido score agentmako?

agentmako scored 74/100 (STEADY) in Hlido's independent, hands-on review.

How much does agentmako cost?

Hlido recorded the pricing model as: Open source. Derived from evidence Hlido holds, not vendor-supplied; verify current prices on the vendor's pricing page.

Does any vendor pay Hlido for placement?

No. Hlido takes no money from the agents it rates — scoring weights stay private and the evidence behind every verdict is public.

agentmako

Name: agentmako review
Item: agentmako
Rating: 74
Author: Hlido Editor

Coding · tested 2026-08-25 · re-test due 2026-11-23 · by the Hlido desk, not the vendor

In short: A local-first MCP server that gives coding agents a live, queryable map of your repo — a broad typed-tool surface and a durable 'findings' layer, from a small but Apache-licensed project.

5 PASS · 0 FAIL of 5 public-surface claims

Visit agentmako → scorecard.json

Quick answer

agentmako scores 74/100 (STEADY) on Hlido’s independent, hands-on test (reviewed 2026-08-25). STEADY (74), lower-middle, because agentmako is a genuinely agent-native, local-first, Apache-licensed MCP server with a broad typed-tool surface and a thoughtful durable-findings layer (Reef), including rare multi-tenan Pricing: Open source (free entry point documented).

Hlido Editor · 2026-08-25

agentmako is a local-first MCP server that keeps a project's code, routes, schema, diagnostics, rules, findings and freshness state queryable for Claude Code, Codex CLI, Cursor, Cline and other MCP clients. Its distinctive idea is the Reef engine — not just an index, but a durable fact-and-finding layer that remembers what changed, what failed, what was reviewed, and whether a piece of evidence is fresh enough for an agent to trust, with a background daemon that watches edits and refreshes the map. The tool surface is unusually broad for a young project: two dozen typed tools spanning context packets, AST pattern search, route tracing, import-impact analysis, database schema and RLS inspection, a tenant-leak audit, git pre-commit checks, and project-convention extraction. Several of those (RLS inspection, tenant-leak audit) point at a genuinely useful multi-tenant-security angle most codebase tools ignore. The honesty markers are good — 'local-first, no hosted service', 'node >= 20', 'apache-2.0', typed tools — so there is no cloud dependency to trust and the license is permissive. What holds it to the lower-middle of STEADY is maturity and proof: 51 GitHub stars, no published benchmarks or independent evidence for the Reef 'freshness' claims, and a large tool surface whose reliability across real repos the public page asserts rather than demonstrates. It is a promising, well-scoped local server; it is early, and it is honest about being early.

Why STEADY

STEADY (74), lower-middle, because agentmako is a genuinely agent-native, local-first, Apache-licensed MCP server with a broad typed-tool surface and a thoughtful durable-findings layer (Reef), including rare multi-tenant-security tooling. It sits low in the band because it is early (51 stars), publishes no benchmarks or independent evidence for its freshness/durability claims, and its broad tool surface is asserted rather than demonstrated reliable across real projects.

Public-surface checklist

PASS Homepage loads (required)
PASS Primary value prop (required) — Give coding agents a live map of your repo — local-first MCP server
PASS Cta present (required) — npm install -g agentmako / Read the docs
PASS Pricing or access — Free, Apache-2.0, local-first with no hosted service; installed via npm
PASS Evidence or demo — Documented ~two-dozen typed tools; connect/index example; docs, blog and FAQ present

What we saw

4 screenshots captured by the Hlido engine during the reviewed run (run-19aa337213afcb8c-agentmako-drhalto-com). Our own captures — not vendor marketing material.

agentmako — run screenshot 1 (home.png) — home.png

agentmako — run screenshot 2 (page_.png) — page_.png

agentmako — run screenshot 3 (page_docs_.png) — page_docs_.png

agentmako — run screenshot 4 (page_blog_.png) — page_blog_.png

What it does well

Local-first with no hosted service — code and queries stay on your machine
Reef engine adds a durable fact-and-finding layer that survives across sessions, not just a static index
Broad typed-tool surface (~two dozen) covering context, AST search, route tracing, import impact and more
Rare multi-tenant-security tooling: RLS inspection and a tenant-leak audit
Background daemon watches edits and tracks evidence freshness so the agent knows what to trust
Apache-2.0 licensed and node >= 20 — permissive and low-dependency
Works across Claude Code, Codex CLI, Cursor and Cline

What it fails at

Early-stage traction — around 51 GitHub stars at review
No published benchmarks or independent evidence for the Reef freshness/durability claims
A large tool surface whose per-tool reliability across real repos is asserted, not demonstrated
Single-maintainer-scale project with no continuity or support signal published
No pricing/support model because it is a free local tool — fine, but no commercial backing either

Best for

Developers who want a local-first, no-cloud MCP map of their repo for a coding agent
Multi-tenant SaaS teams who value the RLS-inspection and tenant-leak-audit tools
Users who prefer an Apache-licensed tool they can run and inspect entirely locally

Not recommended for

Teams needing a supported, SLA-backed product with a continuity guarantee
Buyers who require published benchmarks before adopting a repo-analysis tool
Anyone wanting a hosted, zero-setup service rather than a local daemon

Pricing & access

ModelOpen source
Free entry pointYes — a free tier or open-source edition is documented
Pricing findable on the public surfacePASS Free, Apache-2.0, local-first with no hosted service; installed via npm (tested 2026-08-25)

Derived from Hlido-held evidence only (engine checklist + editorial text); quotes are verbatim from the scorecard; not vendor-supplied; re-derived daily. Verify current prices on the vendor's pricing page. Last verified 2026-08-25.

Compared to

Serena durable-findings-layer
Serena is a more established semantic code-navigation MCP toolkit; agentmako adds a durable findings layer (Reef) and multi-tenant-security tools but is earlier and less proven. Serena for maturity, agentmako for its findings-persistence idea and security-focused tools.
Neo4j MCP Integrations local-repo-map
Neo4j's MCP server exposes a graph database you model; agentmako is a purpose-built local repo map with typed code tools. Neo4j's for general graph data, agentmako for out-of-the-box, local codebase context.

Agent relevance

CLI MCP Behavioral-testable

Agentic-Commerce Readiness 67/100 · INTEGRABLE

Independent readiness for agent delegation & transaction. How it’s scored · check live

A local-first MCP server. An agent connects agentmako to a project ('agentmako connect .') and calls typed tools — context_packet, ast_find_pattern, route_trace, imports_impact, db_rls, tenant_leak_audit, git_precommit_check and more — to get structured repo context and durable findings. Works with Claude Code, Codex CLI, Cursor and Cline. Runs entirely locally with no API key.

Agent-friendly score: 8/10

Evidence

Local-first MCP server keeping code, routes, schema, diagnostics, rules and findings queryable for coding agents — source (2026-08-25) verified
Reef engine provides a durable fact-and-finding layer with background freshness tracking — source (2026-08-25) verified
Apache-2.0 licensed, node >= 20, no hosted service, typed tools including RLS and tenant-leak audit — source (2026-08-25) verified
Early-stage traction of approximately 51 GitHub stars — source (2026-08-25) verified

scorecard.json · transparency passport · registry · methodology

More: compare agents · best of · developer tools · incident registry

Verdict by Hlido Editor, our automated editorial system · Method: public-surface-tier-1+editorial-narrative-v2 · Methodology version 2026.05 · Next review due 2026-11-23

How this page was produced. The scores, claim verdicts and evidence come from automated hands-on testing of the product’s public surface. The written analysis is drafted by an AI system, and pages publish without a person reviewing each one. Hlido publishes this record and answers for it — tell us if anything here is wrong and we will correct it.

Embed this trust badge

Live, always-current independent score — free to embed on your site or README. No vendor pays for placement.

Markdown

[![Hlido trust score](https://hlido.eu/badge/drhalto-agentmako.svg)](https://hlido.eu/check/?agent=drhalto-agentmako)

HTML

<a href="https://hlido.eu/check/?agent=drhalto-agentmako"><img src="https://hlido.eu/badge/drhalto-agentmako.svg" alt="Hlido trust score"></a>