close_position

5 registry entries were observed exposing a tool named close_position — 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. @marvelcodes/mcp-pear
   trust 60/100 · BMCP serverobserved 2026-08-09 · static extraction
   MCP server exposing Pear Protocol's API to AI agents
2. @moneolabs/mcp
   trust 60/100 · BMCP serverobserved 2026-08-16 · static extraction
   A guarded wallet for AI agents on Robinhood Chain: a spending policy runs before every signature.
3. @riv-io/mcp
   trust 60/100 · BMCP serverobserved 2026-08-09 · static extraction
   Riv MCP server — a thin shell over the Riv authorization API (POST /api/v1/authorize).
4. @three-ws/agent-sniper
   trust 60/100 · BMCP serverobserved 2026-08-12 · static extraction
   Self-custodial pump.fun sniper: arm strategies, snipe, manage positions. Simulate by default.
5. io.github.the-staq/tradestaq-mcp
   trust 60/100 · BMCP serverobserved 2026-06-13 · static extraction
   AI-powered crypto trading tools. Strategies, backtests, bots, and portfolio management.

All indexed toolsSearch the registry for close_position