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-20T21:25:29.018613+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.lightbringer.com/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-20T21:25:29.018613+00:00",
"registry_status": null,
"subject": {
"id": "com.lightbringer/connector",
"kind": "mcp"
},
"tools": {
"names": [
"add_comment",
"add_discussion_comment",
"create_asset",
"create_strategy",
"delete_asset",
"delete_strategy",
"delete_task",
"edit_strategy",
"fetch",
"get_company_context",
"get_company_context_template",
"get_innovation",
"get_innovation_template",
"get_review",
"get_strategy",
"get_strategy_template",
"get_task_status",
"import_patent",
"list_innovations",
"list_reviews",
"list_strategies",
"list_tasks",
"refresh_patent_family",
"register_innovation",
"reply_to_comment",
"request_patent_preparation",
"respond_to_review",
"search",
"search_public_patents",
"send_developer_feedback",
"set_strategy_publication",
"start_innovation_feedback",
"update_asset",
"update_company_context",
"update_innovation",
"whoami"
],
"names_truncated": false,
"sha256": "52f519620eeb12d83bbeddee3c2cb759519b30fb26e9597cdfcaf532c7b1242c"
},
"tools_complete": true,
"tools_observed_at": "2026-10-20T21:25:29.018613+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