2 checks that ran failed — permission scope and version behavior — so this release can’t be trusted as-is.
- Publisher
- app.apiguru
- Repository
- github.com/apiguru-app/agent-kit
- Install
- pypi:apiguru-mcp, pypi:apiguru-mcp, pypi:apiguru-mcp, npm:apiguru-mcp, pypi:apiguru-mcp, npm:apiguru-mcp, pypi:apiguru-mcp, npm:apiguru-mcp, pypi:apiguru-mcp, npm:apiguru-mcp, pypi:apiguru-mcp, npm:apiguru-mcp, pypi:apiguru-mcp, npm:apiguru-mcp, pypi:apiguru-mcp, npm:apiguru-mcp, pypi:apiguru-mcp, npm:apiguru-mcp, pypi:apiguru-mcp, npm:apiguru-mcp, pypi:apiguru-mcp, npm:apiguru-mcp, pypi:apiguru-mcp, npm:apiguru-mcp, pypi:apiguru-mcp, npm:apiguru-mcp, pypi:apiguru-mcp, npm:apiguru-mcp, pypi:apiguru-mcp, npm:apiguru-mcp, pypi:apiguru-mcp, npm:apiguru-mcp, pypi:apiguru-mcp, npm:apiguru-mcp, pypi:apiguru-mcp, npm:apiguru-mcp, pypi:apiguru-mcp, npm:apiguru-mcp, pypi:apiguru-mcp, npm:apiguru-mcp, pypi:apiguru-mcp, npm:apiguru-mcp, pypi:apiguru-mcp, npm:apiguru-mcp, pypi:apiguru-mcp, npm:apiguru-mcp
- Versions
- 24
- MCP revision
- 2025-11-25 · superseded
- Inspected
- 6 of 6 checks · 100%
- Scored
- 2026-09-09 · rubric 1.0.0
What we checked
Six static checks, weighted by risk. Every result reflects only what could be observed in the published package and repository — never intent.
Injection surface
pass25% of gradeTool descriptions/manifest scanned for instruction-injection patterns (imperatives at the model, hidden text, 'ignore previous', data-exfil URLs).
Scanned 184 text field(s); no instruction-injection patterns found. PASS = no static red flag. A server can serve different tool descriptions at runtime (the rug-pull class), which static scanning cannot see.
Supply chain
pass25% of gradePackage provenance: namespace verification, repo linkage, maintainer count, account age, postinstall scripts, typosquat distance.
repository linkage verified
Credential hygiene
pass15% of gradeHow the server takes secrets (env vs plaintext config vs hardcoded); secrets appearing in tool schemas.
Reads secrets from the environment (e.g. bin/apiguru-mcp.mjs) — the recommended intake shape. PASS = no static red flag; static analysis cannot prove the code honors env-based secret handling at runtime.
Permission scope
fail15% of gradeDeclared tools vs. breadth (filesystem, network, exec); flags shell-exec and unbounded filesystem access.
HIGH: shell/exec capability is incongruent with a read-only declared purpose (tools look like lookup/read-only but source imports command execution). discloses shell/exec capability: bin/apiguru-mcp.mjs: imports child_process and calls exec/spawn Capability DISCLOSURE, not a verdict: static analysis sees the primitive is present and reachable, not whether its use is attacker-controlled.
Version behavior
fail10% of gradeDiff of tool definitions between versions; new permissions or changed descriptions in a patch release (the postmark-mcp class).
vs prior 1.1.20 (patch bump): tool "product_reviews" description changed (wording only, no injection pattern); tool "search" description changed (wording only, no injection pattern); tool "search" gained input property(ies): deal_type; tool "best_sellers" description changed (wording only, no injection pattern); tool "deals" description changed (wording only, no injection pattern); tool "deals" gained input property(ies): min_price, max_price, min_discount, max_discount, prime_exclusive; tool "seller_products" description changed (wording only, no injection pattern); tool "seller_products" gained input property(ies): query, sort_by, category_id, min_price, max_price, product_condition, brand, today_deals, deal_type; tool "seller_reviews" description changed (wording only, no injection pattern); new capability primitive(s) in source: child_process; new hardcoded outbound host/BCC destination(s): apiguru.app, docs.astral.sh, github.com, mcp.apiguru.app.
Transport config
pass10% of gradeRemote servers: TLS and auth mode (none/token/OAuth). Local servers: whether the manifest indicates it phones home.
remote endpoint "https://mcp.apiguru.app/mcp" uses TLS (https); remote endpoint uses OAuth (strongest auth mode)
Version history
Each release plotted by grade against the safe line at B. A version that sinks below the line has lost its trusted standing — the shape of a rug-pull.
| Version | Published | Grade | Score | Inspected | Change |
|---|---|---|---|---|---|
| v1.1.22 · current | 2026-09-08 | B | 75 | 6/6 · 100% | A→B in v1.1.22 |
| v1.1.20 | 2026-09-07 | A | 95 | 6/6 · 100% | ±0 |
| v1.1.18 | 2026-09-06 | A | 100 | 6/6 · 100% | ±0 |
| v1.1.7 | 2026-09-05 | A | 90 | 6/6 · 100% | ±0 |
| v1.1.2 | 2026-09-04 | A | 100 | 5/6 · 90% | — |