Bowmark
NPM · @BOWMARK/MCP · 3 COMPONENTS · SCANNED SEP 21
Do things on live websites: prices, availability, quotes, bookings, anything behind a form or login.
Available components
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 Security98
- 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
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Build provenance is cryptographically sound, but it attests a different repository to the one declared in the registry. Most often the declared URL is simply stale. View diagnostics → Unverified
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 46 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
- Schema quality not yet verified: this package declared that it provides tools, but our sandbox run could not list them, so the captured schema is incomplete.Unverified
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage0
- Tool coverage not yet verified: this package declared that it provides tools, but our sandbox run could not list them.Unverified
Tool Safety0
- Tool safety not yet verified: this package declared that it provides tools, but our sandbox run could not list them.Unverified
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 3 categories
Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →
How do I install the Bowmark MCP server?
Bowmark runs locally as an npm package, launched with npx -y @bowmark/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @bowmark/mcp
claude mcp add ai-bowmark-bowmark -- npx -y @bowmark/mcp
{
"mcpServers": {
"ai-bowmark-bowmark": {
"command": "npx",
"args": [
"-y",
"@bowmark/mcp"
]
}
}
} {
"servers": {
"ai-bowmark-bowmark": {
"command": "npx",
"args": [
"-y",
"@bowmark/mcp"
]
}
}
} codex mcp add ai-bowmark-bowmark -- npx -y @bowmark/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-bowmark-bowmark": {
"type": "local",
"command": [
"npx",
"-y",
"@bowmark/mcp"
],
"enabled": true
}
}
} openclaw mcp add ai-bowmark-bowmark --command npx --arg -y --arg @bowmark/mcp
mcp_servers:
ai-bowmark-bowmark:
command: "npx"
args: ["-y", "@bowmark/mcp"] {
"McpServers": {
"ai-bowmark-bowmark": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@bowmark/mcp"
]
}
}
} assistant mcp add ai-bowmark-bowmark -t stdio -c npx -a -y @bowmark/mcp
{
"mcpServers": {
"ai-bowmark-bowmark": {
"command": "npx",
"args": [
"-y",
"@bowmark/mcp"
]
}
}
} 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.
- 21 Sept 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.
- 19 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
- 15 Sept 26 −3
- Stability: pass → 0.77 functional
- 14 Sept 26 0
- Stability: 0.97 → pass security
- 13 Sept 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.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 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 21 Sept 2026 · Analysed npm/@bowmark/mcp@2.1.0
Provenance Repository mismatch
The attestation is cryptographically sound but binds a different repository to the one the registry declares. Most often the declared URL is simply stale.
| Result | Repository mismatch |
|---|---|
| Ecosystem | npm |
| Reason | Repository mismatch |
| Discovered via | Registry attestation endpoint |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/bowmark-ai/mcp/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 2353324225 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:b700a6d42b9608ccf16ed01da7e7ef0f8a3527f61ad62b7412d214555924c27de94e6d3eab13f3c2350e807d00c894106e5bc407982f02a25908b438f |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| 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 →
The sandbox run completed and this package exposed no tools.
What is the Bowmark MCP server?
Bowmark is an MCP server listed in the public MCP registry as ai.bowmark/bowmark. Do things on live websites: prices, availability, quotes, bookings, anything behind a form or login. This page covers its npm package (@bowmark/mcp).
Is the Bowmark MCP server safe to use?
Bowmark scores 56 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. 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 Bowmark MCP server expose?
Bowmark exposes no tools. We connected to it and read its tool list, and it was empty, so it offers an MCP client nothing to call.
Is the Bowmark MCP server still maintained?
Bowmark is still listed as active in the MCP registry. We last reached this channel on 21 September 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 Bowmark MCP server under?
Bowmark declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.