Is this dependency current, licensed, deprecated, or already carrying a CVE?
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read from a real MCP initialize → tools/list handshake against the declared endpoint. No tool was ever invoked — tools/list is the read-only introspection call the protocol defines for this. It reflects what the server advertised at that moment; a hosted endpoint is not pinned to any version and can change without notice.
https://devpkg-intel.bowling-anthony.workers.dev/mcp5 tools · 116msrequest_dataFREE, no payment. Describe in your own words the data you are trying to buy — anything, not just packages — and get back whether we operate a service that supplies it, with the MCP endpoint if so. Every request is catalogued so repeatedly-requested data gets built. Nothing identifying is stored, on…FREE, no payment. Describe in your own words the data you are trying to buy — anything, not just packages — and get back whether we operate a service that supplies it, with the MCP endpoint if so. Every request is catalogued so repeatedly-requested data gets built. Nothing identifying is stored, on…
| Parameter | Type | Description |
|---|---|---|
| need* | string | What you are looking for. |
demand_reportFREE, no payment. The aggregate of what agents have told us they are looking for, most-requested first, with the categories nothing available yet serves.FREE, no payment. The aggregate of what agents have told us they are looking for, most-requested first, with the categories nothing available yet serves.
| Parameter | Type | Description |
|---|---|---|
| days | string | Window in days, default 30, max 90. |
package_infoLook up a package in npm, PyPI or crates.io: latest version, licence, whether it is deprecated or yanked, when it was last published, dependency count and repository. Use before writing a dependency line, or to check whether a pinned version is behind. Registries answer with hundreds of kilobytes;…Look up a package in npm, PyPI or crates.io: latest version, licence, whether it is deprecated or yanked, when it was last published, dependency count and repository. Use before writing a dependency line, or to check whether a pinned version is behind. Registries answer with hundreds of kilobytes;…
| Parameter | Type | Description |
|---|---|---|
| ecosystem* | string | One of 'npm', 'pypi', 'crates' (aliases: node, python, rust). |
| name* | string | Package name, e.g. 'express', '@scope/pkg', 'requests', 'serde'. |
package_vulnerabilitiesKnown security advisories for a package from OSV, the open advisory database. Returns advisory ids, severity, summary and the versions that fix each one. Pass 'version' to ask only about the version you are about to install; omit it to see advisories affecting any version. Use before pinning a depe…Known security advisories for a package from OSV, the open advisory database. Returns advisory ids, severity, summary and the versions that fix each one. Pass 'version' to ask only about the version you are about to install; omit it to see advisories affecting any version. Use before pinning a depe…
| Parameter | Type | Description |
|---|---|---|
| ecosystem* | string | One of 'npm', 'pypi', 'crates'. |
| name* | string | Package name. |
| version | string | Optional exact version, e.g. '4.17.20'. Narrows advisories to that version. |
package_auditOne call that answers whether a dependency is safe to add: latest version, licence, deprecation, advisories affecting the current version, how long since the last release, and a verdict with the specific concerns found. Prefer this over calling package_info and package_vulnerabilities separately —…One call that answers whether a dependency is safe to add: latest version, licence, deprecation, advisories affecting the current version, how long since the last release, and a verdict with the specific concerns found. Prefer this over calling package_info and package_vulnerabilities separately —…
| Parameter | Type | Description |
|---|---|---|
| ecosystem* | string | One of 'npm', 'pypi', 'crates'. |
| name* | string | Package name. |
5 of 5 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.
Is this dependency current, licensed, deprecated, or already carrying a CVE?
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.