apinoa
NPM · APINOA-MCP · 2 COMPONENTS
Products, social posts, search results and AI answers from Amazon, TikTok, Google, ChatGPT and more.
Available components
Last scanned (1 hour ago)
Scores higher than 50% of npm servers
Category Search and Retrieval
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 Security98
- 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
- 30 of 99 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to apinoahq/apinoa-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability49
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1537 tokens (~512/item across 3 items; 3 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 Management3
- Stability observed for 1 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "execute" implies "execute" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
- An AI judge read all 4 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
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 74
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 · Analysed npm/apinoa-mcp@0.2.8
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | apinoahq/apinoa-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/apinoahq/apinoa-mcp/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3691551886 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:7d0ad5d87a8c6cb68299eda30081848f0274e0c3ac467e73870264722d645b5d18dafa70e427bcc3bef435eef13dd66ca3a0c306df047c8c8343ded7f |
Background: How many MCP packages publish verified provenance →
Dependencies 99 packages
| Packages resolved | 99 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
execute Run code against apinoa ~1,012
Run TypeScript that calls the apinoa API, and get back only what it prints or returns. Use it for every data task, from one call to thousands: fan out over accounts or posts, follow pages, then filter, count, rank and average in the code, so raw API answers never fill the conversation. The code is the body of an async function: use await, and `return` a small result (aggregate, slice, pick the fields you need). In scope: - apinoa.<platform>.<operation>(params): one API call, returns the answer's data; throws ApinoaError (code, status) on a refusal. search_docs lists the parameters and the fields returned. - pages(op, params, { maxPages }): every item of a paged operation, following cursors (default 5 pages). - many(items, fn, { concurrency }): fn over every item, 8 at a time by default; a failed item comes back undefined. - store.save(name, value) / store.load(name) / store.list() / store.saveFile(name, base64): data kept on this machine between runs. - usage: { calls, units, budget } of this run. The code is type-checked before it runs: an operation, parameter or field that does not exist fails there, before anything is billed. Each call costs units (1 unit = $0.001, per search_docs); the run stops once budget_units are spent. Answers are cached for 10 minutes, so re-running after a fix costs nothing for calls already made. Only the API is reachable from the code. Example: const page = await apinoa.tiktok.posts({ hashtag: "glassskin", limit: 50 }); const authors = [...new Set(page.items.map((p) => p.author.handle))].slice(0, 10); const recent = await many(authors, (u) => apinoa.tiktok.posts({ username: u, limit: 30 })); return authors.map((u, i) => { const views = (recent[i]?.items ?? []).map((p) => p.metrics?.views ?? 0).sort((a, b) => a - b); return { author: u, median: views[Math.floor(views.length / 2)] ?? null }; }); Operations (call search_docs with words or a platform for parameters, costs and the fields returned): - apinoa.aliexpress: search, browse…
| Name | Type | Req | Description |
|---|---|---|---|
| budget_units | integer | – | Most units this run may spend (default 500, at most 20000). |
| code | string | yes | TypeScript: the body of an async function. Return the result. |
| timeout_seconds | integer | – | Stop the run after this long (default 300). |
No output schema declared.
No examples provided.
search_docs Search the apinoa docs ~248
Find how to do a task with apinoa: the matching operations as you call them in execute (e.g. apinoa.tiktok.posts({ hashtag })), every parameter, the cost per call, and the fields of what they return. Free: it calls nothing. Use it before writing code. Pass words ('tiktok hashtag videos', 'instagram reels of an account', 'amazon product reviews'), a platform, or a type name ('Post'); with neither you get the list of every operation. Platforms: aliexpress, amazon, app-store, baidu, bing, chatgpt, daum, duckduckgo, gemini, google, google-ai-mode, google-aio, google-play, google-shopping, google-trends, instagram, linkedin, naver, naver-ai-brief, naver-ai-tab, reddit, seznam, shopify, sogou, threads, tiktok, tiktokshop, tripadvisor, walmart, x, yahoo, yahoo-japan, yandex, youtube.
| Name | Type | Req | Description |
|---|---|---|---|
| platform | string | – | Only this platform's operations. |
| query | string | – | What you want to do or read, in a few words, or a type name. |
No output schema declared.
No examples provided.
translate_image Translate the text in an image ~123
Replace the text inside a product image with a translation, keeping fonts, colours and layout. Give the image as a URL. Returns the translated image.
| Name | Type | Req | Description |
|---|---|---|---|
| font | string | – | A font name from supported fonts. Default Pretendard. |
| image_url | string | yes | An http(s) URL of a JPEG, PNG or WebP image. |
| source_language | string | yes | The language of the text in the image, or auto. |
| target_language | string | yes | The language to translate into, e.g. ko, en, ja, zh-CN. |
No output schema declared.
No examples provided.
How do I install the apinoa MCP server?
apinoa runs locally as an npm package, launched with npx -y apinoa-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 · apinoa-mcp
claude mcp add apinoahq-apinoa-mcp -- npx -y apinoa-mcp
What is the apinoa MCP server?
apinoa is an MCP server listed in the public MCP registry as io.github.apinoahq/apinoa-mcp. Products, social posts, search results and AI answers from Amazon, TikTok, Google, ChatGPT and more. This page covers its npm package (apinoa-mcp).
Is the apinoa MCP server safe to use?
apinoa scores 75 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. Its build provenance is signed and verified. 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 apinoa MCP server expose?
apinoa exposes 3 tools: search_docs, execute, translate_image. Their descriptions and schemas cost roughly 1,383 tokens of context every time the server is loaded.
Is the apinoa MCP server still maintained?
apinoa 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 apinoa MCP server under?
apinoa declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.