vayl-mcp@0.11.0
VERIFIED· not startedPublisher claims: "The reconciling memory layer for AI agents, over MCP: when a fact changes, the old value is retired and kept in history." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
ANTHROPIC_API_KEYEMBED_API_KEYGROQ_API_KEYNEO4J_PASSWORDOPENAI_API_KEYVAULT_TOKENVAYL_DATABASE_URLVAYL_METRICS_TOKENConfiguration, not credentials: ANTHROPIC_MODEL, EMBED_BASE_URL, EMBED_MODEL, GROQ_MODEL, LLM_PROVIDER, NEO4J_URI, NEO4J_USER, OPENAI_BASE_URL, OPENAI_MODEL, OPENAI_REASONING_EFFORT, OPENAI_SYSTEM_PREFIX, VAULT_ADDR, VAYL_ALLOWED_HOSTS, VAYL_ALLOWED_ORIGINS, VAYL_CONFIRM_MODE, VAYL_CRITICAL_CATEGORIES, VAYL_DB, VAYL_ESCALATE_MODEL, VAYL_EXTRACTOR_ID, VAYL_HOST, VAYL_KDF, VAYL_KEY, VAYL_KMS, VAYL_LICENSE, VAYL_LOG_FORMAT, VAYL_LOG_LEVEL, VAYL_OIDC_AUDIENCE, VAYL_OIDC_DEFAULT_ROLE, VAYL_OIDC_ISSUER, VAYL_OIDC_JWKS_URL, VAYL_OIDC_ROLE_CLAIM, VAYL_OIDC_ROLE_MAP- Where it talks to
- no vendor host named in the codeAlso okta.com, acme.com, groq.com, openrouter.ai, cerebras.ai — not the publisher's domain; check what for before connecting.
- What we saw when it ran
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names okta.com, acme.com, groq.com, openrouter.ai, cerebras.ai as well as its own vendor. The guard injects ANTHROPIC_API_KEY, EMBED_API_KEY, GROQ_API_KEY, NEO4J_PASSWORD, OPENAI_API_KEY, VAULT_TOKEN, VAYL_DATABASE_URL, VAYL_METRICS_TOKEN only into requests to the host you bind (and its subdomains) and refuses the rest.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-20 and scored it 87/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
mcp_app = mcp_server.mcp.http_app(transport="http", stateless_http=True)Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.mcp_app = mcp_server.mcp.http_app(transport="http", stateless_http=True, **mcp_server._transport_security())Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.with self.db.space_lock(_AUDIT_LOCK_KEY): # serialize read-head -> compute -> insert (cross-process)Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.mcp_app = mcp_server.mcp.http_app(transport="http", stateless_http=True,Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.r = subprocess.run([sys.executable, str(root / "openapi" / "generate.py"), "--check"],Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
Not checked against OSV yet; the weekly check has not reached this version.