_ registry / mcp http-sse · checked 1h ago

gitjog

https://gitjog.remenyfarm.hu

Registry code: 5eaf44b848ee3f93

api record

GitJog: a magyar törvények teljes szövege és teljes változástörténete (4300+ törvény, 1827-től), naponta frissítve.

Nem hiteles jogforrás — idézésnél mondd ki, hogy a hiteles szöveg az njt.jog.gov.hu-n van.

endpoint
https://gitjog.remenyfarm.hu/api/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is gitjog live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is gitjog free to use?
Yes — the hub reached it with no key and no payment.
What tools does gitjog have?
6 tools: kereses, diff, szakasz, search, fetch, valtozasok.
Is gitjog safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 99.7%· all time 99.7%

latency
223ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 295 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
used for
  • search hungarian laws by question or citation
  • get a law section as of a given date
  • list recent amendments to hungarian laws
  • compare two versions of a law
takes → gives
text → text, data
tools
6 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 6 tools
6 never probed 0 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • kereses reads unknown 4h ago

    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ó.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "q"
      ],
      "properties": {
        "q": {
          "type": "string",
          "maxLength": 200,
          "minLength": 1,
          "description": "Kereső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.”"
        },
        "limit": {
          "type": "integer",
          "maximum": 9007199254740991,
          "description": "Találatok száma (alap 10, max 40).",
          "exclusiveMinimum": 0
        },
        "hatalyos": {
          "type": "boolean",
          "description": "Csak hatályos szöveg (alap: true). false: a már nem hatályos jogszabályok szövege is."
        }
      }
    }
    arguments 25 lines
  • diff reads unknown 12h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "slug",
        "tol",
        "ig"
      ],
      "properties": {
        "ig": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "A későbbi időállapot napja (YYYY-MM-DD)."
        },
        "tol": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "A korábbi időállapot napja (YYYY-MM-DD)."
        },
        "slug": {
          "type": "string",
          "maxLength": 200,
          "minLength": 1,
          "description": "A jogszabály slugja, pl. „2013-evi-cxxii-torveny-foldforgalmi” (a `kereses` adja)."
        },
        "horgony": {
          "type": "string",
          "maxLength": 200,
          "description": "Csak ezt a §-t (horgony)."
        }
      }
    }
    arguments 32 lines
  • szakasz reads unknown 12h ago

    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).

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "maxLength": 200,
          "minLength": 1,
          "description": "A jogszabály slugja, pl. „2013-evi-cxxii-torveny-foldforgalmi” (a `kereses` adja)."
        },
        "datum": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "Időállapot napja (YYYY-MM-DD): az ezen a napon hatályos szöveg. Alap: a legutolsó."
        },
        "horgony": {
          "type": "string",
          "maxLength": 200,
          "description": "A § horgonya, pl. „18-sz-elovasarlasi-jog” (a `kereses` vagy a tartalomjegyzék adja)."
        },
        "paragrafus": {
          "type": "string",
          "maxLength": 200,
          "description": "A § száma horgony helyett: „18. §”, „6:272. §”, „18/A. §”."
        }
      }
    }
    arguments 30 lines
  • search reads unknown 4h ago

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

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "minLength": 1
        }
      }
    }
    arguments 13 lines
  • fetch reads unknown 12h ago

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

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "minLength": 1
        }
      }
    }
    arguments 13 lines
  • valtozasok reads unknown 4h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "q": {
          "type": "string",
          "maxLength": 200,
          "description": "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 („föld” → „földek”, de nem „külföld”); a puszta „föld” túl tág (földgáz, földmérés is)."
        },
        "limit": {
          "type": "integer",
          "maximum": 9007199254740991,
          "description": "Tételek száma (alap 20, max 50).",
          "exclusiveMinimum": 0
        },
        "since": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "Hatálybalépés napjától (YYYY-MM-DD)."
        },
        "slugs": {
          "type": "array",
          "items": {
            "type": "string",
            "maxLength": 200
          },
          "maxItems": 50,
          "description": "Csak ezek a jogszabályok."
        },
        "until": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "Hatálybalépés napjáig (YYYY-MM-DD)."
        },
        "felveve_utan": {
          "type": "string",
          "maxLength": 40,
          "description": "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."
        }
      }
    }
    arguments 41 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 5eaf44b848ee3f93.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/5eaf44b848ee3f93/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/5eaf44b848ee3f93/badge.svg)](https://brick.blue/agent/5eaf44b848ee3f93?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.