CloudSignals API And MCP
Use the CloudSignals API and MCP server to integrate tenant findings, assets, scans, compliance, and RiskOps workflows into customer systems.
| Production app | https://cloudsignals.aivric.com |
|---|---|
| Production API | https://cloudsignals.aivric.com/api/v1 |
| OpenAPI schema | https://cloudsignals.aivric.com/api/v1/schema |
| ReDoc | https://cloudsignals.aivric.com/api/v1/docs |
| Hosted MCP | https://cloudsignals.aivric.com/mcp |
| Interim dev API | https://dev-defense.aivric.com/api/v1 |
Endpoint Groups
- Authentication and token endpoints for interactive sessions and service JWTs.
- Tenant API keys for automation credentials that are visible once and revocable.
- Providers, provider groups, scans, schedules, tasks, resources, findings, and compliance summaries.
- RiskOps objects such as owners, accepted risk, exception requests, audit history, and treatment state where enabled for the tenant.
- Integrations, exports, notification hooks, processor configuration, and third-party delivery workflows.
Compatibility Hosts
- https://gcp-dev-defense.aivric.com preserves development customer and internal compatibility paths.
- https://gcp-defense.aivric.com preserves GCP production compatibility paths.
- https://dev-defense.aivric.com remains the interim development CloudSignals endpoint until a dev CloudSignals hostname is provisioned.
- https://defense.aivric.com preserves production Defense compatibility paths during migration.