io.github.Bristlecone2026/bristlecone-logic
PYPI · BRISTLECONE-MCP · SCANNED SEP 21
Micro-settled web content extraction and JSON schema validation utilities for AI agents via XRPL.
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 1 of 32 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 29 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 78 tokens (~39/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the io.github.Bristlecone2026/bristlecone-logic MCP server?
io.github.Bristlecone2026/bristlecone-logic runs locally as a PyPI package, launched with uvx bristlecone-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · bristlecone-mcp
claude mcp add bristlecone2026-bristlecone-logic -- uvx bristlecone-mcp
{
"mcpServers": {
"bristlecone2026-bristlecone-logic": {
"command": "uvx",
"args": [
"bristlecone-mcp"
]
}
}
} {
"servers": {
"bristlecone2026-bristlecone-logic": {
"command": "uvx",
"args": [
"bristlecone-mcp"
]
}
}
} codex mcp add bristlecone2026-bristlecone-logic -- uvx bristlecone-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"bristlecone2026-bristlecone-logic": {
"type": "local",
"command": [
"uvx",
"bristlecone-mcp"
],
"enabled": true
}
}
} openclaw mcp add bristlecone2026-bristlecone-logic --command uvx --arg bristlecone-mcp
mcp_servers:
bristlecone2026-bristlecone-logic:
command: "uvx"
args: ["bristlecone-mcp"] {
"McpServers": {
"bristlecone2026-bristlecone-logic": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"bristlecone-mcp"
]
}
}
} assistant mcp add bristlecone2026-bristlecone-logic -t stdio -c uvx -a bristlecone-mcp
{
"mcpServers": {
"bristlecone2026-bristlecone-logic": {
"command": "uvx",
"args": [
"bristlecone-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
- Stability: 0.97 → pass security
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 17 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.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 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 pypi/bristlecone-mcp@0.1.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 32 packages
| Packages resolved | 32 |
|---|---|
| No linked repository | 1 |
| 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 →
bristlecone_extract_web ~36
Extract and sanitize clean textual content from any target web page. Costs 1 micro-credit.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
bristlecone_validate_schema ~42
Validate a JSON payload against a standard JSON Schema definition. Costs 1 micro-credit.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
| schema | object | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
What is the io.github.Bristlecone2026/bristlecone-logic MCP server?
io.github.Bristlecone2026/bristlecone-logic is an MCP server listed in the public MCP registry as io.github.Bristlecone2026/bristlecone-logic. Micro-settled web content extraction and JSON schema validation utilities for AI agents via XRPL. This page covers its PyPI package (bristlecone-mcp).
Is the io.github.Bristlecone2026/bristlecone-logic MCP server safe to use?
io.github.Bristlecone2026/bristlecone-logic scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. 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 io.github.Bristlecone2026/bristlecone-logic MCP server expose?
io.github.Bristlecone2026/bristlecone-logic exposes 2 tools: bristlecone_extract_web, bristlecone_validate_schema. Their descriptions and schemas cost roughly 78 tokens of context every time the server is loaded.
Is the io.github.Bristlecone2026/bristlecone-logic MCP server still maintained?
io.github.Bristlecone2026/bristlecone-logic 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.