Autonomous x402 Token Stripper API settling $0.002 USDC micro-payments on Base L2.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
extract_clean_web_dataFetch web content stripped of bloat for cheap token processing.Fetch web content stripped of bloat for cheap token processing.
No input schema was published for this tool.
extract_textStrips scripts, styles, and HTML tags from a URL to return context-efficient plain text for LLMs.Strips scripts, styles, and HTML tags from a URL to return context-efficient plain text for LLMs.
No input schema was published for this tool.
2 of 2 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Autonomous x402 Token Stripper API settling $0.002 USDC micro-payments on Base L2.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.