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-20T19:56:20.590591+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.atlarium.bio/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-20T19:56:20.590591+00:00",
"registry_status": null,
"subject": {
"id": "bio.atlarium/habitat-database",
"kind": "mcp"
},
"tools": {
"names": [
"calculate_equipment_requirements",
"calculate_fertilizer_dose",
"calculate_nutrient_gaps",
"calculate_tank_volume",
"calculate_tank_weight",
"calculate_water_change",
"calculate_water_chemistry",
"calculate_weekly_dose_totals",
"check_species_compatibility",
"convert_units",
"generate_fertilization_plan",
"get_algae_profile",
"get_disease_profile",
"get_equipment_profile",
"get_fertilization_regime",
"get_fertilizer_profile",
"get_fish_profile",
"get_guide",
"get_medicine_profile",
"get_plant_problem_profile",
"get_plant_profile",
"get_product_profile",
"get_water_parameters",
"list_product_brands",
"list_product_categories",
"match_diagnostic_profiles",
"search_algae",
"search_diseases",
"search_equipment",
"search_fertilization_regimes",
"search_fertilizers",
"search_fish",
"search_guides",
"search_medicines",
"search_plant_problems",
"search_plants",
"search_products",
"suggest_habitat_for_tank",
"suggest_species_for_tank"
],
"names_truncated": false,
"sha256": "af935446fe4cf29224c4a0108e630ca2d1c074c33390d9f350b0ca5c2234af91"
},
"tools_complete": true,
"tools_observed_at": "2026-10-20T19:56:20.590591+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