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-22T06:41:23.733600+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.seekrit.dev/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-22T06:41:23.733600+00:00",
"registry_status": null,
"subject": {
"id": "dev.seekrit/remote-mcp",
"kind": "mcp"
},
"tools": {
"names": [
"audit",
"billing",
"compose_group",
"create_app",
"create_group",
"delete_app",
"delete_branch",
"delete_env",
"delete_group",
"delete_secret",
"get_started",
"invite_member",
"kms_disable_key",
"kms_list_keys",
"kms_revoke_grant",
"list_apps",
"list_branches",
"list_env_groups",
"list_envs",
"list_group_envs",
"list_groups",
"list_invites",
"list_lease_targets",
"list_leases",
"list_members",
"list_orgs",
"list_secret_versions",
"list_secrets",
"list_tokens",
"local_tool_for",
"rename_app",
"rename_group",
"restore_secret",
"revoke_invite",
"revoke_lease",
"revoke_token",
"setup_local_crypto",
"signup",
"uncompose_group",
"whoami"
],
"names_truncated": false,
"sha256": "0678d7736a948169aca42546044e9518575a3d076fa620fc7675421b1027bb5a"
},
"tools_complete": true,
"tools_observed_at": "2026-10-22T06:41:23.733600+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