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-20T19:56:29.584894+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://mcp.socialdatax.com/weibo/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-20T19:56:29.584894+00:00",
"registry_status": null,
"subject": {
"id": "com.52choujiang/weibo-insights",
"kind": "mcp"
},
"tools": {
"names": [
"socialdatax_get_points_balance",
"weibo_get_hot_search_list",
"weibo_get_post_comment_replies_by_comment_id",
"weibo_get_post_comments_by_post_id",
"weibo_get_post_comments_by_post_url",
"weibo_get_post_detail_by_post_id",
"weibo_get_post_detail_by_post_url",
"weibo_get_post_liker_list_by_post_id",
"weibo_get_post_liker_list_by_post_url",
"weibo_get_post_repost_list_by_post_id",
"weibo_get_post_repost_list_by_post_url",
"weibo_get_user_info_by_profile_url",
"weibo_get_user_info_by_user_id",
"weibo_get_user_posts_by_profile_url",
"weibo_get_user_posts_by_user_id",
"weibo_get_video_speech_text_job",
"weibo_search_posts",
"weibo_search_suggestions",
"weibo_search_user_suggestions",
"weibo_search_users",
"weibo_submit_video_speech_text_by_post_id",
"weibo_submit_video_speech_text_by_post_url"
],
"names_truncated": false,
"sha256": "917c1f085b9aa25f6cd16af768006550fb5f45fbe7ae9e2683d7d068a3d47326"
},
"tools_complete": true,
"tools_observed_at": "2026-10-20T19:56:29.584894+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