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-11-01T07:47:19.495360+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://brapi.caseyjhand.com/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-11-01T07:47:19.495360+00:00",
"registry_status": null,
"subject": {
"id": "io.github.cyanheads/brapi-mcp-server",
"kind": "mcp"
},
"tools": {
"names": [
"brapi_build_phenotype_matrix",
"brapi_connect",
"brapi_dataframe_describe",
"brapi_dataframe_query",
"brapi_describe_filters",
"brapi_export_genotype_matrix",
"brapi_find_genotype_calls",
"brapi_find_germplasm",
"brapi_find_images",
"brapi_find_locations",
"brapi_find_observations",
"brapi_find_studies",
"brapi_find_variables",
"brapi_find_variants",
"brapi_germplasm_performance",
"brapi_get_germplasm",
"brapi_get_image",
"brapi_get_study",
"brapi_raw_get",
"brapi_raw_search",
"brapi_server_info",
"brapi_walk_pedigree"
],
"names_truncated": false,
"sha256": "653c47ede421f0b725adc5bca2b993c734cb13fe7a82f6adffe17ea2869eb3dd"
},
"tools_complete": true,
"tools_observed_at": "2026-11-01T07:47:19.495360+00:00",
"version": "0.5.0"
}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