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-21T07:31:50.641923+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://postari.io/api/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-21T07:31:50.641923+00:00",
"registry_status": null,
"subject": {
"id": "io.github.wilmendezofficial/postari",
"kind": "mcp"
},
"tools": {
"names": [
"account_stats",
"activate_flow",
"add_subscriber_to_list",
"arm_flow",
"clean_bounced_subscribers",
"create_flow",
"create_form",
"create_landing",
"create_launch",
"create_list",
"create_segment",
"create_subscriber",
"create_tag",
"create_template",
"diagnose_deliverability",
"get_agent_activity",
"get_campaign_audience",
"get_campaign_stats",
"get_form",
"get_launch",
"get_subscriber",
"launch_campaign",
"link_campaign_to_launch_stage",
"list_campaigns",
"list_flow_emails",
"list_forms",
"list_landings",
"list_launches",
"list_lists",
"list_subscribers",
"reactivate_bounced_subscriber",
"send_transactional_email",
"set_campaign_audience",
"tag_subscribers",
"test_flow",
"trigger_flow",
"update_flow",
"update_flow_email",
"update_form",
"update_landing",
"update_subscriber"
],
"names_truncated": false,
"sha256": "10281daa34d4d4a111776eb7a513b0ccf5dedb03f64f327ec77a39c7a45bc549"
},
"tools_complete": true,
"tools_observed_at": "2026-10-21T07:31:50.641923+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