Local Scanner MCP Server

Created By
treaties-aia year ago
MCP server for scanning local code and localhost URLs
Overview

what is Local Scanner MCP Server?

Local Scanner MCP Server is a Model Context Protocol (MCP) server designed for scanning local code and localhost URLs, providing tools for validating code, capturing screenshots, and analyzing web pages running on localhost.

how to use Local Scanner MCP Server?

To use the Local Scanner MCP Server, clone the repository from GitHub, install the dependencies, build the project, and start the server. It can be integrated with MCP clients like VSCode/Cline or WindSurf/Cascade by configuring their settings files.

key features of Local Scanner MCP Server?

  • Scan localhost URLs for runtime errors and console logs.
  • Capture screenshots of web pages.
  • Lint JavaScript, TypeScript, or CSS code files.
  • Validate HTML for accessibility and standards compliance.

use cases of Local Scanner MCP Server?

  1. Testing and debugging locally running web applications.
  2. Capturing visual verification screenshots during development.
  3. Ensuring code quality through linting.
  4. Validating HTML content for compliance with standards.

FAQ from Local Scanner MCP Server?

  • What is the purpose of the Local Scanner MCP Server?

It helps developers validate and analyze their local web applications and code files using AI capabilities.

  • Is it compatible with all local development environments?

Yes, it can be used with any local development setup that supports MCP clients.

  • How do I install the Local Scanner MCP Server?

Clone the repository, install dependencies, build the project, and start the server as per the instructions in the documentation.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
treaties-ai
Star
0
Language
JavaScript
License
MIT license

Recommend Servers

View All
Voyei

2 hours ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago