Auditon security assessments
Read-only access to your Auditon vulnerability scans: findings, endpoints, reports and changes.
¿Debería usar esto?
Calidad y seguridad
Basado en el análisis automatizado de las definiciones de herramientas y el cumplimiento del protocolo.
Costo de contexto
Este es el número aproximado de tokens que se consumen cada vez que las herramientas del servidor se cargan en el contexto de un modelo. Los recuentos más altos reducen la atención disponible para otras tareas.
Instalar
Instalación con un clic
Agrega esto a tu archivo `claude_desktop_config.json`:
{
"mcpServers": {
"assessments": {
"url": "https://auditon.co/mcp"
}
}
}Puntos de conexión remotos
https://auditon.co/mcpstreamable-httpQué puede hacer
Inventario de herramientas
Herramientas (6)
🟢list_endpoints
Hosts assessed in this workspace, with open findings by severity and the most recent scan. Start here.
Esquema de entrada
{
"type": "object",
"additionalProperties": false
}🟢list_scans(endpoint, limit)
Scans, newest first: type, status, rating and coverage. With an endpoint, rating, findings and coverage are for that endpoint only.
Esquema de entrada
{
"type": "object",
"properties": {
"endpoint": {
"type": "string",
"description": "Endpoint hostname or IP, as returned by list_endpoints"
},
"limit": {
"type": "integer",
"minimum": 1,
"maximum": 100,
"default": 20
}
},
"additionalProperties": false
}🟢get_report(scan_id, endpoint, detail)
One scan as structured data: rating, coverage gaps, findings, items requiring verification, accepted risks, dismissed false positives and passed controls. Read "interpretation" before drawing conclusions. Set detail=true for descriptions and remediation.
Esquema de entrada
{
"type": "object",
"properties": {
"scan_id": {
"type": "string",
"description": "scan_id (or source_id) as returned by list_scans"
},
"endpoint": {
"type": "string",
"description": "Limit the report to one endpoint"
},
"detail": {
"type": "boolean",
"default": false,
"description": "Include description, impact, remediation, references and evidence for each finding"
}
},
"required": [
"scan_id"
],
"additionalProperties": false
}🟢list_findings(state, min_severity, endpoint, since, limit)
Current findings across all scans, most severe first. Defaults to open findings; potential (unconfirmed) matches are included and marked by assurance.
Esquema de entrada
{
"type": "object",
"properties": {
"state": {
"type": "string",
"enum": [
"open",
"resolved",
"all"
],
"default": "open"
},
"min_severity": {
"type": "string",
"enum": [
"Critical",
"High",
"Medium",
"Low",
"Info"
],
"default": "Info",
"description": "Lowest severity to include"
},
"endpoint": {
"type": "string",
"description": "Endpoint hostname or IP, as returned by list_endpoints"
},
"since": {
"type": "string",
"description": "Only findings last observed on or after this date (YYYY-MM-DD)"
},
"limit": {
"type": "integer",
"minimum": 1,
"maximum": 500,
"default": 100
}
},
"additionalProperties": false
}🟢get_finding(finding_id)
Full detail for one finding: description, impact, remediation, references, evidence, analyst decision and its history across scans.
Esquema de entrada
{
"type": "object",
"properties": {
"finding_id": {
"type": "string",
"description": "finding_id from list_findings or get_report"
}
},
"required": [
"finding_id"
],
"additionalProperties": false
}🟢compare_scans(endpoint, from_scan, to_scan)
What changed on an endpoint between two scans: appeared, resolved, not reassessed (the check did not complete, so status is unknown) and severity changes. Without scan ids, compares the endpoint's two most recent scans.
Esquema de entrada
{
"type": "object",
"properties": {
"endpoint": {
"type": "string",
"description": "Endpoint hostname or IP, as returned by list_endpoints"
},
"from_scan": {
"type": "string",
"description": "Earlier scan"
},
"to_scan": {
"type": "string",
"description": "Later scan"
}
},
"required": [
"endpoint"
],
"additionalProperties": false
}Comunidad
Evidencia