An agent can connect on its own if it already holds CANVASAAS_TOKEN.Remote endpoint behind a static API key or header. The registry never sees the value; the agent fills the placeholder.
tools.descriptions, tools.description_length, tools.schemas, tools.annotations, tools.directory_hints, tools.token_cost, tools.api_dumptool list unknown (behind auth, not probed, or empty)
stabilityn/a · weight 15
n/a
stability.changes, stability.rug_pulltool list unknown
dependencies100 · weight 15
pass
deps.known_vulnsno known advisory in 1 resolved packages
n/a
deps.mcp_sdk_versionthe official MCP SDK is not in the dependency graph
Dependency graphs from deps.dev; advisories from OSV.dev, including the GitHub Advisory Database and the PyPI Advisory Database; all CC BY 4.0. The graph is what a clean install of this version resolves today; nothing was installed or run. How it is checked.
Endpoints
remote
auth
reachable
uptime 30d
p50
protocol
last ok
https://mcp.canvasaas.com/ssesse
api_key ${CANVASAAS_TOKEN}
no (13 failures)
0%
–
–
–
package
registry
version
runtime
secrets
canvasaas
npm
1.1.3
npx
CVS_API_KEY
Tools (0)
No tools observed. Tools appear once a credential-free probe can list them.