Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

AIFEC

REMOTE · AIFEC.GMARTOS.ES

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

Available components

72 Trust /100

Last scanned (18 hours ago)

Scores higher than 57% of remote servers

Reachable. Last reached 21 Nov 2026.

Category E-commerce

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability79
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
  • Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 18 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Nov 26 +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.

  • 18 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 17 Nov 26 70

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://aifec.gmartos.es/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=aifec.gmartos.es CN=YE1,O=Let's Encrypt,C=US 12 Nov 2026 10 Feb 2027 ECDSA 256 ECDSA-SHA384 6a49303a0fdec2a9b8313846d28a60be032
SANs: aifec.gmartos.es
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of aifec.gmartos.es. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
es. DS published 4901, 54404 8, 8 Verified
gmartos.es. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://aifec.gmartos.es/mcp Verified 200
http (plaintext) http://aifec.gmartos.es/mcp HTTPS enforced 301 https://aifec.gmartos.es/mcp
MCP tools · 18 exposed · ~3,006 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
cart_add ~221

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.

NameTypeReqDescription
product_idintegeryesThe id of the product, from search_products
qtyinteger–How many units to add
session_idstring–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_idinteger–The id of the variant (colour, size…), from get_product; 0 for a product without variants

No output schema declared.

No examples provided.

cart_update ~113

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

NameTypeReqDescription
keystringyesThe key of the cart line, from cart_view
qtyintegeryesThe new number of units; 0 removes the line
session_idstring–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.

No output schema declared.

No examples provided.

cart_view ~74

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

NameTypeReqDescription
session_idstring–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.

No output schema declared.

No examples provided.

check_availability ~178

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.

NameTypeReqDescription
product_idintegeryesThe id of the product, from search_products
qtyinteger–How many units
session_idstring–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_idinteger–The id of the variant (colour, size…), from get_product; 0 for a product without variants

No output schema declared.

No examples provided.

checkout_link ~78

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

NameTypeReqDescription
session_idstring–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.

No output schema declared.

No examples provided.

checkout_payment_options ~91

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.

NameTypeReqDescription
session_idstring–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.

No output schema declared.

No examples provided.

checkout_place ~201

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.

NameTypeReqDescription
buyer_codestring–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_confirmedbooleanyestrue: the person has seen the total and said yes
confirm_tokenstringyesThe confirm_token of the last checkout_review

No output schema declared.

No examples provided.

checkout_review ~163

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.

NameTypeReqDescription
session_idstring–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.

No output schema declared.

No examples provided.

checkout_set_customer ~672

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.

NameTypeReqDescription
address_idinteger–One of the saved_addresses ids of checkout_status (customers with an account)
citystring–The city or town only. Only if the customer gave it.
companystring–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…
countrystring–ISO 3166-1 alpha-2 code ("ES" for Spain). Only if the customer gave it.
emailstring–The email address, nothing else. Only if the customer gave it.
first_namestring–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_namestring–The surname or surnames, nothing else. Only if the customer gave it.
line1string–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.
line2string–Floor, door or staircase only ("3º A", "2n 1a", "bajo"), if given. Only if the customer gave it.
notestring–A note for the order, only if the customer asked for one
phonestring–The phone number, digits and an optional + prefix. Only if the customer gave it.
postcodestring–The postcode only. Only if the customer gave it.
regionstring–The province or region, only if given. Only if the customer gave it.
session_idstring–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.
textstring–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_idstring–The tax or VAT ID exactly as given (keep a country prefix such as "ES"), without the label. Only if the customer gave it.

No output schema declared.

No examples provided.

checkout_set_payment ~89

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

NameTypeReqDescription
methodstringyesThe id of the payment method, from checkout_payment_options
session_idstring–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.

No output schema declared.

No examples provided.

checkout_set_shipping ~88

Choose the delivery option (carrier_id from checkout_shipping_options).

NameTypeReqDescription
carrier_idintegeryesThe id of the delivery option, from checkout_shipping_options
session_idstring–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.

No output schema declared.

No examples provided.

checkout_shipping_options ~80

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

NameTypeReqDescription
session_idstring–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.

No output schema declared.

No examples provided.

checkout_status ~107

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.

NameTypeReqDescription
session_idstring–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.

No output schema declared.

No examples provided.

get_product ~143

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.

NameTypeReqDescription
idintegeryesThe id of the product, from search_products
session_idstring–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.

No output schema declared.

No examples provided.

list_categories ~90

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.

NameTypeReqDescription
session_idstring–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.

No output schema declared.

No examples provided.

search_products ~264

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).

NameTypeReqDescription
category_idinteger–Only products of this category (see list_categories)
in_stock_onlyboolean–true: only products that can be bought now
limitinteger–How many products to return, from 1 to 8
max_price_centsinteger–Maximum price in cents: 5000 means 50.00
querystring–What to look for: the customer's words or, for a vague need, a product type or synonym of your own that fits
session_idstring–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.

No output schema declared.

No examples provided.

shipping_quote ~190

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.

NameTypeReqDescription
countrystring–ISO 3166-1 alpha-2 code, for example ES
postcodestring–The postcode of the delivery address
product_idinteger–The id of the product, from search_products
qtyinteger–How many units
session_idstring–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_idinteger–The id of the variant (colour, size…), from get_product; 0 for a product without variants

No output schema declared.

No examples provided.

store_info ~164

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.

NameTypeReqDescription
session_idstring–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.
topicstring–What to tell about the shop; all gives everything

No output schema declared.

No examples provided.

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.

remote · aifec.gmartos.es

# add to Claude Code
claude mcp add --transport http es-gmartos-aifec-shop 'https://aifec.gmartos.es/mcp'
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.