Skip to main content
Glama
Naroh091

gijon-avisos-mcp

by Naroh091
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to gijon-avisos-mcp

No user-submitted related servers found.

    Related Servers

    • bilbao-avisos-mcp

      Naroh091
      A
      license
      B
      quality
      C
      maintenance
      Enables AI agents to report incidents to the Bilbao City Council (MeJora Bilbao / Bilbo Hobetuz) by listing categories, looking up streets, reviewing existing reports, and creating new ones — including generating a report directly from a geolocated photo. Drafts are dry-run by default and real submissions require explicit human confirmation.
      12
      AGPL 3.0

    • valencia-avisos-mcp

      Naroh091
      A
      license
      B
      quality
      C
      maintenance
      Enables AI agents to report street incidents to Valencia City Council by listing categories, geocoding streets, checking existing reports, and creating nuevos avisos from text or photos with human-confirmed previews. Supports stdio and HTTP transports, with identity and device registration handled locally.
      11
      AGPL 3.0

    • klaxon

      ali-cabukel
      A
      license
      B
      quality
      C
      maintenance
      Enables incident management through natural language, with tools for searching, retrieving, creating, updating, and commenting on issues, simulating upstream events, creating GitHub issues, and listing side effects.
      10
      MIT

    • Catastro GPS MCP server

      TheHiddenPandaDev
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to look up official cadastral parcels across 31 European country and region codes by reference, coordinates, or free-text Spanish address, returning location, area, land use, and outlines while also estimating solar and agricultural potential, market prices, and investment scores.
      9
      256 npm
      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.4/5.0

    Scored across 7 tools

    Disambiguation4/5

    Identity (get/set), category (list/get/suggest), and creation (aviso/photo) tools are largely distinct. Minor overlap exists between create_aviso and create_aviso_from_photo (both create reports, differentiated only by photo input) and between list_categories and suggest_categories (both surface types, one filtered).

    Naming Consistency5/5

    All seven tools follow a consistent snake_case verb_noun pattern (get_identity, set_identity, list_categories, get_category, suggest_categories, create_aviso, create_aviso_from_photo). No mixing of conventions or vague verbs.

    Tool Count5/5

    Seven tools is well-scoped for a municipal incident-reporting client, with each tool earning its place (identity, category lookup, and two creation paths). No redundancy or filler.

    Completeness3/5

    The surface covers identity, category discovery, and report creation (text and photo), but offers no way to list, get, or track previously submitted avisos, nor to update/withdraw them. This creates a dead end for verifying report status, a notable gap for a reporting domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources