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-21T06:27:33.495086+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://qiniso.qinisolabs.workers.dev/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-21T06:27:33.495086+00:00",
"registry_status": null,
"subject": {
"id": "io.github.qinisolabs/qiniso",
"kind": "mcp"
},
"tools": {
"names": [
"format_currency",
"is_holiday",
"next_holiday",
"parse_address",
"parse_date",
"tax_rate",
"validate_aadhaar",
"validate_be_nrn",
"validate_bg_egn",
"validate_bsn",
"validate_btc_address",
"validate_card",
"validate_ch_ahv",
"validate_china_ric",
"validate_cnpj",
"validate_codice_fiscale",
"validate_cpf",
"validate_cusip",
"validate_cz_rc",
"validate_de_steuer_id",
"validate_dni",
"validate_domain",
"validate_ee_isikukood",
"validate_email",
"validate_eth_address",
"validate_fodselsnummer",
"validate_fr_nir",
"validate_gln",
"validate_gtin",
"validate_hetu",
"validate_hr_oib",
"validate_iban",
"validate_imei",
"validate_ip",
"validate_isbn",
"validate_isbn10",
"validate_isin",
"validate_issn",
"validate_lei",
"validate_mx_curp",
"validate_nif_pt",
"validate_orcid",
"validate_personnummer",
"validate_pesel",
"validate_phone",
"validate_ro_cnp",
"validate_routing",
"validate_sa_id",
"validate_sedol",
"validate_sscc",
"validate_tckn",
"validate_tld",
"validate_url",
"validate_uuid",
"validate_vat",
"validate_vin"
],
"names_truncated": false,
"sha256": "2c6113a1fa0315841a978ebececf17e4da64567342aba77c4c09c3ad4cd0ce50"
},
"tools_complete": true,
"tools_observed_at": "2026-10-21T06:27:33.495086+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