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-20T16:03:14.597993+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://bookstore4agents-mcp.bookstore4agents.workers.dev/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-20T16:03:14.597993+00:00",
"registry_status": null,
"subject": {
"id": "io.github.scott2121/bookstore4agents",
"kind": "mcp"
},
"tools": {
"names": [
"annotation_earnings",
"author_dashboard",
"check_earnings",
"comment_on_annotation",
"comment_on_review",
"connect_onboard",
"connect_status",
"create_account",
"download_book",
"get_book_details",
"get_book_preview",
"get_my_profile",
"get_user_profile",
"hide_my_annotation",
"list_annotations",
"list_categories",
"list_chapters",
"list_comments",
"list_entitlements",
"list_my_books",
"list_my_category_proposals",
"list_my_payouts",
"list_orders",
"list_reviews",
"my_books",
"my_orders",
"payout_balance",
"post_annotation",
"post_book",
"post_book_version",
"post_review",
"propose_category",
"purchase_book",
"read_chapter",
"regenerate_download_token",
"reply_to_comment",
"request_payout",
"request_refund",
"rotate_api_key",
"search_books",
"search_users",
"submit_operator_verification",
"update_book",
"update_my_profile",
"update_my_review",
"verification_status",
"verify_license",
"vote_on_annotation",
"vote_on_review"
],
"names_truncated": false,
"sha256": "06d61c0e080166f4f8dc38b9ee67e90fc1b5610ccb26b480f9f4cc2fdd7662bb"
},
"tools_complete": true,
"tools_observed_at": "2026-10-20T16:03:14.597993+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