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-30T15:34:39.980111+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://mcp.luxalgo.com/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-30T15:34:39.980111+00:00",
"registry_status": null,
"subject": {
"id": "io.github.luxalgo/luxalgo-mcp-server",
"kind": "mcp"
},
"tools": {
"names": [
"edge_presets",
"edge_report",
"edge_symbols",
"journal_add_trade",
"journal_breakdown",
"journal_calendar",
"journal_get_day",
"journal_get_trade",
"journal_list_accounts",
"journal_list_tags",
"journal_list_trades",
"journal_overview",
"journal_search_notes",
"journal_update_note",
"journal_update_trade",
"journal_write_note",
"library_get_concept",
"library_get_family",
"library_get_indicator",
"library_get_source_code",
"library_list_concepts",
"library_list_families",
"library_list_indicators",
"library_search",
"luxalgo_account",
"propfirms_challenge_rules",
"propfirms_compare",
"propfirms_get",
"propfirms_list_simulatable",
"propfirms_optimal_risk",
"propfirms_pass_rates",
"propfirms_search",
"propfirms_search_challenges",
"propfirms_search_offers",
"propfirms_simulate",
"propfirms_simulate_trades",
"propfirms_validate_strategy",
"trackers_datasets",
"trackers_latest",
"trackers_query",
"trackers_ticker"
],
"names_truncated": false,
"sha256": "80cfbac5f7a45ed306a50dccd786f1a3d210c4148980f0546dd32e6bcb3182db"
},
"tools_complete": true,
"tools_observed_at": "2026-10-30T15:34:39.980111+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