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.

GitJog — Hungarian legislation

REMOTE · GITJOG.REMENYFARM.HU · SCANNED SEP 25

Full text and amendment history of Hungarian acts: section-level search, point-in-time text, diffs.

+3 this week 75 Trust /100
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 Security80
Transport & Reachability100
Schema Quality & AI Usability61
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1448 tokens (~241/item across 6 items; 6 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 Management30
  • Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 89% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 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
Install

How do I install the GitJog — Hungarian legislation MCP server?

GitJog — Hungarian legislation is a hosted endpoint at https://gitjog.remenyfarm.hu/api/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 · gitjog.remenyfarm.hu

# add to Claude Code
claude mcp add --transport http godavid-gitjog 'https://gitjog.remenyfarm.hu/api/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "godavid-gitjog": {
      "url": "https://gitjog.remenyfarm.hu/api/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "godavid-gitjog": {
      "type": "http",
      "url": "https://gitjog.remenyfarm.hu/api/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.godavid-gitjog]
url = "https://gitjog.remenyfarm.hu/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "godavid-gitjog": {
      "type": "remote",
      "url": "https://gitjog.remenyfarm.hu/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add godavid-gitjog --url 'https://gitjog.remenyfarm.hu/api/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  godavid-gitjog:
    url: "https://gitjog.remenyfarm.hu/api/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "godavid-gitjog": {
      "Transport": "http",
      "Url": "https://gitjog.remenyfarm.hu/api/mcp"
    }
  }
}
# add to Vellum
assistant mcp add godavid-gitjog -t streamable-http -u 'https://gitjog.remenyfarm.hu/api/mcp'
// mcp.json
{
  "mcpServers": {
    "godavid-gitjog": {
      "type": "http",
      "url": "https://gitjog.remenyfarm.hu/api/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 25 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 23 Sept 26 +1

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

  • 21 Sept 26 +1

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

  • 18 Sept 26 +1

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

  • 17 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 16 Sept 26 71

    First indexed and scored.

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 25 Sept 2026 · Probed https://gitjog.remenyfarm.hu/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=gitjog.remenyfarm.hu CN=YR1,O=Let's Encrypt,C=US 16 Sept 2026 15 Dec 2026 RSA 2048 SHA256-RSA 69e1c45fba70c875786edeac81e89e84e8a
SANs: gitjog.remenyfarm.hu
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of gitjog.remenyfarm.hu. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
hu. present 46162 8 Verified
remenyfarm.hu. 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=63072000

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://gitjog.remenyfarm.hu/api/mcp Verified 200
http (plaintext) http://gitjog.remenyfarm.hu/api/mcp HTTPS enforced 308 https://gitjog.remenyfarm.hu/api/mcp
MCP tools · 6 exposed · ~1,169 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
diff ~178

Egy jogszabály két időállapotának összevetése: csak az eltérő §-ok, régi és új szöveggel, soronkénti blokkokkal. Az időállapotok napjait a `szakasz` (§ nélkül) vagy a `valtozasok` adja.

NameTypeReqDescription
horgonystring–Csak ezt a §-t (horgony).
igstringyesA későbbi időállapot napja (YYYY-MM-DD).
slugstringyesA jogszabály slugja, pl. „2013-evi-cxxii-torveny-foldforgalmi” (a `kereses` adja).
tolstringyesA korábbi időállapot napja (YYYY-MM-DD).

No output schema declared.

No examples provided.

fetch ~38

Egy `search`-találat teljes szövege az id („slug#horgony”) alapján.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

kereses ~223

Melyik § szabályozza X-et? Teljes szövegű keresés magyar szótövezéssel, vagy hivatkozás feloldása („Fftv. 18. §”, „2013. évi CXXII. törvény”). A találat a § teljes szövegét hozza (4000 karakterig) és a § URL-jét — egy körben citálható.

NameTypeReqDescription
hatalyosboolean–Csak hatályos szöveg (alap: true). false: a már nem hatályos jogszabályok szövege is.
limitinteger–Találatok száma (alap 10, max 40).
qstringyesKeresőkifejezés vagy hivatkozás: „termőföld elővásárlási jog”, „Ptk. 6:272. §”, „2013. évi CXXII. törvény 18. §”, „Fftv.”

No output schema declared.

No examples provided.

search ~37

Keresés a magyar törvényekben; az eredmény id-jét a `fetch` várja.

NameTypeReqDescription
querystringyes–

No output schema declared.

No examples provided.

szakasz ~238

Egy jogszabály egy §-a (horgony vagy §-szám szerint), opcionálisan egy adott napon hatályos szöveggel. § nélkül a jogszabály metaadatát, időállapot-listáját és tartalomjegyzékét adja (nem a teljes szöveget).

NameTypeReqDescription
datumstring–Időállapot napja (YYYY-MM-DD): az ezen a napon hatályos szöveg. Alap: a legutolsó.
horgonystring–A § horgonya, pl. „18-sz-elovasarlasi-jog” (a `kereses` vagy a tartalomjegyzék adja).
paragrafusstring–A § száma horgony helyett: „18. §”, „6:272. §”, „18/A. §”.
slugstringyesA jogszabály slugja, pl. „2013-evi-cxxii-torveny-foldforgalmi” (a `kereses` adja).

No output schema declared.

No examples provided.

valtozasok ~455

Hatályba lépett módosítások listája az érintett §-ok régi/új szövegével — egy hívás elég egy értesítéshez. Figyeléshez: add meg a `felveve_utan` cursort (első hívásnál egy időbélyeg, utána a válasz `kovetkezo_felveve_utan` mezője) és szűrj `q`-val (címbeli szókezdet, pl. „termőföld|földek forgalm|Földalap”) vagy `slugs`-szal. Történeti kérdésre (`mi változott a Btk.-ban 2024-ben?`) a `since`/`until`/`slugs` szűrők valók.

NameTypeReqDescription
felveve_utanstring–Cursor: ISO-8601 időbélyeg; csak az ezután a repóba került időállapotok. A válasz `kovetkezo_felveve_utan` mezőjét add vissza a következő hívásban.
limitinteger–Tételek száma (alap 20, max 50).
qstring–Jogszabálycímre/rövidítésre illesztett szókezdet (kisbetű- és ékezet-független), „|”-vel több alternatíva, többszavas tag is lehet: „termőföld|földek forgalm|Földalap”. A tag szó elején illeszkedik (…
sincestring–Hatálybalépés napjától (YYYY-MM-DD).
slugsarray–Csak ezek a jogszabályok.
untilstring–Hatálybalépés napjáig (YYYY-MM-DD).

No output schema declared.

No examples provided.

Common questions

What is the GitJog — Hungarian legislation MCP server?

GitJog — Hungarian legislation is an MCP server listed in the public MCP registry as io.github.godavid/gitjog. Full text and amendment history of Hungarian acts: section-level search, point-in-time text, diffs. This page covers its hosted endpoint (https://gitjog.remenyfarm.hu/api/mcp).

Is the GitJog — Hungarian legislation MCP server safe to use?

GitJog — Hungarian legislation scores 75 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 GitJog — Hungarian legislation MCP server expose?

GitJog — Hungarian legislation exposes 6 tools: kereses, szakasz, valtozasok, diff, search, fetch. Their descriptions and schemas cost roughly 1,169 tokens of context every time the server is loaded.

Does the GitJog — Hungarian legislation MCP server require authentication?

No. We connected to GitJog — Hungarian legislation without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the GitJog — Hungarian legislation MCP server still maintained?

GitJog — Hungarian legislation is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.