How to Use npm package dependents in Manus
Returns npm packages that depend on a package. Use it to discover downstream integrations and choose packages to review before a breaking change.
Prompts to try with npm package dependents in Manus
Copy an example into Manus, or ask in your own words.
Use npm package dependents to look this up and give me the result as a table.
Pull the latest numbers from npm package dependents and tell me what changed since last week.
Check npm package dependents and summarize what you find in three bullet points.
Pull the newest data from npm package dependents and give me the result as a table.
Check npm package dependents every morning and tell me only when something changed.
How to set up npm package dependents in Manus
Pick the way that suits you. Each takes about two minutes.
Use the Manus connector
- Add a custom MCP connector
In Manus open Settings › Connectors (or the connectors icon under the chat box), then Add connectors › Custom MCP and Add MCP by URL. Name it Spiral, set Transport to HTTP and paste this Server URL:
https://api.spiral.ai/mcp
- Sign in to Spiral and approve
Manus asks you to sign in the first time it uses Spiral. Spiral opens: sign in, pick the organization and click Authorize. No API key. Spiral gives the connection its own key; Manus never sees it, and you can remove it under Settings › Connected apps in the console.
Use the Spiral skill
- Send Manus this message
Your agent reads Spiral's skill and sets itself up.
set up https://spiral.ai/SKILL.md
- Sign in or paste a key
Approve Spiral in the browser, or give the agent a key from the console.
Use the Spiral CLI
- Install and sign in
Installs the Spiral CLI, signs you in and adds its skill to your coding agents.
npx -y spiral-cli@latest init
Call the Spiral API
- Create an API key
In the console, under API keys.
- Run npm package dependents
One request; the result comes back by polling or a webhook.
curl https://api.spiral.ai/v1/runs \ -H "Authorization: Bearer $SPIRAL_API_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: $(uuidgen)" \ -d '{ "provider": "alexandria", "model": "npmjs-com/packages/list_dependents", "input": { "package": "<package>" } }'
Then paste one of the prompts above: Manus finds npm package dependents on Spiral, shows the price and runs it.
npm package dependents providers and prices
Spiral runs npm package dependents through Alexandria. Open a card for today's price, with every fee included.
What can you do with npm package dependents in Manus?
Create a comparison table for an npm package decision. Explain what the returned package records or download measurements contribute to that decision.
Plan a major version migration
Review release requirements and downstream packages alongside download totals, daily trends, and version shares. Use the evidence to choose compatibility tests and prioritize migration documentation.
Prepare a weekly package review
Compare saved publisher listings, package metadata, release details, and returned dependent names. Add changes in download totals, daily patterns, and version shares to identify items worth reviewing.
Find downstream integrations
Start with dependent packages and publisher catalogs, then use search and name suggestions to find related integrations. Review descriptions and download totals to select packages for compatibility testing.
Research package adoption
Define a package sample through search and publisher listings. Compare download totals, daily trends, version shares, and downstream package relationships for an adoption report.
More on npm package dependents and Manus
Overview
npm package dependents in other agents
Questions about npm package dependents in Manus
Can Manus use npm package dependents?
Yes. Add Spiral to Manus as an MCP server, and Manus can find and run npm package dependents like any built-in tool.
How much does npm package dependents cost in Manus?
$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your Manus plan is separate.
Do I need an Alexandria account to use npm package dependents in Manus?
No. Spiral runs npm package dependents on its own Alexandria account. You sign in to Spiral once and never paste a key.
How long does it take to set up npm package dependents in Manus?
About two minutes: add a custom MCP connector, then sign in to Spiral and approve.
Does Manus wait while npm package dependents runs?
npm package dependents runs in the background. Manus starts the run, checks on it and gives you the json when it's ready.
How fresh are npm download statistics?
npm documents a daily process that aggregates the previous day's logs after UTC midnight. Download statistics therefore describe completed reporting days.
Why might a published package be missing from npm search?
npm says newly published packages can take up to two weeks to appear. Deprecated packages are excluded from search results.
Do npm download counts represent unique users?
No. npm counts successful package tarball responses, including downloads from automated builds, mirrors, and analysis robots.
How much download history can npm return at once?
npm limits download queries other than bulk queries to 18 months per request. Per-version download counts cover only the previous seven days.
Does npm search return every match in one response?
npm registry search returns at most 250 matches per request and supports offset pagination. The response also reports a total.
Start using npm package dependents in Manus
One Spiral account for every tool your agent needs. No subscription; you pay per run.
Paste this into Manus:
set up https://spiral.ai/SKILL.md


