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-23T14:34:12.806046+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.scholarfeed.org/mcp?src=mcp-registry",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-23T14:34:12.806046+00:00",
"registry_status": null,
"subject": {
"id": "io.github.ygao2005/scholar-feed-mcp",
"kind": "mcp"
},
"tools": {
"names": [
"add_to_collection",
"annotate_paper",
"ask_library",
"check_drift",
"check_watches",
"co_author_graph",
"create_collection",
"create_watch",
"delete_watch",
"embed_text",
"fetch_fulltext",
"find_author",
"find_gaps",
"get_citations",
"get_field_orientation",
"get_foundational_lineage",
"get_paper",
"like_paper",
"list_collections",
"list_library",
"list_watches",
"preview_watch",
"remove_from_collection",
"save_paper",
"search_papers",
"unsave_paper",
"update_watch"
],
"names_truncated": false,
"sha256": "2ac5cd4c8af6698dc6bc70e0937878ef0a8a0c0ba1fcc2f533d8eaabbb1b9213"
},
"tools_complete": true,
"tools_observed_at": "2026-10-23T14:34:12.806046+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