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-22T15:55:48.403586+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://sellag.vercel.app/api/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-22T15:55:48.403586+00:00",
"registry_status": null,
"subject": {
"id": "x402/sella",
"kind": "mcp"
},
"tools": {
"names": [
"browse_catalog",
"budget_status",
"business_assess",
"business_brief",
"business_draft",
"business_end",
"business_file_put",
"business_list",
"business_log",
"business_rate",
"business_request_funding",
"business_start",
"business_status",
"call_api",
"charge_create",
"charge_get",
"charge_list",
"charge_refund",
"compare",
"cradle_breed_agent",
"deliver_product",
"describe_catalog",
"distribution_log",
"distribution_set",
"explain_decision",
"get_activity",
"get_approval",
"get_dataset",
"get_job",
"get_listing",
"list_datasets",
"list_market_apis",
"merge_models",
"policy_check",
"policy_get",
"policy_set",
"purchase_preview",
"recommend",
"search_catalog",
"search_datasets",
"search_open_models",
"sella_auth_complete",
"sella_auth_start",
"sella_setup_claim",
"service_create",
"service_deliver",
"service_list",
"service_update",
"storefront_get",
"storefront_set",
"submit_feedback",
"try_dataset"
],
"names_truncated": false,
"sha256": "7611b4fc890d3b1c7b0b7956e9c6b67c2c5d4991770c4d6cad38ba12cf703717"
},
"tools_complete": true,
"tools_observed_at": "2026-10-22T15:55:48.403586+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