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-22T00:26:57.663045+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://courseprofiler.com/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-22T00:26:57.663045+00:00",
"registry_status": null,
"subject": {
"id": "com.courseprofiler/courseprofiler",
"kind": "mcp"
},
"tools": {
"names": [
"analyze_activity",
"assess_finish_time_goal",
"build_runner_profile_from_strava",
"compare_execution",
"compare_pacing_strategies",
"create_race_plan",
"enrich_course_waypoints",
"export_race_plan_pdf",
"generate_course_segments",
"generate_runner_profile",
"get_activity_submission",
"get_artifact",
"get_artifact_upload_requirements",
"get_course_submission_requirements",
"get_job",
"get_race_plan_requirements",
"get_runner_profile_requirements",
"get_storage_readiness",
"import_course",
"import_profile_attachment",
"inspect_analysis",
"inspect_runner_profile",
"search_race_catalog",
"submit_course",
"validate_course_profile",
"validate_runner_profile"
],
"names_truncated": false,
"sha256": "615ccbd6a8d97386a907b13c31374e4c9e26253d99877e7a8540d85fda043b2c"
},
"tools_complete": true,
"tools_observed_at": "2026-10-22T00:26:57.663045+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