For teams using external agents and MCP servers: inspect measured evidence, watch changes, and keep a record of what your team accepted. Unknown evidence stays explicit.
Have a client configuration? Extract and check its public endpoints locally. Maintaining integrations for clients? Explore the agency pilot.
Runtime observation: 2026-10-21T00:40:10.327576+00:00 · State: live
Watch availability, tools and parameter schemas, authentication access, endpoint changes and lifecycle notices. Only complete observed schemas are compared. OAuth scope and consent-screen changes are not currently measured.
Sign in to watch this MCP serverSign-in required. Agent and MCP watches share the existing Free / Pro / Enterprise budget. Manage watches.
{
"auth": "anonymous",
"availability": "live",
"endpoint": "https://agentaegis-mcp-production.up.railway.app/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-21T00:40:10.327576+00:00",
"registry_status": null,
"subject": {
"id": "io.github.astafford8488/agentaegis",
"kind": "mcp"
},
"tools": {
"names": [
"access_review",
"account_balance",
"agent_history",
"agent_scan_get",
"agent_whoami",
"audit_report_generate",
"compliance_framework_check",
"control_gap_analysis",
"credential_check",
"cve_lookup",
"dependency_audit",
"dns_security_check",
"email_security_audit",
"evidence_collect",
"help",
"incident_triage",
"mfa_audit",
"policy_generate",
"sast_scan",
"scan_mcp_plugin",
"scan_skill",
"secret_scan",
"ssl_tls_audit",
"threat_intel_lookup",
"vet_endpoint",
"vuln_prioritize",
"vuln_scan_network",
"vuln_scan_web_app"
],
"names_truncated": false,
"sha256": "51c7da112fb23ed245e248b43b82ccd20df1a2978ed4350bb12c9a4aa04ce4c7"
},
"tools_complete": true,
"tools_observed_at": "2026-10-21T00:40:10.327576+00:00",
"version": null
}Keep an accepted snapshot in agents.lock.json. CI compares it with current evidence and returns allow, review or block with reasons, before/after data and policy hashes.
Default gaps require review. Configure stricter handling explicitly. A lock records your acceptance; it is not a supplier attestation.
API referenceVerified domain owners can publish up to five exact-match sandbox fixtures and opt in to a test run. Results include fixture version, latency, output hashes and comparable regressions. Cost remains unknown when unobserved.
Run with POST /api/v1/dependencies/task-checks?domain=… while signed in. Read the schema and example in the integration guide.
Domain control, a declared business identifier and an active name-matched company record are separate evidence. Zero verified records means zero recorded proof.
Current coverage and measurement date · Verify your domainVerify issuer signatures, subject and credential freshness using the public key document. Keep its task evidence categories separate from Agenstry measurements.
A valid SEAL does not establish domain ownership, legal identity, key possession or execution permission.
Credential verification API · Issuer documentationSmithery endpoint migration · Agent monitoring · Methodology