Postproxy MCP Server
postproxy-mcp
npm
v1.17.0
Published by postproxy — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
MCP server for Postproxy API integration with Claude Code
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 1 = 99. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 1
low Hardcoded egress to an external endpoint in packaging/dev tooling (test/worker-auth.test.mjs)MTC-SRC-003
In a packaging/dev/install script (shipped, but not the server runtime) (`test/worker-auth.test.mjs:22`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: aders = {}) => worker.fetch('https://mcp.postproxy.dev/mcp', { method: 'POST', headers: { 'Content-Type': 'app
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server test/worker-auth.test.mjs
Tools 64
Each tool and what it can reach — statically extracted from the published source.
auth_statusno sensitive capabilitycomments_createno sensitive capabilitycomments_deleteno sensitive capabilitycomments_getno sensitive capabilitycomments_hideno sensitive capabilitycomments_likeno sensitive capabilitycomments_listno sensitive capabilitycomments_unhideno sensitive capabilitycomments_unlikeno sensitive capabilitydm_chat_archiveno sensitive capability
Show 54 more tools ↓
dm_chat_createno sensitive capabilitydm_chat_getno sensitive capabilitydm_chat_unarchiveno sensitive capabilitydm_chats_listno sensitive capabilitydm_comment_private_replyno sensitive capabilitydm_message_editno sensitive capabilitydm_message_getno sensitive capabilitydm_message_reactno sensitive capabilitydm_message_sendno sensitive capabilitydm_message_unreactno sensitive capabilitydm_messages_listno sensitive capabilitygoogle_business_attributes_availableno sensitive capabilitygoogle_business_attributes_getno sensitive capabilitygoogle_business_attributes_updateno sensitive capabilitygoogle_business_categories_listno sensitive capabilitygoogle_business_food_menus_getno sensitive capabilitygoogle_business_food_menus_updateno sensitive capabilitygoogle_business_hours_updateno sensitive capabilitygoogle_business_location_getno sensitive capabilitygoogle_business_location_updateno sensitive capabilitygoogle_business_media_createno sensitive capabilitygoogle_business_media_deleteno sensitive capabilitygoogle_business_media_listno sensitive capabilitygoogle_business_place_action_link_createno sensitive capabilitygoogle_business_place_action_link_deleteno sensitive capabilitygoogle_business_place_action_link_updateno sensitive capabilitygoogle_business_place_action_links_listno sensitive capabilitygoogle_business_service_list_getno sensitive capabilitygoogle_business_service_list_updateno sensitive capabilityhistory_listno sensitive capabilitypost_deleteno sensitive capabilitypost_delete_on_platformno sensitive capabilitypost_publishno sensitive capabilitypost_publish_draftno sensitive capabilitypost_statsno sensitive capabilitypost_statusno sensitive capabilitypost_updateno sensitive capabilityprofile_comments_createno sensitive capabilityprofile_comments_deleteno sensitive capabilityprofile_comments_getno sensitive capabilityprofile_comments_listno sensitive capabilityprofile_groups_initialize_connectionno sensitive capabilityprofile_groups_listno sensitive capabilityprofiles_listno sensitive capabilityprofiles_placementsno sensitive capabilityprofiles_statsno sensitive capabilityqueues_createno sensitive capabilityqueues_deleteno sensitive capabilityqueues_getno sensitive capabilityqueues_listno sensitive capabilityqueues_next_slotno sensitive capabilityqueues_updateno sensitive capabilitysummary_getno sensitive capabilityupload_createno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (64 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 6
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.17.0 latest |
A 99/100 | 1 | 1.13.0 | 2026-09-07 |
v1.15.0 |
A 99/100 | 0 | 1.13.0 | 2026-08-31 |
v1.14.0 |
A 99/100 | 0 | 1.12.1 | 2026-08-18 |
v1.13.0 |
A 99/100 | 0 | 1.12.1 | 2026-08-16 |
v1.12.0 |
A 99/100 | 0 | 1.12.1 | 2026-08-12 |
Show 1 more version ↓
v1.10.0 |
A 99/100 | 0 | 1.12.1 | 2026-08-06 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan postproxy-mcp --onlineMore in Marketing & Social
Official Abyssfall game info, newsletter double opt-in, and merch reservation tools.
AdCritter ads platform: docs, API reference, app scaffolding, and white-label integration.
Google AdSense MCP Server - Monitor earnings, reports, and account health via Claude/AI
Operational empathy for technical founders + PE/VC operators navigating high-stakes B2B interactions. 28 MCP tools + CLI: ICP scoring, persona simulation, battlecards, deal classification, prospect discovery, investor matching, founder wellness, plus mark
MCP server for Bing Webmaster Tools — SEO site management, URL submission, sitemaps, stats, keywords
MCP (Model Context Protocol) server that helps AI agents use Primer Brand (@primer/react-brand) correctly when building GitHub marketing and landing pages.