Skip to main content
Glama
roccoangelella

Dichiarazione-MCP

by roccoangelella
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Dichiarazione-MCP

No user-submitted related servers found.

    Related Servers

    • LawryAI

      HeyLawry
      A
      license
      Not graded
      quality
      B
      maintenance
      A local-first MCP server that connects to legal case-management systems like ActaPort, letting AI agents read and prepare work for lawyer approval by replaying saved browser sessions.
      AGPL 3.0

    • falltax-us-mcp

      sjgant80-hub
      A
      license
      Not graded
      quality
      B
      maintenance
      A sovereign, MIT-licensed MCP server for US tax operations, enabling offline-capable and self-hostable tax workflow management.
      MIT

    • taxbrainai-mcp

      harshil-projects
      A
      license
      Not graded
      quality
      C
      maintenance
      A standalone MCP server for Indian personal income-tax work (ITR-1/2/3/4 + post-filing notices) with 8 deterministic tools, running fully offline with no API keys.
      MIT

    • Chrome Tab Remote

      ai-4-you
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that gives AI agents secure, consent-based access to a single browser tab, supporting read-only snapshots, element interaction with per-action approval, and frozen multi-step plans, all audited.
      MIT

    • Networking MCP

      otnielba
      A
      license
      Not graded
      quality
      D
      maintenance
      Local-first MCP server for research on AI-assisted browsing of a user-owned professional-network account (e.g., LinkedIn), providing read-focused tools such as profile, company, search, and feed reads.
      MIT
    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

    B3.2/5.0

    Scored across 7 tools

    Disambiguation4/5

    Most tools target distinct concerns: reading drafts, reading evidence, validating, mutating, reverting, and preparing review. However, read_declaration_draft and read_normalized_evidence both read bounded session-bound content and could be confused in scope. The naming clearly differentiates them by object type, so ambiguity is low.

    Naming Consistency4/5

    Tools follow a consistent verb_noun pattern (read_, validate_, mutate_, revert_, prepare_). The main deviation is session_status, which uses noun_status instead of a verb_noun form, though it's still readable and predictable alongside the pattern.

    Tool Count4/5

    Seven tools is a reasonable, slightly tight count for a declaration workflow server. Each tool earns its place and there's a clear lifecycle: read, validate, mutate, revert, review. It feels appropriately scoped with room to grow.

    Completeness4/5

    The set covers the core declaration workflow: read draft, validate, mutate, revert mutations, and prepare review. Minor gaps exist—there's no obvious create/get initial draft or final approval/submission tool—but the stated purpose (working with normalized synthetic drafts and evidence) appears largely covered.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources