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-23T06:36:43.968199+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://app.bitroad.ai/api/v1/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-23T06:36:43.968199+00:00",
"registry_status": null,
"subject": {
"id": "ai.bitroad/bitroad",
"kind": "mcp"
},
"tools": {
"names": [
"addresses_create",
"addresses_list",
"auth_revoke_self",
"auth_whoami",
"catalog_describe_category",
"catalog_get_product",
"catalog_list_categories",
"catalog_search_products",
"disputes_add_evidence",
"disputes_file",
"disputes_get",
"disputes_list",
"disputes_respond",
"disputes_withdraw",
"envelopes_get",
"envelopes_list",
"orders_get",
"orders_list",
"payment_methods_create",
"payment_methods_list",
"platforms_get",
"purchase_cancel_intent",
"purchase_confirm_intent",
"purchase_create_intent",
"returns_get",
"returns_get_label",
"returns_initiate",
"returns_list",
"seller_accept_return",
"seller_archive_listing",
"seller_attach_tracking",
"seller_create_listing",
"seller_get_listing",
"seller_get_me",
"seller_get_order",
"seller_get_return",
"seller_list_listings",
"seller_list_orders",
"seller_list_returns",
"seller_list_reviews",
"seller_mark_delivered",
"seller_mark_shipped",
"seller_onboarding_status",
"seller_reject_return",
"seller_respond_to_review",
"seller_update_listing",
"seller_update_stock",
"sellers_get",
"services_accept_quote",
"services_acknowledge_delivery",
"services_counter_quote",
"services_create_listing",
"services_get_listing",
"services_get_quote",
"services_list_my_quotes",
"services_list_my_sales",
"services_list_open_requests",
"services_purchase",
"services_reject_quote",
"services_request_quote",
"services_search_listings",
"services_start_work",
"services_submit_deliverable",
"services_submit_quote",
"services_withdraw_quote"
],
"names_truncated": false,
"sha256": "7603928c2f607bec01fec899bcb6925bdabcef53ddb89eb713ea759e807afa9c"
},
"tools_complete": true,
"tools_observed_at": "2026-10-23T06:36:43.968199+00:00",
"version": "1.0.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