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:32:17.793650+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://programmes.net/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-21T07:32:17.793650+00:00",
"registry_status": null,
"subject": {
"id": "net.programmes/developer-tools",
"kind": "mcp"
},
"tools": {
"names": [
"ascii",
"aspect-ratio",
"base-n",
"base64",
"bcrypt",
"case",
"char-inspector",
"chmod",
"cidr",
"color",
"color-palette",
"compress",
"contrast",
"cron",
"csp",
"css-minify",
"css-units",
"curl-converter",
"data-size",
"date-calc",
"diff",
"docker-compose",
"duration",
"env-json",
"gitignore",
"glob-tester",
"hash",
"hmac",
"html",
"html-entity",
"html-jsx",
"html-markdown",
"http-status",
"id-decoder",
"ieee754",
"image-base64",
"ipv6",
"json",
"json-csv",
"json-diff",
"json-schema",
"json-schema-validator",
"json-ts",
"json-xml",
"jsonc",
"jsonpath",
"jwt",
"jwt-encode",
"key-inspector",
"lorem",
"luhn",
"markdown",
"markdown-table",
"mime",
"morse-code",
"nanoid",
"number-base",
"password",
"password-strength",
"punycode",
"random",
"regex",
"robots-txt",
"roman-numeral",
"saml-decoder",
"security-headers",
"semver",
"slugify",
"sort-lines",
"sql",
"string-escape",
"svg-data-uri",
"text-cleanup",
"timestamp",
"toml-json",
"totp",
"ulid",
"url",
"url-encode",
"user-agent",
"utm",
"uuid",
"wifi-qr",
"word-count",
"x509",
"xml",
"yaml-json"
],
"names_truncated": false,
"sha256": "496f059db83af88281174735963604d0f0a78d6e4bca3a9a3c6174263fa1cf77"
},
"tools_complete": false,
"tools_observed_at": "2026-10-21T07:32:17.793650+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