MCP.Market

walkerOS Source Browser MCP server

by walkeros.io·io.walkeros/source-browser·v4.5.0·348 stars
No reviews yet

Generate, parse, and validate walkerOS data-elb HTML tagging attributes

A92/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A92/100

full report

Adoption
Established

348 stars733 downloads/wk

Reviews

Write one

Nobody has reviewed walkerOS Source Browser yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

walkerOS Source Browser tools (3)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • generate_tagging

    Generate walkerOS data-elb HTML attributes from structured input. Returns attribute key-value pairs and an example HTML snippet.

  • parse_tagging

    Parse HTML with data-elb attributes using real DOM parsing (JSDOM). Extracts all walkerOS events and globals. Use validate_tagging for issue detection.

  • validate_tagging

    Validate HTML data-elb tagging for common mistakes. Checks for orphan actions, missing entities, unknown triggers, and more.

Public scan report

scanner v0.1.10 · 2026-10-16 · same rubric, same numbers if you re-run it

no findings
  • Code scan3 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 1 days ago15/15
  • Maintainer identitynamespace and repository owner differ; GitHub account older than a year; website matches verified namespace8/10
Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How walkerOS Source Browser compares

Against every graded Scraping and browsing MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
92/100
higher than 85% of 867 Scraping and browsing servers
Tools
3
the typical Scraping and browsing server has 6
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
348
more than 95% of 584 Scraping and browsing servers
Downloads a week
733
more than 90% of 312 Scraping and browsing servers with a package

What its tools let an agent do: 2 read · 1 create

Install walkerOS Source Browser in Claude Code, Cursor or VS Code

Runs npx -y @walkeros/mcp-source-browser on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add source-browser -- npx -y @walkeros/mcp-source-browser
Add to Cursor

What the publisher says

From the walkerOS Source Browser repository's README, as published. We do not edit it. Read it on GitHub

Event collection you own, version, and trust

From browser to BigQuery and ad platforms - warehouse-native, and ready for AI agents via MCP.

The problem

GA4, custom tags, ad pixels - each one a separate setup, none of them agreeing on the same numbers. When something breaks, you can't see where.

walkerOS is one collection layer for all of them.

Why walkerOS?

with confidence

  • Config-as-code - version control your tracking, review it in PRs, deploy

to every destination

  • Declarative tagging - tag your UI in HTML, not scattered JavaScript
  • Consent-native - events queue until consent is given, then flush correctly

in a dashboard

  • Schema validation - catch bad events at collection time, not weeks later

from a single event definition

  • One layer, many destinations - send to your warehouse and ad platforms

warehouse, ready to query

  • Warehouse-native - events land clean and structured in your data
  • MIT licensed - self-host anywhere, no vendor lock-in

How it works

GCP Functions, and more)

  • Sources: Where events come from (browser, dataLayer, Express, AWS Lambda,

enrichment)

  • Collector: The processing engine (consent, validation, mapping, routing,

more)

  • Destinations: Where events go (GA4, Google Ads, Meta CAPI, BigQuery, and

Two ways to install walkerOS

Choose one based on your workflow and integration possibilities:

Integrated (import into your app):

import { startFlow } from '@walkeros/collector';

const { elb } = await startFlow({
  destinations: {
    console: {
      code: {
        type: 'console',
        config: {},
        push: (event) => console.log('Event:', event.name),
      },
    },
  },
});

await elb('page view', { title: 'Home' });
// -> logs: Event: page view

Wire a real source and destination once you are ready:

import { startFlow } from '@walkeros/collector';
import { sourceBrowser } from '@walkeros/web-source-browser';
import { destinationGtag } from '@walkeros/web-destination-gtag';

await startFlow({
  sources: {
    browser: {
      code: sourceBrowser,
      config: { settings: { pageview: true } },
    },
  },
  destinations: {
    ga4: {
      code: destinationGtag,
      config: {
        settings: { ga4: { measurementId: 'G-XXX' } },
      },
    },
  },
});

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

walkerOS Source Browser: common questions

Is walkerOS Source Browser MCP server safe?
Yes, by our scan: it is graded A (92/100). Read the walkerOS Source Browser safety report
How do I install walkerOS Source Browser?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does walkerOS Source Browser need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is walkerOS Source Browser maintained?
The last commit was 20 days ago (2026-10-15). The latest release is v4.5.0.
What can I use instead of walkerOS Source Browser?
Servers from other publishers that do the same job: Presio MCP server, GrowBlocks Dev Kit MCP server and SeleniumBase MCP server.
How does walkerOS Source Browser compare with other Scraping and browsing MCP servers?
safety score 92/100 (higher than 85% of 867 Scraping and browsing servers); tools 3 (the typical Scraping and browsing server has 6); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to walkerOS Source Browser

Same job from other publishers: the closest match first, then the best rated.

  • Presio
    Present PDFs from the browser: upload to start a slideshow or validate Presio sidecars. No auth.
    A
  • GrowBlocks Dev Kit
    Build, play-test with screenshots, and ship three.js browser games on GrowBlocks.
    A
  • SeleniumBase MCP
    Stealthy browser automation, testing, and web-scraping via CDP Mode.
    A
  • Next AI Draw.io
    draw.io diagrams your AI agent draws on a live browser canvas that you can also edit by hand
    A
  • AIHawk
    AI browser agent: browses, clicks, types, and reads real web pages from plain-English instructions.
    More from feder-cr →
    A