Claude Miggo connectorWhat Claude can do in your Miggo account.

Searches the services running in your Miggo environment, by name or technology, to build an inventory of microservices or scope a risk review.

Fetches one service by its ID with its details, dependencies and risk score, so Claude can drill into a single component.

Returns how many services match a set of filters, a quick figure rather than a list. Miggo's example is asking how many Java services the company runs.

Gives the possible field values for service filters, so Claude learns which options exist before it builds a search.

Looks for API endpoints across your environment, by route pattern, HTTP method or exposure, to find what is reachable from outside. Like the other list tools, it returns at most 50 endpoints per API call, riskiest first by default, so Claude may page through the rest.

Pulls up one endpoint by ID with its owning service, exposure level and associated findings, the detail behind a single route. It needs the ID of one record, the kind endpoints_search returns.

Tells you how many endpoints match given filters. Miggo frames it with a question like how many public endpoints you expose. The answer is a number, not records: the matching endpoints themselves come from endpoints_search.

Lists the values available for endpoint filters, such as HTTP methods, services or exposure types, before Claude narrows a query. It returns filter options rather than endpoints; endpoints_search then uses them.

Searches the third-party integrations your services talk to, to audit external dependencies and data flows leaving your environment. Like the other list tools, it returns at most 50 third-party integrations per API call, riskiest first by default, so Claude may page through the rest.

Fetches one third-party integration by ID and shows which of your services connect to that external provider. It needs the ID of one record, the kind third_parties_search returns.

Counts the third-party integrations that match filters, the quick answer to how many external services the company depends on. The answer is a number, not records: the matching third-party integrations themselves come from third_parties_search.

Returns possible values for third-party filters, revealing the known providers and integration types before Claude searches. It returns filter options rather than third-party integrations; third_parties_search then uses them.

Searches security findings, including posture issues, configuration drift and incidents, the core material for a risk assessment or compliance review. Like the other list tools, it returns at most 50 findings per API call, riskiest first by default, so Claude may page through the rest.

Brings back the full detail of one finding by ID, including the affected services and the remediation context Miggo holds. It needs the ID of one record, the kind findings_search returns.

Totals the findings that match filters. Miggo's own framing is the executive summary, for instance how many critical findings are open. The answer is a number, not records: the matching findings themselves come from findings_search.

Lists the severity levels, finding types and statuses available as filters, so Claude queries findings with the right vocabulary. It returns filter options rather than findings; findings_search then uses them.

Searches known vulnerabilities across your services, to check exposure to a specific CVE or rank patching work by severity.

Pulls one vulnerability by ID and shows which services and dependencies it affects, the link between a CVE and your own code. It needs the ID of one record, the kind vulnerabilities_search returns.

Gives the number of vulnerabilities matching filters, for example how many critical CVEs remain unpatched across the estate. The answer is a number, not records: the matching vulnerabilities themselves come from vulnerabilities_search.

Shows the severity levels, statuses and affected packages available as vulnerability filters, ahead of a precise search. It returns filter options rather than vulnerabilities; vulnerabilities_search then uses them.

Searches the software dependencies used by your services, for supply-chain audits, license reviews or finding who uses a given package. Like the other list tools, it returns at most 50 dependencies per API call, riskiest first by default, so Claude may page through the rest.

Retrieves a single dependency by ID with its version, its vulnerabilities and the services relying on it. It needs the ID of one record, the kind dependencies_search returns.

Counts the dependencies matching filters, such as how many vulnerable packages sit in your services right now. The answer is a number, not records: the matching dependencies themselves come from dependencies_search.

Lists package ecosystems, vulnerability statuses and versions in use as filter options, so Claude can slice the dependency data precisely. It returns filter options rather than dependencies; dependencies_search then uses them.

Returns metadata about the authenticated project, confirming which Miggo environment Claude is connected to and its project-level settings. Its answer reflects the project tied to the API token entered at setup.