# AIFEC (remote · aifec.gmartos.es)

Demo AI-first shop: search products, fill a cart and prepare the order (test payments).

- Trust score: 72/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `aifec.gmartos.es`: 72/100 (this document), [markdown](https://verifymcp.io/servers/es-gmartos-aifec-shop/aifec.md), [page](https://verifymcp.io/servers/es-gmartos-aifec-shop/aifec)

## Channel facts

- Endpoint: `https://aifec.gmartos.es/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.2`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 79/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 3273 tokens (~163/item across 20 items; 18 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 18 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the AIFEC MCP server?

AIFEC is a hosted endpoint at https://aifec.gmartos.es/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http es-gmartos-aifec-shop 'https://aifec.gmartos.es/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "es-gmartos-aifec-shop": {
      "url": "https://aifec.gmartos.es/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "es-gmartos-aifec-shop": {
      "type": "http",
      "url": "https://aifec.gmartos.es/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.es-gmartos-aifec-shop]
url = "https://aifec.gmartos.es/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "es-gmartos-aifec-shop": {
      "type": "remote",
      "url": "https://aifec.gmartos.es/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add es-gmartos-aifec-shop --url 'https://aifec.gmartos.es/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  es-gmartos-aifec-shop:
    url: "https://aifec.gmartos.es/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "es-gmartos-aifec-shop": {
      "Transport": "http",
      "Url": "https://aifec.gmartos.es/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add es-gmartos-aifec-shop -t streamable-http -u 'https://aifec.gmartos.es/mcp'
```

### Other

```json
{
  "mcpServers": {
    "es-gmartos-aifec-shop": {
      "type": "http",
      "url": "https://aifec.gmartos.es/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 71, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-17 (score 70)

First indexed and scored.

## MCP tools (18)

### `search_products` (~264 tokens)

Search the shop catalogue. Give words (query), a category, a maximum price in cents or only products in stock. Returns up to 8 products (id, name, price_formatted, available, summary, options such as colour or size) and answer_kind: exact (they match), relaxed or related (NOT exact: only the closest, say so), shop (a question about the shop, see shop_answer) or none (nothing matches: say so, never offer unrelated products).

Input parameters:

- `category_id` (integer): Only products of this category (see list_categories)
- `in_stock_only` (boolean): true: only products that can be bought now
- `limit` (integer): How many products to return, from 1 to 8
- `max_price_cents` (integer): Maximum price in cents: 5000 means 50.00
- `query` (string): What to look for: the customer's words or, for a vague need, a product type or synonym of your own that fits
- `session_id` (string): Only if your client does not keep the MCP session (the Mcp-Session-Id header): the session_id that an earlier answer of this server gave you. It keeps the same cart between calls.

### `get_product` (~143 tokens)

Everything the shop says about one product: description in plain text, key facts, the options (colour, size) with their available values, variants with price and availability, delivery time and frequently asked questions. Call it whenever the customer asks about a product ("tell me about it", "what is it", "features") and answer with what it says.

Input parameters:

- `id` (integer, required): The id of the product, from search_products
- `session_id` (string): Only if your client does not keep the MCP session (the Mcp-Session-Id header): the session_id that an earlier answer of this server gave you. It keeps the same cart between calls.

### `list_categories` (~90 tokens)

The product categories of the shop with their sub-categories (what the shop sells), and popular: the categories of the best sellers, first the one that sells most.

Input parameters:

- `session_id` (string): Only if your client does not keep the MCP session (the Mcp-Session-Id header): the session_id that an earlier answer of this server gave you. It keeps the same cart between calls.

### `check_availability` (~178 tokens)

Whether a product (or one of its variants) can be bought in a given quantity right now, and what that quantity costs: unit_price and total (unit price × quantity, calculated by the shop). When the customer asks how much several units cost, call it with that qty and say its total: never multiply yourself.

Input parameters:

- `product_id` (integer, required): The id of the product, from search_products
- `qty` (integer): How many units
- `session_id` (string): Only if your client does not keep the MCP session (the Mcp-Session-Id header): the session_id that an earlier answer of this server gave you. It keeps the same cart between calls.
- `variant_id` (integer): The id of the variant (colour, size…), from get_product; 0 for a product without variants

### `shipping_quote` (~190 tokens)

Delivery options, prices and times to a destination. Give the postcode (and the 2-letter country if it is not the shop's own). Quotes the product given, or the current cart when no product is given.

Input parameters:

- `country` (string): ISO 3166-1 alpha-2 code, for example ES
- `postcode` (string): The postcode of the delivery address
- `product_id` (integer): The id of the product, from search_products
- `qty` (integer): How many units
- `session_id` (string): Only if your client does not keep the MCP session (the Mcp-Session-Id header): the session_id that an earlier answer of this server gave you. It keeps the same cart between calls.
- `variant_id` (integer): The id of the variant (colour, size…), from get_product; 0 for a product without variants

### `store_info` (~164 tokens)

About the shop itself and its policies: what the shop is and sells in its own words (about), returns (the deadline and the text of the returns page, with its link), shipping and terms pages, accepted payment methods, how the invoice reaches the customer (invoices), contact details and opening hours. Call it for any question about the shop that is not about a product. Say you do not know only when this returns nothing for the topic.

Input parameters:

- `session_id` (string): Only if your client does not keep the MCP session (the Mcp-Session-Id header): the session_id that an earlier answer of this server gave you. It keeps the same cart between calls.
- `topic` (string): What to tell about the shop; all gives everything

### `cart_view` (~74 tokens)

The customer's cart: lines, quantities, prices and totals, as the shop calculates them.

Input parameters:

- `session_id` (string): Only if your client does not keep the MCP session (the Mcp-Session-Id header): the session_id that an earlier answer of this server gave you. It keeps the same cart between calls.

### `cart_add` (~221 tokens)

Add units of a product to the customer's cart. The price is always the shop's own; it cannot be given. A product with variants needs its variant_id: without it you get need=options with the choices (the shop shows them as buttons): ask which one the customer wants and call again with that variant_id. If the product is already in the cart it returns already_in_cart and adds nothing (unless the customer asked for more in this message): to change how many there are, use cart_update with the exact number.

Input parameters:

- `product_id` (integer, required): The id of the product, from search_products
- `qty` (integer): How many units to add
- `session_id` (string): Only if your client does not keep the MCP session (the Mcp-Session-Id header): the session_id that an earlier answer of this server gave you. It keeps the same cart between calls.
- `variant_id` (integer): The id of the variant (colour, size…), from get_product; 0 for a product without variants

### `cart_update` (~113 tokens)

Change the quantity of a cart line (the key comes from cart_view). Quantity 0 removes the line.

Input parameters:

- `key` (string, required): The key of the cart line, from cart_view
- `qty` (integer, required): The new number of units; 0 removes the line
- `session_id` (string): Only if your client does not keep the MCP session (the Mcp-Session-Id header): the session_id that an earlier answer of this server gave you. It keeps the same cart between calls.

### `checkout_link` (~78 tokens)

The address of the checkout page with the customer's cart, where they review and pay. Payment always happens there.

Input parameters:

- `session_id` (string): Only if your client does not keep the MCP session (the Mcp-Session-Id header): the session_id that an earlier answer of this server gave you. It keeps the same cart between calls.

### `checkout_status` (~107 tokens)

Where the purchase is: what is still missing (contact, address, shipping, payment, in the order to ask for it), the cart summary and what is already saved. Personal data come masked. Call it before asking the customer anything about their order.

Input parameters:

- `session_id` (string): Only if your client does not keep the MCP session (the Mcp-Session-Id header): the session_id that an earlier answer of this server gave you. It keeps the same cart between calls.

### `checkout_set_customer` (~672 tokens)

Save the customer's details for this order. Pass every detail in its OWN field, already separated: first_name, last_name, email, phone, line1 (street and number), line2 (floor and door), postcode, city, region, country, company and vat_id. Put only the value in each field, never the label or the sentence around it. Use text only as a last resort, when you cannot tell the details apart. It saves what is valid and returns what it understood, what is wrong and what is still missing. Never invent a value: ask for what was not said.

Input parameters:

- `address_id` (integer): One of the saved_addresses ids of checkout_status (customers with an account)
- `city` (string): The city or town only. Only if the customer gave it.
- `company` (string): The company name ONLY when a company buys and needs the invoice in its name ("Invoice to company X", "Factura a nombre de X"); then vat_id is required too. The name of an office, hotel or association…
- `country` (string): ISO 3166-1 alpha-2 code ("ES" for Spain). Only if the customer gave it.
- `email` (string): The email address, nothing else. Only if the customer gave it.
- `first_name` (string): The first name of the person, nothing else. Never a greeting, a yes or a label: "Yes", "Ok", "Hello", "Address" or "Name" are not names. Only if the customer gave it.
- `last_name` (string): The surname or surnames, nothing else. Only if the customer gave it.
- `line1` (string): Street and number only ("Calle Mayor 1", "Carrer de l'Exemple 9"), without the word "address", the floor or the postcode. Only if the customer gave it.
- `line2` (string): Floor, door or staircase only ("3º A", "2n 1a", "bajo"), if given. Only if the customer gave it.
- `note` (string): A note for the order, only if the customer asked for one
- `phone` (string): The phone number, digits and an optional + prefix. Only if the customer gave it.
- `postcode` (string): The postcode only. Only if the customer gave it.
- `region` (string): The province or region, only if given. Only if the customer gave it.
- `session_id` (string): Only if your client does not keep the MCP session (the Mcp-Session-Id header): the session_id that an earlier answer of this server gave you. It keeps the same cart between calls.
- `text` (string): ONLY if you cannot separate the details into the fields: what the customer wrote about themselves, exactly as they wrote it. When you pass any separate field, text is ignored.
- `vat_id` (string): The tax or VAT ID exactly as given (keep a country prefix such as "ES"), without the label. Only if the customer gave it.

### `checkout_shipping_options` (~80 tokens)

The delivery options for the order with their price and delay, and the one selected. Needs the delivery address first.

Input parameters:

- `session_id` (string): Only if your client does not keep the MCP session (the Mcp-Session-Id header): the session_id that an earlier answer of this server gave you. It keeps the same cart between calls.

### `checkout_set_shipping` (~88 tokens)

Choose the delivery option (carrier_id from checkout_shipping_options).

Input parameters:

- `carrier_id` (integer, required): The id of the delivery option, from checkout_shipping_options
- `session_id` (string): Only if your client does not keep the MCP session (the Mcp-Session-Id header): the session_id that an earlier answer of this server gave you. It keeps the same cart between calls.

### `checkout_payment_options` (~91 tokens)

The payment methods offered for the order, with their kind (offline: transfer or cash on delivery; redirect: paid online) and any fee, and the one selected.

Input parameters:

- `session_id` (string): Only if your client does not keep the MCP session (the Mcp-Session-Id header): the session_id that an earlier answer of this server gave you. It keeps the same cart between calls.

### `checkout_set_payment` (~89 tokens)

Choose the payment method (method = the id from checkout_payment_options).

Input parameters:

- `method` (string, required): The id of the payment method, from checkout_payment_options
- `session_id` (string): Only if your client does not keep the MCP session (the Mcp-Session-Id header): the session_id that an earlier answer of this server gave you. It keeps the same cart between calls.

### `checkout_review` (~163 tokens)

The exact order that would be placed: lines, discounts, shipping, taxes, the total (total_cents and total formatted), the delivery address and the payment method, and the confirm_token that checkout_place needs. Read the total from here: never calculate it. If something is missing it says what. When no API key with the scope orders:create is sent, the shop emails a 6-digit verification code to the buyer for security and says so in "confirmation": tell the person, ask for the code and wait for it.

Input parameters:

- `session_id` (string): Only if your client does not keep the MCP session (the Mcp-Session-Id header): the session_id that an earlier answer of this server gave you. It keeps the same cart between calls.

### `checkout_place` (~201 tokens)

Place the order. Needs the confirm_token of the last checkout_review, buyer_confirmed true (you declare that the person has seen the total and said yes) and one of two things: buyer_code, the 6-digit verification code that the shop emails to the buyer when you call checkout_review (ask the person for it and wait: never guess it), or an API key with the scope orders:create, sent as Authorization: Bearer. Without them nothing is placed. If anything changed after the review, the confirm_token is no longer valid: review again. The person pays: the answer says how.

Input parameters:

- `buyer_code` (string): The 6-digit code the shop emailed to the buyer after checkout_review. Not needed with an API key that has the scope orders:create
- `buyer_confirmed` (boolean, required): true: the person has seen the total and said yes
- `confirm_token` (string, required): The confirm_token of the last checkout_review

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/es-gmartos-aifec-shop/aifec#diagnostics

## Score history

- 2026-11-21: 72
- 2026-11-20: 72
- 2026-11-19: 71
- 2026-11-18: 71
- 2026-11-17: 70

## Common questions

### What is the AIFEC MCP server?

AIFEC is an MCP server listed in the public MCP registry as es.gmartos.aifec/shop. Demo AI-first shop: search products, fill a cart and prepare the order (test payments). This page covers its hosted endpoint (https://aifec.gmartos.es/mcp).

### Is the AIFEC MCP server safe to use?

AIFEC scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the AIFEC MCP server expose?

AIFEC exposes 18 tools: search_products, get_product, list_categories, check_availability, shipping_quote, and 13 more. Their descriptions and schemas cost roughly 3,006 tokens of context every time the server is loaded.

### Does the AIFEC MCP server require authentication?

No. We connected to AIFEC without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the AIFEC MCP server still maintained?

AIFEC is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the AIFEC MCP server?

VerifyMCP ran 13 checks on AIFEC, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://aifec.gmartos.es/mcp
- Repository: https://github.com/ecomyseo/aifec
- Website: https://aifec.gmartos.es/
- Changelog RSS feed: https://verifymcp.io/servers/es-gmartos-aifec-shop/aifec.xml
- Changelog JSON feed: https://verifymcp.io/servers/es-gmartos-aifec-shop/aifec/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/es-gmartos-aifec-shop/aifec.json
- HTML version of this page: https://verifymcp.io/servers/es-gmartos-aifec-shop/aifec
