Tapsite MCP Server

tapsite npm v5.2.0

Published by mgriffen — 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 web intelligence extraction — design systems, accessibility audits, competitive analysis, and migration prep

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/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
Moderate
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 = 96/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 − 4 = 96. 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
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−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

medium Hardcoded egress to an external endpoint (src/server.js)MTC-SRC-003

In the server's implementation (`src/server.js:53`): 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: ckage.json').version; fetch('https://registry.npmjs.org/tapsite/latest', { signal: AbortSignal.timeout(5000) }) .t

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 src/server.js

Tools 55

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

  • tapsite_crawlingests untrusted input
  • tapsite_download_imagesingests untrusted input
  • tapsite_extract_faviconingests untrusted input
  • tapsite_auditno sensitive capability
  • tapsite_capture_networkno sensitive capability
  • tapsite_closeno sensitive capability
  • tapsite_designsystemno sensitive capability
  • tapsite_diff_pagesno sensitive capability
  • tapsite_exportno sensitive capability
  • tapsite_export_design_reportno sensitive capability
Show 45 more tools ↓
  • tapsite_extract_a11yno sensitive capability
  • tapsite_extract_aimlno sensitive capability
  • tapsite_extract_animationsno sensitive capability
  • tapsite_extract_api_schemano sensitive capability
  • tapsite_extract_breakpointsno sensitive capability
  • tapsite_extract_canvasno sensitive capability
  • tapsite_extract_colorsno sensitive capability
  • tapsite_extract_componentsno sensitive capability
  • tapsite_extract_contentno sensitive capability
  • tapsite_extract_contrastno sensitive capability
  • tapsite_extract_css_varsno sensitive capability
  • tapsite_extract_customno sensitive capability
  • tapsite_extract_darkmodeno sensitive capability
  • tapsite_extract_fontsno sensitive capability
  • tapsite_extract_formsno sensitive capability
  • tapsite_extract_graphqlno sensitive capability
  • tapsite_extract_i18nno sensitive capability
  • tapsite_extract_iconsno sensitive capability
  • tapsite_extract_imagesno sensitive capability
  • tapsite_extract_layoutno sensitive capability
  • tapsite_extract_linksno sensitive capability
  • tapsite_extract_markdownno sensitive capability
  • tapsite_extract_metadatano sensitive capability
  • tapsite_extract_perfno sensitive capability
  • tapsite_extract_pwano sensitive capability
  • tapsite_extract_schema_suggestno sensitive capability
  • tapsite_extract_securityno sensitive capability
  • tapsite_extract_shadowsno sensitive capability
  • tapsite_extract_spacingno sensitive capability
  • tapsite_extract_stackno sensitive capability
  • tapsite_extract_storageno sensitive capability
  • tapsite_extract_svgsno sensitive capability
  • tapsite_extract_tableno sensitive capability
  • tapsite_extract_third_partyno sensitive capability
  • tapsite_extract_wasmno sensitive capability
  • tapsite_extract_web_componentsno sensitive capability
  • tapsite_harvestno sensitive capability
  • tapsite_inspectno sensitive capability
  • tapsite_interactno sensitive capability
  • tapsite_login_checkno sensitive capability
  • tapsite_login_manualno sensitive capability
  • tapsite_run_jsno sensitive capability
  • tapsite_screenshotno sensitive capability
  • tapsite_scrollno sensitive capability
  • tapsite_teardownno 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
v5.2.0 latest A 96/100 1 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 · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/tapsite/badge.svg)](https://mcptrustchecker.com/registry/tapsite)
HTML
<a href="https://mcptrustchecker.com/registry/tapsite"><img src="https://mcptrustchecker.com/registry/tapsite/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/tapsite/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 tapsite --online

Use the free API → How scoring works

More in Browser Automation