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-22T13:51:05.706003+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.jobmojito.com/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-22T13:51:05.706003+00:00",
"registry_status": null,
"subject": {
"id": "com.jobmojito/jobmojito",
"kind": "mcp"
},
"tools": {
"names": [
"create_catalogue_directory",
"create_interview",
"create_interview_from_questions",
"create_persona",
"create_report",
"generate_interview_report",
"generate_interview_url",
"get_catalogue_directory",
"get_documentation",
"get_interview_definition",
"get_interview_result_details",
"get_merchant_analytics",
"get_merchant_credit_usage",
"get_merchant_status",
"get_report",
"jobmojito_configuration",
"list_avatars",
"list_candidates",
"list_catalogue_directories",
"list_interview_results",
"list_interviews",
"list_languages",
"list_my_merchants",
"list_report_fields",
"list_reports",
"list_sub_merchants",
"preview_report",
"register_users_for_interview",
"report_technical_issue",
"request_another_interview_attempt",
"run_report",
"search_documentation",
"set_interview_state",
"submit_feature_request",
"update_catalogue_directory",
"update_interview",
"update_report",
"upload_knowledge_base_document"
],
"names_truncated": false,
"sha256": "0f501f1d5c8eb0ffb98e3f6761dbbd3ab97879ffc96c77e0375b9410f66976f9"
},
"tools_complete": true,
"tools_observed_at": "2026-10-22T13:51:05.706003+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