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.

AutoSugges

NPM · @AUTOSUGGES/MCP

Autocomplete over edge-served reference lists (countries, NAICS, airports), plus catalog and setup.

Available components

+3 this week 74 Trust /100

Last scanned (5 hours ago)

Scores higher than 48% of npm servers

Category Search and Retrieval

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
Schema Quality & AI Usability75
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 283 tokens (~70/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
  • Stability observed for 11 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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
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.

  • 4 Nov 26 +1

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

  • 2 Nov 26 +1

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

  • 31 Oct 26 +1

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

  • 29 Oct 26 +1

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

  • 27 Oct 26 +1

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

  • 26 Oct 26 +26
    • Malware scan: unverified → pass ▲ security
    • Known CVEs: unverified → pass ▲ security
    • Dependency health: unverified → pass ▲ functional
  • 25 Oct 26 43

    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 5 Nov 2026 · Analysed npm/@autosugges/mcp@0.1.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~283 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
get_dataset ~50

Metadata for one platform dataset by slug, plus its docs URL. Never returns items; use search_list to query.

NameTypeReqDescription
slugstringyesDataset slug from list_datasets, e.g. "countries".

No output schema declared.

No examples provided.

get_integration_instructions ~43

Self-contained, agent-ready instructions for integrating AutoSugges into a framework or using one runtime endpoint.

NameTypeReqDescription
frameworkstringyesTarget framework or HTTP topic.

No output schema declared.

No examples provided.

list_datasets ~35

Catalog of AutoSugges platform datasets: slug, name, description, category, availability, authority. Metadata only; never items.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_list ~155

Autocomplete against an AutoSugges reference list (countries, NAICS, airports, currencies, ...). Returns the ranked, bounded suggestions for ONE query; it cannot enumerate a list. The publishable key (server env) decides which list is searched.

NameTypeReqDescription
limitinteger–Max suggestions; capped by the list policy.
liststring–Informational list name or slug. The configured key selects the list.
localestring–BCP-47 tag for display values, e.g. "fr".
parentstring–Item id of a parent (hierarchical lists only), to restrict to its descendants.
querystringyesText typed so far; at least 2 characters.

No output schema declared.

No examples provided.

Install

How do I install the AutoSugges MCP server?

AutoSugges runs locally as an npm package, launched with npx -y @autosugges/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @autosugges/mcp

# add to Claude Code
claude mcp add autosugges-autosugges-mcp -- npx -y @autosugges/mcp
Common questions

What is the AutoSugges MCP server?

AutoSugges is an MCP server listed in the public MCP registry as io.github.autosugges/autosugges-mcp. Autocomplete over edge-served reference lists (countries, NAICS, airports), plus catalog and setup. This page covers its npm package (@autosugges/mcp).

Is the AutoSugges MCP server safe to use?

AutoSugges scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 AutoSugges MCP server expose?

AutoSugges exposes 4 tools: search_list, list_datasets, get_dataset, get_integration_instructions. Their descriptions and schemas cost roughly 283 tokens of context every time the server is loaded.

Is the AutoSugges MCP server still maintained?

AutoSugges 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 licence is the AutoSugges MCP server under?

AutoSugges declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.