check_access_status

5 registry entries were observed exposing a tool named check_access_status — 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. @spideriq/mcp-gate
    trust 60/100 · BMCP serverobserved · static extraction
    SpiderIQ Gate MCP Server — SpiderGate LLM gateway (completions, models, usage, traces) for AI assistants
  2. @spideriq/mcp-leads
    trust 60/100 · BMCP serverobserved · static extraction
    SpiderIQ Leads MCP Server — lead gen, scraping, enrichment (jobs, campaigns, IDAP, Maps, People, Verify) for AI assistants
  3. @spideriq/mcp-mail
    trust 60/100 · BMCP serverobserved · static extraction
    SpiderIQ Mail MCP Server — SpiderMail mailboxes, messages, threads, send, compose for AI assistants
  4. @spideriq/mcp-media
    trust 60/100 · BMCP serverobserved · static extraction
    SpiderIQ Media MCP Server — SpiderMedia files, videos, and the per-tenant media catalog (read) for AI assistants
  5. @spideriq/mcp-publish
    trust 60/100 · BMCP serverobserved · static extraction
    SpiderIQ Publish MCP Server — content platform tools (pages, posts, templates, components, domains, media) for AI assistants

All indexed toolsSearch the registry for check_access_status