中文 · English

← Evidence index

trendsapi-ai

21 MCP servers associated with this publisher in public records · generated 2026-09-22T12:17:45.454Z

incomplete 21

Records

ServerVerdictPackageFindings
ai.trendsapi/amazonincomplete0 finding(s)
ai.trendsapi/app-storeincomplete0 finding(s)
ai.trendsapi/competitor-trackingincomplete0 finding(s)
ai.trendsapi/content-strategyincomplete0 finding(s)
ai.trendsapi/cryptoincomplete0 finding(s)
ai.trendsapi/ecommerceincomplete0 finding(s)
ai.trendsapi/google-trendsincomplete0 finding(s)
ai.trendsapi/market-researchincomplete0 finding(s)
ai.trendsapi/news-sentimentincomplete0 finding(s)
ai.trendsapi/news-volumeincomplete0 finding(s)
ai.trendsapi/npmincomplete0 finding(s)
ai.trendsapi/redditincomplete0 finding(s)
ai.trendsapi/seoincomplete0 finding(s)
ai.trendsapi/social-mediaincomplete0 finding(s)
ai.trendsapi/spotifyincomplete0 finding(s)
ai.trendsapi/steamincomplete0 finding(s)
ai.trendsapi/tiktokincomplete0 finding(s)
ai.trendsapi/trendsincomplete0 finding(s)
ai.trendsapi/wikipediaincomplete0 finding(s)
ai.trendsapi/x-twitterincomplete0 finding(s)
ai.trendsapi/youtubeincomplete0 finding(s)

Scope

Data comes from public registry entries and manifests of packages that were actually published. Each row opens a standalone evidence page.

Repository source is outside this index’s scan scope. Run the CLI locally for source scanning.

A finding is a matched shape, not a conclusion. It does not prove exploitability. Unmeasured work is listed on each server page and is never treated as clean.