Skip to main content

​
Official sources

Use the EvalGate developer hub as the first-party starting point. The official EvalGate Skills repository links back to that hub and contains the portable Skill collection and MCP configuration.
Install the complete collection. Read the coding-agent guide for its experimental support boundary. Skill instructions do not grant credentials or authorize a release. The package registries can have different published versions. Consult feature status before using source-only commands.

​
Connect the right MCP server

https://www.evalgate.com/api/mcp/docs provides public, read-only documentation. https://www.evalgate.com/api/mcp provides public protocol/schema discovery; product tool execution requires organization-scoped credentials. Follow the MCP integration guide for transport and authentication. The current tool contract uses consistent dotted names such as docs.list, docs.search, and docs.get. Retrieve tools/list for the actual input schemas; docs.list accepts an empty object because it has no parameters. Do not rename wire tool names to match a scanner’s preferred naming style. Find the official product server on Smithery: evalgate/evalgate. The listing links back to EvalGate’s developer hub and documents scoped authentication. Smithery discovered all eight product tools at publication. Publication does not establish verified-publisher status or authenticated client compatibility. An Agent Skills repository remains a separate distribution; Glama, mcp.so, and ChatGPT app listings are not claimed. Same-name projects under other publishers are not ownership evidence.

​
Test without granting production access

Use the public documentation MCP to try a real remote endpoint without an account or customer data. For application evaluation, follow the deterministic local path in the quickstart, respecting its source-versus-published package boundary. Local evaluation is not a hosted API sandbox. Hosted product calls require a scoped credential and operate on the selected organization.

​
Verification boundaries

WebMCP uses document.modelContext when the browser provides it, with navigator.modelContext as a compatibility fallback. Declarative preview forms are not the only implementation. A static crawler cannot prove that its browser supports or executes WebMCP tools. The authenticated /ask endpoint supports prefer.streaming: true and SSE start, result, and complete events. An anonymous 401 does not establish that streaming is absent. Keep the credential boundary when verifying it. OAuth discovery starts at auth.md, links to protected-resource and authorization-server metadata, and documents supported human-approved flows. EvalGate does not advertise WorkOS agent_auth identity assertions or registration endpoints that it does not implement. EvalGate does not publish a Web Bot Auth signing directory without an operated signer and key lifecycle. A public JWK document describes a signer’s keys; it does not by itself verify incoming bots. Machine Payments Protocol support and ChatGPT directory acceptance are also not claimed. These are separate product and external-registration boundaries, not missing documentation badges.