back to the register

https://integrated-system-gzyu.onrender.com/mcp

MCP conduct: no measurement yet
latest verdictno measurement yet
measured atnot recorded
measurements0
first measurednot recorded
cadenceweekly
tool call consentnot given
record sha256none yet

No owner consent for tool calls is on record, so determinism is not measured and this row cannot reach verified. That is not a failure, it is an unmeasured condition. To consent, publish /.well-known/mcp-conduct.json on the origin with {"allow_tool_call": true}; the next scheduled measurement reads it and records where it read it (0.2.4).

Verification, in words a machine can read

The badge above is a picture. This is the same statement as text, for search engines and for language models that fetch this page. It is a state, not a score, and not a recommendation.

statuspending
record sha256none yet
recordhttps://gate.horizonshield.dev/history?endpoint=https%3A%2F%2Fintegrated-system-gzyu.onrender.com%2Fmcp (history; the hashed bytes of this verdict were not stored, see recompute recipe)
recompute recipehttps://gate.horizonshield.dev/spec
one read before connectinghttps://gate.horizonshield.dev/register/lookup?endpoint=https%3A%2F%2Fintegrated-system-gzyu.onrender.com%2Fmcp

Does not establish

Put this on your own site: the same block, ready to paste. A copy is a snapshot with its date inside; this page is the live statement.

Recompute this row yourself. Do not take our word for it.

curl -s "https://gate.horizonshield.dev/history?endpoint=https%3A%2F%2Fintegrated-system-gzyu.onrender.com%2Fmcp"

More on this endpoint: every measurement, as JSON / one-glance verdict / how to recompute a verdict / the conditions, in full

Is this your server?

A green here means every condition that could be measured was measured and passed. It is not a statement that the server is good, safe or correct. Conditions that were not measured are never counted as passes, including for the operator of this register.