General Tools

aynexa.es

Provides general-purpose tools through the Model Context Protocol.

1 endpoint4 known toolsFirst detected September 19, 2026Last detected September 19, 2026

ENDPOINT 1

https://aynexa.es/api/mcp

No auth detected

MCP server metadata

Name: aynexa-mcp
Version: 1.0.0

Capabilities

tools.listChanged

Known tools 4

listar_servicios

Los dos servicios de AyneXA (consultoría de IA para pymes): qué es la foto inicial con su precio y plazo, qué ejecución viene después con sus precios, y dónde empezar.

Inferred read-only

detalle_servicio

Ficha completa de un servicio de AyneXA en markdown: qué incluye, para quién es, proceso y precios.

Inferred read-only

ultimos_posts

Últimos artículos publicados en el blog de AyneXA (IA y automatización para pymes, en lenguaje de negocio).

Inferred read-only

info_contacto

Cómo contactar con AyneXA y qué esperar del proceso comercial.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.aynexa-mcp]
url = "https://aynexa.es/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "aynexa-mcp": {
      "type": "http",
      "url": "https://aynexa.es/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: aynexa-mcp
Remote MCP URL: https://aynexa.es/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "aynexa-mcp": {
      "url": "https://aynexa.es/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "aynexa-mcp": {
      "type": "http",
      "url": "https://aynexa.es/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "aynexa-mcp",
  "transport": "streamable-http",
  "url": "https://aynexa.es/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.