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-20T23:36:49.518605+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://latex-tools.online/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-20T23:36:49.518605+00:00",
"registry_status": null,
"subject": {
"id": "io.github.mcpservings/paper-mcp",
"kind": "mcp"
},
"tools": {
"names": [
"autocomplete_papers",
"extract_pdf",
"extract_pdf_result",
"get_author",
"get_author_papers",
"get_authors_batch",
"get_dataset_diffs",
"get_dataset_download_links",
"get_dataset_release",
"get_openalex_citations",
"get_openalex_references",
"get_openalex_trends",
"get_openalex_work",
"get_paper",
"get_paper_authors",
"get_paper_citations",
"get_paper_references",
"get_papers_batch",
"lint_latex",
"list_categories",
"list_dataset_releases",
"list_ocr_models",
"list_openalex_topics",
"list_paper_sources",
"list_recent",
"match_paper_title",
"read_paper",
"recognize_formula",
"recognize_table",
"recommend_papers_for_paper",
"recommend_papers_from_examples",
"search_all",
"search_authors",
"search_by_author",
"search_medical",
"search_openalex_authors",
"search_openalex_institutions",
"search_openalex_works",
"search_papers",
"search_papers_bulk",
"search_snippets"
],
"names_truncated": false,
"sha256": "3223cb697e3c620041a271a350e37fa153463e8b1be1ef2b7d8419105b64463e"
},
"tools_complete": true,
"tools_observed_at": "2026-10-20T23:36:49.518605+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