Ostorlab

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as co.ostorlab/mcp and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 26 Oct 2026. Not supplied by the maker.

• me

  Describe the calling API key and the organisation it belongs to. The caller is an API key, not a user account. Args: ctx: The MCP request context holding connection parameters. Returns: The

• list_vulnerabilities

  List vulnerabilities for the authenticated organisation with optional filtering. Object-level scoping is performed at the scan level via the same ``shared_access.access.get_scan_with_access`` helper

• search_vulnerabilities

  Find findings across every scan, filtered by application, date and severity. Reach for this whenever the question spans more than one scan — "all criticals on this app", "what did we find last month"

• get_vulnerability

  Get detailed information for a single vulnerability by database id. Args: ctx: FastMCP Context holding connection path parameters. vulnerability_id: The database id of the vulnerability. Ret

• update_vulnerability

  Update a vulnerability's risk rating, CVSS vectors, or triage status. Mirrors the GraphQL ``customizeVulnerabilities`` mutation. With ``all_vulnerabilities=True`` the update is applied to every vulne

• list_scans

  List scans for the authenticated organisation with optional filtering. The non-archived path reuses ``query_helper.query_scans`` (the GraphQL scan scoping: organisation, visibility and object-level a

• get_scan

  Get detailed information for a single scan by database id. Access is resolved through ``shared_access.access.get_scan_with_access`` so object-level access matches GraphQL. Archived scans are not serv

• get_scan_status

  Get a scan's progress state, start/end times and errors. Mirrors the GraphQL resolvers: ``state`` is the latest ``key="progress"`` value (``resolve_progress``), ``start_time`` is ``Scan.created_time`