ToolTrust
A2/100
docfork

docfork-docfork

mcp2.1.0

@docfork

Docfork - Up-to-date docs for AI Coding Agents.

By docfork | 7 findings | Scanned 10/15/2026 | tooltrust-scanner/v0.3.20 | 486

Repository health

Popularity and maintenance signals alongside the security grade.

View repository
Stars

486

current snapshot

Forks

38

current snapshot

Contributors

4

public GitHub contributors

Last commit

Jun 13, 2026

GitHub repository activity

Last release

May 25, 2026

dgrep: v0.2.2

Release version

dgrep-v0.2.2

Latest GitHub release

Stars trend

Daily star additions · History data pending

—

No observed star events yet.

——

Pull request activity

Weekly PR events · History data pending

No observed PR events yet.

——
TypeScriptMITDeveloper Tools700/mo npm downloadsLast scan Oct 15, 2026
2 Low5 Info

Risk Summary

Safe With Normal Controls

Excessive Permissions is the main signal, but overall risk remains within an acceptable range.

Potential impact: The agent may gain overly broad access to files, network, databases, or execution capabilities.

Recommended action: No high-risk findings were detected in this scan, but you should still apply least-privilege defaults and rescan after changes.

Suggested policy: keep this tool behind manual approval, do not allow unattended runs, and re-scan after narrowing risky permissions.

Security Findings (7)

  • LowAS-011

    ℹ️Missing Rate-Limit / Timeout ×2

    tool performs network or execution operations but declares no rate-limit, timeout, or retry configuration

    docfork_search_docsdocfork_read_url

    Fix: Declare explicit rate-limit, timeout, and retry configuration for all network and execution tools. Implement exponential back-off and surface resource state to the calling agent.

  • InfoAS-002

    ⚠️Excessive Permissions ×2

    declared capabilities: network access, filesystem access

    docfork_search_docsdocfork_read_url

    Fix: Tool requests broad permissions (exec/fs/network). Validate input parameters using Enums where possible, and restrict file system operations to explicit allowed directories.

  • InfoAS-010

    🔑Insecure Secret Handling

    docfork_search_docs:input parameter "tokens" accepts a credential (informational; not evidence of insecure handling)

    Fix: Avoid accepting raw credentials as input parameters. Use secret managers (e.g. 1Password CLI, AWS Secrets Manager) and ensure credentials are never logged or stored in agent traces.

  • InfoAS-014

    ℹ️Dependency Inventory Unavailable ×2

    Tool did not expose metadata.dependencies or repo_url, so supply-chain coverage is limited.

    docfork_search_docsdocfork_read_url

    Fix: Review and remediate the identified issue.

Scan this tool yourself

Reproduce this audit locally, integrate into CI, or let your agent audit its own tools.

Install once, then scan any MCP server:

$ curl -sfL https://raw.githubusercontent.com/AgentSafe-AI/tooltrust-scanner/main/install.sh | bash
$ tooltrust-scanner scan --server "npx -y docfork-docfork"

Adjust the package name if your npm registry name differs from the tool ID. View source

Add badge to your README

Copy this Markdown to show your ToolTrust grade on GitHub.

[![ToolTrust Grade A](https://raw.githubusercontent.com/AgentSafe-AI/tooltrust-directory/main/docs/badges/grade-a.svg)](https://github.com/AgentSafe-AI/tooltrust-directory)