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-30T11:38:49.304586+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://anatome.dev/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-30T11:38:49.304586+00:00",
"registry_status": null,
"subject": {
"id": "dev.anatome/anatome",
"kind": "mcp"
},
"tools": {
"names": [
"ai_meal_plan",
"ai_parse_meal",
"ai_photo_macros",
"ai_workout_plan",
"delete_meal",
"delete_workout",
"export_data",
"generate_muscle_image",
"get_body_metrics",
"get_cardio_activities",
"get_events",
"get_exercise",
"get_meals",
"get_muscle_recovery",
"get_nutrition_daily",
"get_profile",
"get_progress",
"get_routine",
"get_water",
"get_workouts",
"instantiate_routine",
"list_muscles",
"list_routines",
"log_body_metric",
"log_cardio",
"log_meal",
"log_water",
"log_workout",
"lookup_barcode",
"my_training_context",
"resolve_exercise",
"search_exercises",
"search_foods",
"update_meal",
"update_sets",
"upsert_profile"
],
"names_truncated": false,
"sha256": "6b28620bf8b68dd42c76e4ba4d700e7a2ebb669ad5530b4b3a735742cb6a580a"
},
"tools_complete": true,
"tools_observed_at": "2026-10-30T11:38:49.304586+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