Skip to main content
Glama
Sign In
Naroh091

valencia-avisos-mcp

by Naroh091
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to valencia-avisos-mcp

No user-submitted related servers found.

    Related Servers

    • chiclana-avisos-mcp

      dfernandezdaw
      A
      license
      A
      quality
      B
      maintenance
      Enables an AI agent to file municipal incidents and street-damage reports with a GECOR-based town council, attaching a photo (extracting GPS from EXIF when present), previewing the exact summary for explicit human confirmation before anything is sent, and listing previously registered reports and their status. It also supports choosing official categories, resolving nearby streets or callejero references, and switching between GECOR municipalities.
      7
      MIT

    • 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
      8 npm
      1
      AGPL 3.0

    • gijon-avisos-mcp

      Naroh091
      A
      license
      B
      quality
      C
      maintenance
      Enables an AI agent to list the incident categories of Gijón's municipal reporting system and file real service notices on a citizen's behalf, including generating one from a photo by reading its EXIF GPS and suggesting the matching category. Report creation is dry-run by default and only sends after explicit human confirmation, using a saved email as the contact identity and no credentials.
      7
      10 npm
      AGPL 3.0
    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 11 tools

    Disambiguation4/5

    Cada herramienta tiene un propósito distinto: identidad, registro, categorías, geocodificación, consulta y creación. La única superposición es create_aviso vs create_aviso_from_photo, pero las descripciones aclaran que la segunda es para fotos y con fases; list/get/suggest de categorías se distinguen bien.

    Naming Consistency3/5

    Mayoría sigue verbo_sustantivo (get_identity, set_identity, register_device, list_categories, create_aviso) pero hay excepciones en español sin verbo (actuaciones, my_avisos) y geocode es solo verbo. Mezcla de idiomas y convenciones, aunque legible.

    Tool Count5/5

    11 herramientas es un número adecuado para cubrir identidad, dispositivo, categorías, geocodificación, consulta y creación de avisos. Cada una aporta una operación necesaria, sin redundancia excesiva.

    Completeness3/5

    Cubre el ciclo de creación y consulta (listar avisos propios, crear desde texto o foto) pero faltan operaciones de actualización/edición, cancelación/borrado y obtención de un aviso concreto. Es una brecha notable para la gestión completa de avisos.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources