Pinpole MCP Server

@pinpole/mcp npm v0.3.2

Published by @pinpole — 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.

Pinpole MCP server — design cloud architectures, run cost simulations, and draw on the Pinpole canvas from Claude Code, Cursor, and Codex.

Trust grade
A
99/100
Last scanned get badge →
Trust
A · 99/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Minimal
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 99/100

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:

PointsAdoption-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 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 64

Each tool and what it can reach — statically extracted from the published source.

  • pinpole_ai_chatno sensitive capability
  • pinpole_ai_visionno sensitive capability
  • pinpole_apply_templateno sensitive capability
  • pinpole_canvas_syncno sensitive capability
  • pinpole_clone_templateno sensitive capability
  • pinpole_create_api_tokenno sensitive capability
  • pinpole_create_architectureno sensitive capability
  • pinpole_create_projectno sensitive capability
  • pinpole_create_team_inviteno sensitive capability
  • pinpole_create_team_projectno sensitive capability
Show 54 more tools ↓
  • pinpole_create_template_from_imageno sensitive capability
  • pinpole_create_workspaceno sensitive capability
  • pinpole_delete_projectno sensitive capability
  • pinpole_delete_workspaceno sensitive capability
  • pinpole_deploy_apply_changesno sensitive capability
  • pinpole_deploy_cancelno sensitive capability
  • pinpole_deploy_executeno sensitive capability
  • pinpole_deploy_gcp_executeno sensitive capability
  • pinpole_export_gif_shareno sensitive capability
  • pinpole_export_terraformno sensitive capability
  • pinpole_export_terraform_serverno sensitive capability
  • pinpole_get_deploy_latestno sensitive capability
  • pinpole_get_deploy_statusno sensitive capability
  • pinpole_get_driftno sensitive capability
  • pinpole_get_gcp_driftno sensitive capability
  • pinpole_get_meno sensitive capability
  • pinpole_get_projectno sensitive capability
  • pinpole_get_resource_infono sensitive capability
  • pinpole_get_service_specno sensitive capability
  • pinpole_get_simulationno sensitive capability
  • pinpole_get_subscriptionno sensitive capability
  • pinpole_get_teamno sensitive capability
  • pinpole_get_templateno sensitive capability
  • pinpole_get_usageno sensitive capability
  • pinpole_get_workspaceno sensitive capability
  • pinpole_github_lambda_functionsno sensitive capability
  • pinpole_github_reposno sensitive capability
  • pinpole_list_accountsno sensitive capability
  • pinpole_list_api_tokensno sensitive capability
  • pinpole_list_connectorsno sensitive capability
  • pinpole_list_deploymentsno sensitive capability
  • pinpole_list_notificationsno sensitive capability
  • pinpole_list_projectsno sensitive capability
  • pinpole_list_servicesno sensitive capability
  • pinpole_list_simulationsno sensitive capability
  • pinpole_list_team_invitesno sensitive capability
  • pinpole_list_team_membersno sensitive capability
  • pinpole_list_team_projectsno sensitive capability
  • pinpole_list_teamsno sensitive capability
  • pinpole_list_templatesno sensitive capability
  • pinpole_list_workspacesno sensitive capability
  • pinpole_open_billing_portalno sensitive capability
  • pinpole_recommend_connectionno sensitive capability
  • pinpole_revoke_api_tokenno sensitive capability
  • pinpole_rollback_templateno sensitive capability
  • pinpole_run_simulationno sensitive capability
  • pinpole_simulate_costno sensitive capability
  • pinpole_simulation_recommendationsno sensitive capability
  • pinpole_start_aws_connectno sensitive capability
  • pinpole_start_cloudflare_connectno sensitive capability
  • pinpole_start_gcp_connectno sensitive capability
  • pinpole_start_github_connectno sensitive capability
  • pinpole_update_projectno sensitive capability
  • pinpole_update_workspaceno sensitive capability

What this scan could not see

Versions 1

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.

VersionScoreFindingsEngineScanned
v0.3.2 latest A 99/100 0 1.13.0 2026-09-07

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.

MCP Trust Score: A · 99/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/pinpole-mcp/badge.svg)](https://mcptrustchecker.com/registry/pinpole-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/pinpole-mcp"><img src="https://mcptrustchecker.com/registry/pinpole-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/pinpole-mcp/badge.json via https://img.shields.io/endpoint?url=…

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 @pinpole/mcp --online

Use the free API → How scoring works

More in Cloud & DevOps