Skip to main content
Glama
Sign In
Fontes

Fontes

by ykarapazar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Fontes

No user-submitted related servers found.

    Related Servers

    • Law7 MCP

      mikhashev
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides AI assistants with up-to-date legal documents from official sources, enabling accurate legal information retrieval and analysis.
      21
      AGPL 3.0

    • Open Legal Compliance MCP

      TCoder920
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI assistants to search and analyze legal documents from multiple jurisdictions including US federal and state law, case law, EU regulations, UK legislation, Canadian law, Congress bills, SEC filings, and FDA data through free government APIs.
      6
      MIT

    • 갈피 법령조회 MCP

      uscaidev
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to search and retrieve Korean laws, regulations, administrative rules, legal interpretations, and precedents via official APIs for legal review workflows.
      1
      MIT

    • open-rakiduam-juris

      danoriveravk-wq
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents and legal users to search Chilean jurisprudence in real time across PJUD, the Constitutional Tribunal, and the Comptroller General, retrieve full official rulings, and verify citations against source texts with SHA-256 auditability.
      5
      Creative Commons Attribution Non Commercial Share Alike 4.0 International
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.4/5.0

    Scored across 8 tools

    Disambiguation4/5

    Tools split cleanly along resource (caselaw vs legislation) and action (search vs fetch vs structure), and report_bug is unmistakably separate. The only soft overlap is get_legislation_text versus get_legislation_toc + get_legislation_provision, since both return statutory text; the descriptions do steer agents (full code vs single provision) but an agent could still pick the wrong one for a large code.

    Naming Consistency4/5

    Consistent snake_case verb_noun pattern throughout (search_caselaw, get_decision, get_legislation_toc, list_jurisdictions, report_bug). The one asymmetry is that caselaw retrieval is get_decision rather than get_caselaw_decision, breaking the parallel with the get_legislation_* family, though it remains readable.

    Tool Count5/5

    Eight tools is well within the ideal range and each earns its place: discovery, two search tools, three legislation-retrieval granularities, and a scoped bug reporter. Nothing appears redundant or missing at the count level.

    Completeness4/5

    The surface covers the full research loop: list jurisdictions, search caselaw/legislation, then fetch decisions, tables of contents, provisions, or whole texts, with paging on long documents. Gaps are minor—no cross-jurisdiction search in a single call, no body-text search within a law (the TOC keyword explicitly does not search text), and no citator/related-case traversal.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources