Skills/npm/post-engineer-mcp

post-engineer-mcp@1.54.231

VERIFIED· not started

Publisher claims: "Post Engineer MCP Server for AI pair programming and agentic workflows" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server)Publisher ryan-carloso · publishing for 62 daysInstalls 11,610Last detonated 19 min ago
$claude mcp add post-engineer-mcp -- npx -y post-engineer-mcp
WatchReport an issue

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
MCP_OAUTH_ISSUERMCP_OAUTH_JWKS_URLPOST_ENGINEER_API_KEYConfiguration, not credentials: AVATAR_PATH_DESCRIPTION, MCP_HTTP_ALLOW_REMOTE, MCP_HTTP_HOST, MCP_HTTP_PORT, MCP_HTTP_RATE_LIMIT_PER_MINUTE, MCP_RESOURCE, POST_ENGINEER_API_URL
Where it talks to
post-engineer.com (its own)
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. It asks for MCP_OAUTH_ISSUER, MCP_OAUTH_JWKS_URL, POST_ENGINEER_API_KEY and talks to post-engineer.com. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.

$vet-skills run --secrets MCP_OAUTH_ISSUER=post-engineer.com,MCP_OAUTH_JWKS_URL=post-engineer.com,POST_ENGINEER_API_KEY=post-engineer.com -- npx -y post-engineer-mcp

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-21 and scored it 92/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 · 13 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
13sprocessdependency install exit 1 · (Use `node --trace-warnings ...` to show where the warning was created) npm error Cannot read properties of null (reading 'edgesOut') npm error A complete log of this run can be found in: /tmp/ks-detonate-nEv0ka/task/home/.npm/_logs/2026-11-21T14_36_30_324Z-debug-0.log
13sclaimednot started: dependency install failed (exit 1); the server itself was not observed
13sprocessscript backend runs setup only
13sprocessno install scripts to re-run

Static findings

MEDIUM
MCP server using network transport (SSE/HTTP)dist/index.js:59 · MCP server using network transport (SSE/HTTP) — data sent over networkawait serveHttpTransport((auth) => createPostEngineerMcpServer(new PostEngineerClient({ apiKey: auth?.bearer ?? apiKey, suppressVersionHeader: true }), 'http'), httpOptions, authOptions);Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04

No other findings across 5,507 lines in 81 files.

Cost to the agent

Instructions loaded
≈57 tok
1 file · 81 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

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.