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-20T21:56:35.375577+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://pikasim.com/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-20T21:56:35.375577+00:00",
"registry_status": null,
"subject": {
"id": "com.pikasim/pikasim",
"kind": "mcp"
},
"tools": {
"names": [
"cancel_esim",
"cancel_sms_rental",
"cancel_sms_verification",
"check_balance",
"check_country_coverage",
"check_sms_verification",
"create_deposit",
"create_wallet",
"extend_sms_rental",
"fetch",
"get_esim_status",
"get_package_details",
"get_phone_plan_pricing",
"get_pricing",
"get_sms_rental_messages",
"get_sms_service_countries",
"get_topup_options",
"list_esims",
"list_orders",
"list_sms_orders",
"list_sms_rentals",
"list_transactions",
"order_sms_verification",
"purchase_esim",
"purchase_phone_plan",
"rent_sms_number",
"search",
"search_esim_packages",
"search_phone_plans",
"search_sms_services",
"topup_esim"
],
"names_truncated": false,
"sha256": "cc4910de28c4dc6d48474c66fdd4f9f4fae065d51654b63d1a046edcdb67b3ec"
},
"tools_complete": true,
"tools_observed_at": "2026-10-20T21:56:35.375577+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