mcp-registry/ai.bowmark/bowmark · v8.196.1
Verdict. Bowmark MCP server answered 99.82% of Glimind's liveness checks over 30 days, better than 25% of MCP servers, with 481 ms median handshake and 34 outages in 90 days. Its agent-readiness grade is A (96/100) across 16 tools, costing an agent about 3,923 tokens to load. Checked every few minutes; no tool is ever called.
Data as of .
| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 99.82% | 25% of MCP servers |
| Median handshake latency | 481 ms | 51% of MCP servers |
| p95 handshake latency | 2703 ms | — |
| Checks in 30 days | 5,016 | — |
| Outages, 90 days | 34 | — |
| Median recovery | 3 min | — |
| Agent-readiness score | 96/100 (A) | 82% of MCP servers |
| Tools | 16 | — |
| Tool-list size for an agent | ~3,923 tokens | 41% of MCP servers |
| Days observed | 29 | — |
As of 2026-10-27 02:17 UTC, the Bowmark MCP server is up with a Glimind reliability score of 88/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 34 outages in 90 days, with a median recovery of 3 minutes.
Do things on live websites: prices, availability, quotes, bookings, anything behind a form or login.
Claude Code
claude mcp add --transport http bowmark-mcp-server https://api.bowmark.ai/mcp/registry
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"bowmark-mcp-server": {
"type": "http",
"url": "https://api.bowmark.ai/mcp/registry"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
2 parameter(s) across 1 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
In the last 30 days: 0 tool(s) removed and 4 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/ai.bowmark/bowmark"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/ai.bowmark/bowmark"}) over MCP.
get_library ~542 tokensrequest_secret ~365 tokenssession_call ~326 tokensrun ~312 tokenslease_ip ~311 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fai.bowmark%2Fbowmark?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fai.bowmark%2Fbowmark?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.bowmark%2Fbowmark.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.bowmark%2Fbowmark.svg :target: https://glimind.com/server/mcp-registry%2Fai.bowmark%2Fbowmark?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:af8aacb26740a0e7…, first seen 2026-10-26, included at leaf 73224 of 76,802. Version history · verify what your client received.
Compare: most reliable security servers · most reliable web servers · most reliable other servers · most reliable browser servers · most reliable communication servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-27 02:17 UTC, the Bowmark MCP server is up with a Glimind reliability score of 88/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 34 outages in 90 days, with a median recovery of 3 minutes.
Bowmark MCP server advertises 16 tools, including add_connection, delete_connection, get_library, get_secret_link, lease_ip.
Point your MCP client at this streamable-http endpoint: https://api.bowmark.ai/mcp/registry
Glimind scanned all 16 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.