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-30T10:07:05.669536+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.jojapi.com/twitter",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-30T10:07:05.669536+00:00",
"registry_status": null,
"subject": {
"id": "com.jojapi/twitter",
"kind": "mcp"
},
"tools": {
"names": [
"get_AutoComplete",
"get_Search",
"get_ShortUrl",
"get_email_search_by_username",
"get_v1_1_Followers",
"get_v1_1_FollowersIds",
"get_v1_1_Following",
"get_v1_1_FollowingIds",
"get_v1_1_Hashflags",
"get_v1_1_Locations",
"get_v1_1_TranslateProfile",
"get_v1_1_TranslateTweet",
"get_v1_1_Trends",
"get_v1_1_Users",
"get_v2_Favoriters",
"get_v2_Followers",
"get_v2_Following",
"get_v2_Likes",
"get_v2_ListTimeline",
"get_v2_Retweeters",
"get_v2_Subscriptions",
"get_v2_Tweet",
"get_v2_TweetDetail",
"get_v2_UserAffiliates",
"get_v2_UserByRestId",
"get_v2_UserByScreenName",
"get_v2_UserHighlights",
"get_v2_UserMedia",
"get_v2_UserTweets",
"get_v2_UserTweetsAndReplies",
"get_v2_UsersByRestIds",
"get_v2_VerifiedFollowers"
],
"names_truncated": false,
"sha256": "ab2d8af39abd06a46c3f2911796a246b3c570741d05c29e7460c30203c7bfd78"
},
"tools_complete": true,
"tools_observed_at": "2026-10-30T10:07:05.669536+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