get_file_contents

5 registry entries were observed exposing a tool named get_file_contents — none of them flagged as a privileged capability.

Every row is point-in-time scan output, dated below. Forge has an observed tool surface for 8,470 of 26,658 scannable entries (32%) — an entry that has not been scanned cannot appear here, so absence from this list is not evidence that an entry does not expose this tool.

  1. trust 85/100 · AMCP serverobserved · static extraction
    Repo analysis for coding agents with ranked files, dependency maps, and task-scoped context.
  2. trust 60/100 · BMCP serverobserved · static extraction
    GitLab MCP server for projects, merge requests, issues, pipelines, wiki, releases, and more.
  3. trust 60/100 · BMCP serverobserved · static extraction
    Reference MCP servers that are no longer maintained
  4. trust 60/100 · BMCP serverobserved · static extraction
    MCP server for GitHub — search repos/code/issues, read repos/issues/PRs/files, and create issues, authenticated via OAuth device flow or a t
  5. trust 60/100 · BMCP serverobserved · static extraction
    MCP server for GitLab and GitHub

All indexed toolsSearch the registry for get_file_contents