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-22T13:06:08.517520+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://api.temsor.com/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-22T13:06:08.517520+00:00",
"registry_status": null,
"subject": {
"id": "com.temsor/api",
"kind": "mcp"
},
"tools": {
"names": [
"email_verify",
"iban_validate",
"pbx_audio_chunk",
"pbx_calls",
"pbx_calls_get",
"pbx_calls_graph",
"pbx_dictionary",
"pbx_dictionary_add",
"pbx_events",
"pbx_facts",
"pbx_facts_get",
"pbx_index_partial",
"pbx_index_partial_get",
"pbx_ingest_transcript",
"pbx_persons",
"pbx_persons_get",
"pbx_promises",
"pbx_promises_act",
"pbx_promises_close",
"pbx_promises_export",
"pbx_promises_reopen",
"pbx_redact",
"pbx_redact_audit",
"pbx_register",
"pbx_search",
"pbx_status",
"pbx_webhooks",
"pbx_webhooks_deliveries",
"pbx_whisper_status",
"pbx_whisper_suggest",
"phone_validate",
"tr_address_parse",
"tr_business_days",
"tr_iban_olustur",
"tr_invoice_build",
"tr_invoice_parse",
"tr_labor",
"tr_money_to_words",
"tr_posta_kodu",
"tr_qr_odeme",
"tr_tebligat_clock",
"tr_validate",
"tr_vat"
],
"names_truncated": false,
"sha256": "6477f6a5cfbd4b9bdcd21e43ceecd20ef648ed08cc65d8f3e56d98989fa5bc69"
},
"tools_complete": true,
"tools_observed_at": "2026-10-22T13:06:08.517520+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