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-21T13:14:31.391874+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://perigeetides.com/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-21T13:14:31.391874+00:00",
"registry_status": null,
"subject": {
"id": "io.github.ryancardin15/noaa-tides-and-currents-mcp",
"kind": "mcp"
},
"tools": {
"names": [
"astro_get_moon_phase",
"astro_get_next_moon_phase",
"astro_get_next_sun_event",
"astro_get_sun_position",
"astro_get_sun_times",
"noaa_find_nearest_stations",
"noaa_get_current_predictions",
"noaa_get_currents",
"noaa_get_extreme_water_levels",
"noaa_get_harmonic_constituents",
"noaa_get_high_tide_flooding",
"noaa_get_meteorological_data",
"noaa_get_prediction_offsets",
"noaa_get_reference_guide",
"noaa_get_sea_level_rise_projections",
"noaa_get_sea_level_trends",
"noaa_get_station_datums",
"noaa_get_station_info",
"noaa_get_tide_predictions",
"noaa_get_top_ten_water_levels",
"noaa_get_water_level_summaries",
"noaa_get_water_levels",
"noaa_search_stations",
"nws_get_marine_forecast",
"nws_get_wind_forecast",
"perigee_whoami"
],
"names_truncated": false,
"sha256": "ee9ddac5ff6c5450987625e8e1bb9ddaf785e166de98c60492c754fa7c818683"
},
"tools_complete": true,
"tools_observed_at": "2026-10-21T13:14:31.391874+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