walkerOS Source Browser
NPM · @WALKEROS/MCP-SOURCE-BROWSER
Generate, parse, and validate walkerOS data-elb HTML tagging attributes
Available components
Last scanned (8 minutes ago)
Scores higher than 96% of npm servers
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security99
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 36 of 134 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to elbwalker/walkerOS). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 369 tokens (~73/item across 5 items; 3 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 6 Nov 26 −3
- Stability: pass → 0.80 functional
- 4 Nov 26 0
- Security disclosure: fail → pass ▲ functional
- 31 Oct 26 +1
- Stability: 0.97 → pass security
- 30 Oct 26 −1
- Stability: pass → 0.97 functional
- 24 Oct 26 +1
- Stability: 0.97 → pass security
- 23 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 0
- Stability: 0.97 → pass security
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 6 Nov 2026 · Analysed npm/@walkeros/mcp-source-browser@4.5.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | elbwalker/walkerOS |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/elbwalker/walkerOS/.github/workflows/release.yml@refs/heads/713-bot-context-mapping |
| Rekor log index | 2581554780 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:e4a117bc2801f3b3e3cf7d49eb55f79f48e97e7f2de35e9dc1650f619662970e067b006db6e11f18d2267912235df7070eb49e9a4b6c3000021c96cc4 |
Background: How many MCP packages publish verified provenance →
Dependencies 134 packages
| Packages resolved | 134 |
|---|---|
| Stale | 36 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
generate_tagging Generate Tagging ~202
Generate walkerOS data-elb HTML attributes from structured input. Returns attribute key-value pairs and an example HTML snippet.
| Name | Type | Req | Description |
|---|---|---|---|
| action | object | – | Trigger:action pairs for data-elbaction (nearest entity only) |
| actions | object | – | Trigger:action pairs for data-elbactions (all entities) |
| context | object | – | Context properties for data-elbcontext |
| data | object | – | Entity properties as key:value pairs |
| entity | string | – | Entity name (creates data-elb="entity" and scopes data-elb-entity properties) |
| globals | object | – | Global properties for data-elbglobals |
| link | object | – | Link relationships for data-elblink (id:type, e.g. {"details":"parent"}) |
| prefix | string | – | Custom prefix (default: data-elb) |
| scoped | object | – | Path-scoped generic properties for data-elb_ (only triggers nested below this element receive them) |
| Name | Type | Req | Description |
|---|---|---|---|
| attributes | object | yes | Generated HTML data attributes |
| html | string | yes | Example HTML element with the attributes applied |
No examples provided.
parse_tagging Parse Tagging ~71
Parse HTML with data-elb attributes using real DOM parsing (JSDOM). Extracts all walkerOS events and globals. Use validate_tagging for issue detection.
| Name | Type | Req | Description |
|---|---|---|---|
| html | string | yes | HTML snippet with data-elb attributes |
| prefix | string | – | Custom prefix (default: data-elb) |
| Name | Type | Req | Description |
|---|---|---|---|
| events | array | yes | Extracted walkerOS events |
| globals | object | yes | Global properties |
| summary | string | yes | Human-readable summary |
No examples provided.
validate_tagging Validate Tagging ~59
Validate HTML data-elb tagging for common mistakes. Checks for orphan actions, missing entities, unknown triggers, and more.
| Name | Type | Req | Description |
|---|---|---|---|
| html | string | yes | HTML snippet to validate |
| prefix | string | – | Custom prefix (default: data-elb) |
| Name | Type | Req | Description |
|---|---|---|---|
| errors | array | yes | Critical issues |
| info | array | yes | Informational notes |
| summary | string | yes | Human-readable validation summary |
| valid | boolean | yes | True if no errors found |
| warnings | array | yes | Potential issues |
No examples provided.
How do I install the walkerOS Source Browser MCP server?
walkerOS Source Browser runs locally as an npm package, launched with npx -y @walkeros/mcp-source-browser. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @walkeros/mcp-source-browser
claude mcp add io-walkeros-source-browser -- npx -y @walkeros/mcp-source-browser
What is the walkerOS Source Browser MCP server?
walkerOS Source Browser is an MCP server listed in the public MCP registry as io.walkeros/source-browser. Generate, parse, and validate walkerOS data-elb HTML tagging attributes. This page covers its npm package (@walkeros/mcp-source-browser).
Is the walkerOS Source Browser MCP server safe to use?
walkerOS Source Browser scores 93 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 6 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the walkerOS Source Browser MCP server expose?
walkerOS Source Browser exposes 3 tools: generate_tagging, parse_tagging, validate_tagging. Their descriptions and schemas cost roughly 332 tokens of context every time the server is loaded.
Is the walkerOS Source Browser MCP server still maintained?
walkerOS Source Browser is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the walkerOS Source Browser MCP server under?
walkerOS Source Browser declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the walkerOS Source Browser MCP server?
VerifyMCP ran 16 checks on walkerOS Source Browser, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.