Neoavis
REMOTE · NEOAVIS.COM
Can an AI agent buy on this French store? 500 stores tested: score, guest checkout, UCP. Free.
Available components
Last scanned (11 hours ago)
Scores higher than 69% of remote servers
Reachable. Last reached 5 Nov 2026.
Category E-commerce
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 Security80
- 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
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1550 tokens (~310/item across 5 items; 5 tools + 0 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 Management40
- Stability observed for 12 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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 →
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +4
- The server rewrote its instructions, which are the text every model session reads security
- Tool “classement_secteur” rewrote its description, which is the text the model reads security
- Tool “comparer_marchands” rewrote its description, which is the text the model reads security
- Tool “rechercher_marchand” rewrote its description, which is the text the model reads security
- Tool “consulter_marchand” rewrote its description, which is the text the model reads security
- Tool “trouver_marchands” rewrote its description, which is the text the model reads security
- Schema quality: 136 → 310 ▼ functional
- Schema quality: 136 → 170 ▼ functional
- Tool coverage: 69% → 100% ▲ functional
- MCP protocol: fail → pass ▲ functional
- Schema quality: good → excellent functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.2.0 → 1.3.0 functional
- Server version: 1.1.0 → 1.2.0 functional
- “trouver_marchands” added an optional parameter “limite” cosmetic
- “classement_secteur” reworded the description of “langue” cosmetic
- “classement_secteur” reworded the description of “secteur” cosmetic
- “comparer_marchands” reworded the description of “domaines” cosmetic
- “comparer_marchands” reworded the description of “langue” cosmetic
- “consulter_marchand” reworded the description of “domaine” cosmetic
- “consulter_marchand” reworded the description of “langue” cosmetic
- “rechercher_marchand” reworded the description of “langue” cosmetic
- “rechercher_marchand” reworded the description of “requete” cosmetic
- “trouver_marchands” reworded the description of “frais_livraison” cosmetic
- “trouver_marchands” reworded the description of “langue” cosmetic
- “trouver_marchands” reworded the description of “note_min” cosmetic
- “trouver_marchands” reworded the description of “prix_livre” cosmetic
- “trouver_marchands” reworded the description of “retours” cosmetic
- “trouver_marchands” reworded the description of “sans_compte” cosmetic
- “trouver_marchands” reworded the description of “secteur” cosmetic
- “trouver_marchands” reworded the description of “ucp” cosmetic
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +3
- HSTS header: fail → pass ▲ security
- 27 Oct 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.
- 26 Oct 26 0
- Tool “consulter_marchand” rewrote its description, which is the text the model reads security
- 25 Oct 26 +1
- Tool “consulter_marchand” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Tool coverage: 50% → 69% ▲ functional
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.0 → 1.1.0 functional
- New tool “comparer_marchands” functional
- New tool “trouver_marchands” functional
- 24 Oct 26 66
First indexed and scored.
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 5 Nov 2026 · Probed https://neoavis.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.neoavis.com | CN=Amazon RSA 2048 S22,O=Amazon,C=US | 22 Oct 2026 | 8 May 2027 | RSA 2048 | SHA256-RSA | 44cbeefb53ec94e3e2c26c144f12d53c |
| SANs: *.neoavis.com, neoavis.com | ||||||
| CN=Amazon RSA 2048 S22,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 8 Jul 2026 | 7 Jul 2029 | RSA 2048 | SHA256-RSA | e2cce9b8b5621211bdeb7b288f5a11e2472d630 |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of neoavis.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| neoavis.com. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| content-security-policy | frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://neoavis.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://neoavis.com/api/mcp | HTTPS enforced | 301 | https://neoavis.com/api/mcp |
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 →
classement_secteur Classement d'un secteur ~230
Ranking of ALL tested French online stores in one sector, best score first. Use it when the user wants the best stores of a sector as a whole (for example the best beauty stores for an AI agent). To filter by proven facts such as guest checkout, use trouver_marchands; for the details of one store, consulter_marchand. Returns: secteur and marchands, a list of every ranked store (30 to 70 per sector) with rang, ex_aequo (equal scores share a rank, then alphabetical order), domaine, nom, note out of 100, nombre_avis, dernier_test, test_ancien and page. Sectors: beaute, mode, maison, sport, epicerie, enfant, animalerie, bijoux, bricolage, high-tech. Unknown sector: error result listing the valid ones.
| Name | Type | Req | Description |
|---|---|---|---|
| langue | string | – | Language of the page links and, for consulter_marchand, of the summary sentence: fr (default) or en. Data fields are the same in both. |
| secteur | string | yes | Sector id. |
No output schema declared.
No examples provided.
comparer_marchands Comparer des marchands ~190
Side-by-side test results for two to five French online stores you already know, in the order given. Use it when the user hesitates between specific stores. To find candidates first, use trouver_marchands or rechercher_marchand. Returns: marchands, one full result per store, identical to consulter_marchand (score out of 100, six steps acces to caisse, proven facts, machine readability, UCP checkout, summary and page). Each store counts as one request against the rate limit. Fewer than two or more than five domains: error result.
| Name | Type | Req | Description |
|---|---|---|---|
| domaines | array | yes | Two to five store domains, for example ["respire.co", "typology.com"]. |
| langue | string | – | Language of the page links and, for consulter_marchand, of the summary sentence: fr (default) or en. Data fields are the same in both. |
No output schema declared.
No examples provided.
consulter_marchand Consulter un marchand ~340
Full test result for ONE French online store, by domain: what an AI shopping agent managed to do there at the latest test. Use it before visiting, recommending or buying from a French store, or when the user asks if a store works with AI agents. To find stores you do not know yet, use trouver_marchands; to look up a store by name, rechercher_marchand; to put several side by side, comparer_marchands. Returns: note (score out of 100: journey 55, proven purchase facts 30, machine readability 15), etapes (six steps in order — acces, cookies, recherche, fiche, panier, caisse — each reussi, partiel, echec or non_atteint, with a motif when it failed), faits (oui, non or inconnu: checkout without an account, delivered price before sign-up, shipping costs, return policy, third-party seller), machine (product data, robots.txt, llms.txt, sitemap, UCP), ucp_commande (store declares UCP checkout), dernier_test (date), test_ancien (true if older than 90 days), resume (one-sentence summary to quote) and page (link to cite). Unknown or untracked domain: error result, nothing charged.
| Name | Type | Req | Description |
|---|---|---|---|
| domaine | string | yes | Store domain, for example respire.co. A full URL or a www. prefix is accepted and normalised. |
| langue | string | – | Language of the page links and, for consulter_marchand, of the summary sentence: fr (default) or en. Data fields are the same in both. |
No output schema declared.
No examples provided.
rechercher_marchand Rechercher un marchand ~208
Find a tracked French store by part of its NAME or DOMAIN, across all sectors (case and accents ignored). Use it when the user names a store but you do not know its exact domain; then call consulter_marchand with the domain found. To discover stores by criteria rather than by name, use trouver_marchands. Returns: requete and marchands, every match (usually a few) with rang in its sector, ex_aequo, secteur, domaine, nom, note out of 100, nombre_avis, dernier_test, test_ancien and page. No match: an empty list, which means the store is not tracked yet.
| Name | Type | Req | Description |
|---|---|---|---|
| langue | string | – | Language of the page links and, for consulter_marchand, of the summary sentence: fr (default) or en. Data fields are the same in both. |
| requete | string | yes | At least two characters of the store name or domain, for example nocibe or sezane. |
No output schema declared.
No examples provided.
trouver_marchands Trouver des marchands par critères ~393
Discover French online stores where an AI agent can actually buy, filtered by PROVEN facts, in one sector or all of them. Use it when the user asks where to buy something online in France, which stores allow guest checkout, or which show the delivered price. To look up a store by name, use rechercher_marchand; for a whole sector ranking, classement_secteur. Every filter is optional; set a boolean to true to require that fact. Returns: secteur, criteres (filters applied), total (number of matching stores) and marchands, best score first, at most limite entries, each with rang, ex_aequo, secteur, domaine, nom, note out of 100, the five facts as booleans (sans_compte, prix_livre, frais_livraison, retours, ucp_commande), dernier_test and page. No match: total 0 and an empty list.
| Name | Type | Req | Description |
|---|---|---|---|
| frais_livraison | boolean | – | Shipping costs were found. |
| langue | string | – | Language of the page links and, for consulter_marchand, of the summary sentence: fr (default) or en. Data fields are the same in both. |
| limite | integer | – | Maximum number of stores returned (default 20, at most 50); total still counts every match. |
| note_min | number | – | Minimum score out of 100. |
| prix_livre | boolean | – | Total price including delivery was shown before any sign-up. |
| retours | boolean | – | Return policy was found and quoted. |
| sans_compte | boolean | – | Agent reached checkout without creating an account (proven by a screenshot or quote). |
| secteur | string | – | Restrict to one sector; all sectors if omitted. |
| ucp | boolean | – | Store publishes a UCP profile that declares checkout, so an agent can order through the protocol. |
No output schema declared.
No examples provided.
How do I install the Neoavis MCP server?
Neoavis is a hosted endpoint at https://neoavis.com/api/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 · neoavis.com
claude mcp add --transport http com-neoavis-constats 'https://neoavis.com/api/mcp'
What is the Neoavis MCP server?
Neoavis is an MCP server listed in the public MCP registry as com.neoavis/constats. Can an AI agent buy on this French store? 500 stores tested: score, guest checkout, UCP. Free. This page covers its hosted endpoint (https://neoavis.com/api/mcp).
Is the Neoavis MCP server safe to use?
Neoavis scores 77 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 Neoavis MCP server expose?
Neoavis exposes 5 tools: consulter_marchand, classement_secteur, rechercher_marchand, trouver_marchands, comparer_marchands. Their descriptions and schemas cost roughly 1,361 tokens of context every time the server is loaded.
Does the Neoavis MCP server require authentication?
No. We connected to Neoavis without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Neoavis MCP server still maintained?
Neoavis is still listed as active in the MCP registry. We last reached this channel on 5 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 Neoavis MCP server?
VerifyMCP ran 13 checks on Neoavis, 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.