MCP server for code search — structured ripgrep, fd, jq, and yq results for AI agents
Inferred from the transports this listing declares (stdio). 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 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.
countCounts pattern matches per file using ripgrep. Returns per-file match counts and totals.Counts pattern matches per file using ripgrep. Returns per-file match counts and totals.
No input schema was published for this tool.
findFinds files and directories using fd with structured output. Returns file paths, names, and extensions.Finds files and directories using fd with structured output. Returns file paths, names, and extensions.
No input schema was published for this tool.
searchSearches file contents using ripgrep with structured JSON output. Returns match locations with file, line, column, matched text, and line content.Searches file contents using ripgrep with structured JSON output. Returns match locations with file, line, column, matched text, and line content.
No input schema was published for this tool.
jqProcesses and transforms JSON using jq expressions. Accepts JSON from a file path or inline string. Returns the transformed result.Processes and transforms JSON using jq expressions. Accepts JSON from a file path or inline string. Returns the transformed result.
No input schema was published for this tool.
yqProcesses and transforms YAML, JSON, XML, TOML, and properties files using yq expressions. Accepts input from a file path or inline string. Returns the transformed result.Processes and transforms YAML, JSON, XML, TOML, and properties files using yq expressions. Accepts input from a file path or inline string. Returns the transformed result.
No input schema was published for this tool.
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.
MCP server for code search — structured ripgrep, fd, jq, and yq results for AI agents
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
The crawl stopped at the depth-4 limit. Anything below that level was never resolved.
The crawl stopped at the 60-package limit. The rest of the tree was never resolved.
36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)
54 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.
+42 more not listed. The counts by reason above cover all of them.
Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.