MCP Risk Ledger MCP vs Pushary
A side-by-side look at the MCP Risk Ledger MCP and Pushary MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
M
MCP Risk Ledger MCPSecurityPaid remote MCP for server intake risk reports, tool review, approvals, and readiness.12EmergingAuth: not declaredVerdict: choose MCP Risk Ledger MCP for security work; choose Pushary for security as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
MChoose MCP Risk Ledger MCP when
- You need dedicated capabilities in the Security domain.
Choose Pushary when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
PUSHARY_API_KEY. - You want tools like
send_notification, ask_user, wait_for_answer.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | M MCP Risk Ledger MCP | |
|---|---|---|
| Category | Security | Security |
| Quality signal | 12/100 · Emerging | 57/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | PUSHARY_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 1 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | 6 |
| Full listing | View MCP Risk Ledger MCP | View Pushary |
Tools & capabilities
MCP Risk Ledger MCP tools
No tool names declared yet. Check the project README from the listing page.
Pushary tools 6
send_notificationSend a push notification with optional rich context (file changes, errors, next steps)ask_userAsk the user a question via push - yes/no, multiple choice, or free textwait_for_answerLong-poll for the user's response to a questioncancel_questionCancel a pending question that's no longer relevantlist_sessionsRead-only view of your live agent sessions and pending questionspropose_scopeRatify the boundary of a run: file globs, enforced on supported hosts, or a recorded promise when the run changes no files
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
MCP Risk Ledger MCP
No confirmed install command for MCP Risk Ledger MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Pushary
{
"mcpServers": {
"pushary": {
"command": "npx",
"args": [
"-y",
"pushary@latest"
],
"env": {
"PUSHARY_API_KEY": "YOUR_PUSHARY_API_KEY_HERE"
}
}
}
}
Frequently asked questions
MCP Risk Ledger MCP is categorized under Security and uses an install path we have not confirmed yet. Pushary belongs to Security and uses a local stdio subprocess. Pick MCP Risk Ledger MCP for security work and Pushary for security.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. MCP Risk Ledger MCP has no confirmed install command yet — follow its own setup instructions.
MCP Risk Ledger MCP has no declared pricing — check the project's own site. Pushary has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add mcp-risk-ledger-mcp and pushary as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Risk Ledger MCP has a quality signal of 12/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars. Pushary has 57/100 (Good) with 2 views, 0 installs and 1 GitHub stars.