Search / io.github.R1ghtHereWaiting/engagelab-email
engagelab-email
L0 · runs locallySend, receive, monitor and reply to email from AI agents with threaded inbox context.
v0.1.2 · active · repository · descriptor JSON · versions
Search / io.github.R1ghtHereWaiting/engagelab-email
Send, receive, monitor and reply to email from AI agents with threaded inbox context.
v0.1.2 · active · repository · descriptor JSON · versions
{
"mcpServers": {
"engagelab-email": {
"command": "npx",
"args": [
"-y",
"@engagelabemail/[email protected]"
],
"env": {
"ENGAGELAB_EMAIL_SECRET_KEY": "${ENGAGELAB_EMAIL_SECRET_KEY}"
}
}
}
}claude mcp add engagelab-email -e "ENGAGELAB_EMAIL_SECRET_KEY=${ENGAGELAB_EMAIL_SECRET_KEY}" -- npx -y @engagelabemail/[email protected][mcp_servers.engagelab-email]
command = "npx"
args = ["-y", "@engagelabemail/[email protected]"]
env = { "ENGAGELAB_EMAIL_SECRET_KEY" = "${ENGAGELAB_EMAIL_SECRET_KEY}" }
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"engagelab-email": {
"type": "local",
"command": [
"npx",
"-y",
"@engagelabemail/[email protected]"
],
"enabled": true,
"environment": {
"ENGAGELAB_EMAIL_SECRET_KEY": "{env:ENGAGELAB_EMAIL_SECRET_KEY}"
}
}
}
}{
"mcpServers": {
"engagelab-email": {
"command": "npx",
"args": [
"-y",
"@engagelabemail/[email protected]"
],
"env": {
"ENGAGELAB_EMAIL_SECRET_KEY": "${ENGAGELAB_EMAIL_SECRET_KEY}"
}
}
},
"deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=engagelab-email&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsIkBlbmdhZ2VsYWJlbWFpbC9tY3BAMC4xLjIiXSwiZW52Ijp7IkVOR0FHRUxBQl9FTUFJTF9TRUNSRVRfS0VZIjoiJHtFTkdBR0VMQUJfRU1BSUxfU0VDUkVUX0tFWX0ifX0%3D"
}{
"servers": {
"engagelab-email": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@engagelabemail/[email protected]"
],
"env": {
"ENGAGELAB_EMAIL_SECRET_KEY": "${ENGAGELAB_EMAIL_SECRET_KEY}"
}
}
}
}{
"mcpServers": {
"engagelab-email": {
"command": "npx",
"args": [
"-y",
"@engagelabemail/[email protected]"
],
"env": {
"ENGAGELAB_EMAIL_SECRET_KEY": "${ENGAGELAB_EMAIL_SECRET_KEY}"
}
}
}
}extensions:
"engagelab-email":
enabled: true
name: "engagelab-email"
type: stdio
cmd: "npx"
args:
- "-y"
- "@engagelabemail/[email protected]"
envs:
"ENGAGELAB_EMAIL_SECRET_KEY": "${ENGAGELAB_EMAIL_SECRET_KEY}"
timeout: 300
Placeholders to fill from your own secret store: ${ENGAGELAB_EMAIL_SECRET_KEY}. The registry never accepts secret values.
This is a local package: the command runs on your machine.
Not scored: fewer than three checks apply, usually because no remote answered a credential-free probe or the server is a local package.
protocol.modern, protocol.stateless, protocol.transport, protocol.list_ttlno remote answered a protocol handshake (not probed yet, unreachable, or local-only)auth.prm, auth.as_metadata, auth.cimdno remote uses OAuthauth.secret_in_urlno templated URLtools.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)stability.changes, stability.rug_pulltool list unknowndeps.known_vulnsno known advisory in 98 resolved packagesdeps.mcp_sdk_version@modelcontextprotocol/sdk 1.30.1 has 1 known advisory (GHSA-6qxp-vccf-f47h); update @modelcontextprotocol/sdk to 1.31.0 or laterdeps.resolvable@engagelabemail/[email protected] resolved: 98 packagesNo tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.
Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.
+repository ~liveness-unmeasured ~updated-39d-ago
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
@engagelabemail/[email protected] npm97 dependencies, resolved · MCP SDK @modelcontextprotocol/sdk 1.30.1 · advisories checked 2026-10-09
| advisory | severity | package | fixed in |
|---|---|---|---|
| GHSA-6qxp-vccf-f47hMCP TypeScript SDK: OAuth client could send credentials to an authorization server chosen by the MCP server | high | @modelcontextprotocol/[email protected]MCP SDK, direct | fixed in 1.31.0 |
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.
| package | registry | version | runtime | secrets |
|---|---|---|---|---|
@engagelabemail/mcp | npm | 0.1.2 | – | ENGAGELAB_EMAIL_SECRET_KEY |
No tools observed. Local packages are never executed by the registry.
Schemas: list_tools.
{
"name": "io.github.R1ghtHereWaiting/engagelab-email",
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
"version": "0.1.2",
"packages": [
{
"version": "0.1.2",
"transport": {
"type": "stdio"
},
"identifier": "@engagelabemail/mcp",
"registryType": "npm",
"environmentVariables": [
{
"name": "ENGAGELAB_EMAIL_SECRET_KEY",
"format": "string",
"isSecret": true,
"isRequired": true,
"description": "EngageLab Secret Key starting with sk_. The region prefix (sk_sg_ / sk_tr_) determines the API node."
},
{
"name": "ENGAGELAB_EMAIL_BASE_URL",
"format": "string",
"description": "Optional API base URL override. Inferred from the Secret Key region prefix when omitted."
}
]
}
],
"repository": {
"url": "https://github.com/Metaverse-Cloud/engagelab-email-mcp",
"source": "github"
},
"description": "Send, receive, monitor and reply to email from AI agents with threaded inbox context."
}