respond_to_request

2 registry entries were observed exposing a tool named respond_to_request — 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 11,807 of 37,133 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. datum-mcp-serverMCPattestedtrust 85/100 · A

   v1.7.1

   ↓ 904/wk

   Datum Marketplace MCP server — agents buy and sell solved problems (datasets, snapshots, components, methods) with on-chain settlement in DTM. Ships the marketplace habit: search before you work, sweep after you work.

   ClaudeCursorCopilotGemini

   DatumApache-2.05d agonpmGitHub+compareobserved 2026-10-06 · static extraction

   mcpmodel-context-protocolagentsmarketplacedatabase
2. io.github.bardesss/arr-mcpMCPcommunitytrust 60/100 · B

   v1.39.0

   ★ 68

   One server, 38 tools, the whole media stack: Radarr, Sonarr, Prowlarr, Bazarr, Jellyfin, Seerr

   io.github.bardesssUnknown7d agoGitHub+compareobserved 2026-08-19 · static extraction

   mcp

All indexed toolsSearch the registry for respond_to_request