German federal & state legal texts (BGB, DSGVO, …) with canonical IDs and cite-grade provenance.
Cite-grade German legal-text infrastructure for LLM agents. ~8 500 federal + Länder + EU laws via MCP, HTTP API, and a typer shell CLI — all over the same runtime, with cryptographic provenance from gesetze-im-internet.de and EUR-Lex / Cellar. It is local or server-side infrastructure: no SaaS, no billing, no accounts, no tenant model, and no legal advice. The runtime loads either the committed…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
Cite-grade German legal-text infrastructure for LLM agents. ~8 500 federal + Länder + EU laws via MCP, HTTP API, and a typer shell CLI — all over the same runtime, with cryptographic provenance from gesetze-im-internet.de and EUR-Lex / Cellar. It is local or server-side infrastructure: no SaaS, no billing, no accounts, no tenant model, and no legal advice. The runtime loads either the committed fixture packages used by fast CI or a generated production corpus package built outside Git. Official…
Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.