io.github.meltingpixelsai/zero-core-tools
REMOTE · TOOLS.RUGSLAYER.COM · 2 COMPONENTS
Web scraping, code review, content gen, sentiment. Zero Core Tools.
Available components
Last scanned (17 hours ago)
Scores higher than 69% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Web Scraping
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 584 tokens (~64/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 4 Nov 26 −1
- Stability: pass → 0.97 functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 6 Aug 26 0
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Schema quality: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → pass ▲ functional
- Schema quality: unverified → good ▲ functional
- First check of Tool coverage: 100 functional
- New tool “health” functional
- New tool “analyze_sentiment” functional
- New tool “extract_structured_data” functional
- New tool “generate_content” functional
- New tool “list_tools” functional
- New tool “review_code” functional
- New tool “scrape_url” functional
- New tool “screenshot_url” functional
- New tool “search_web” functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 4 Nov 2026 · Probed https://tools.rugslayer.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=tools.rugslayer.com | CN=YE1,O=Let's Encrypt,C=US | 30 Oct 2026 | 28 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 64d49be0d884ad8d88739084f9855cf6574 |
| SANs: tools.rugslayer.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of tools.rugslayer.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| rugslayer.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://tools.rugslayer.com/mcp | Verified | 200 | |
| http (plaintext) | http://tools.rugslayer.com/mcp | HTTPS enforced | 301 | https://tools.rugslayer.com/mcp |
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 →
analyze_sentiment ~49
Analyze sentiment of text with entity extraction, confidence scores, and key phrase identification. Returns positive/negative/neutral/mixed with detailed breakdown.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | Text to analyze for sentiment |
No output schema declared.
No examples provided.
extract_structured_data ~87
Scrape a URL then use AI to extract structured JSON data matching your schema description. Combines Playwright scraping with Grok LLM extraction.
| Name | Type | Req | Description |
|---|---|---|---|
| schema_description | string | yes | Description of the data to extract and desired JSON structure. Example: 'Extract all product names and prices as {products: [{name, price}]}' |
| url | string | yes | URL to scrape |
No output schema declared.
No examples provided.
generate_content ~99
Generate high-quality written content. Supports blog posts, product descriptions, documentation, social posts, and emails. Customizable tone, length, and keywords.
| Name | Type | Req | Description |
|---|---|---|---|
| keywords | string | – | Comma-separated keywords to include |
| length | string | – | Target length (default: medium) |
| tone | string | – | Writing tone (default: professional) |
| topic | string | yes | Topic or subject to write about |
| type | string | yes | Content type |
No output schema declared.
No examples provided.
health ~21
Check Zero Core Tools server status, uptime, and payment network configuration.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_tools ~25
List all available Zero Core Tools with pricing and input requirements. Use this for discovery.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
review_code ~93
AI-powered security and quality code review. Analyzes for vulnerabilities, anti-patterns, performance issues, and best practices. Returns issues with severity, suggestions, and an overall score.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Source code to review |
| focus | string | – | Focus area: security, quality, performance, or all (default: all) |
| language | string | – | Programming language (auto-detected if omitted) |
No output schema declared.
No examples provided.
scrape_url ~63
Scrape any URL and return cleaned text content. Powered by Playwright headless browser. Returns title, content, word count.
| Name | Type | Req | Description |
|---|---|---|---|
| max_length | number | – | Max content length in chars (default: 10000) |
| url | string | yes | URL to scrape |
No output schema declared.
No examples provided.
screenshot_url ~87
Take a full-page screenshot of any URL. Returns base64-encoded PNG image.
| Name | Type | Req | Description |
|---|---|---|---|
| full_page | boolean | – | Capture full page scroll height (default: true) |
| height | number | – | Viewport height in pixels (default: 720) |
| url | string | yes | URL to screenshot |
| width | number | – | Viewport width in pixels (default: 1280) |
No output schema declared.
No examples provided.
search_web ~60
Search the web via Google and return organic results with titles, links, and snippets. Optionally returns answer box if available.
| Name | Type | Req | Description |
|---|---|---|---|
| num_results | number | – | Number of results to return (default: 10) |
| query | string | yes | Search query |
No output schema declared.
No examples provided.
How do I install the io.github.meltingpixelsai/zero-core-tools MCP server?
io.github.meltingpixelsai/zero-core-tools is a hosted endpoint at https://tools.rugslayer.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · tools.rugslayer.com
claude mcp add --transport http meltingpixelsai-zero-core-tools 'https://tools.rugslayer.com/mcp'
What is the io.github.meltingpixelsai/zero-core-tools MCP server?
io.github.meltingpixelsai/zero-core-tools is an MCP server listed in the public MCP registry as io.github.meltingpixelsai/zero-core-tools. Web scraping, code review, content gen, sentiment. Zero Core Tools. This page covers its hosted endpoint (https://tools.rugslayer.com/mcp).
Is the io.github.meltingpixelsai/zero-core-tools MCP server safe to use?
io.github.meltingpixelsai/zero-core-tools scores 77 out of 100 on VerifyMCP. 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.meltingpixelsai/zero-core-tools MCP server expose?
io.github.meltingpixelsai/zero-core-tools exposes 9 tools: list_tools, health, scrape_url, screenshot_url, extract_structured_data, and 4 more. Their descriptions and schemas cost roughly 584 tokens of context every time the server is loaded.
Does the io.github.meltingpixelsai/zero-core-tools MCP server require authentication?
No. We connected to io.github.meltingpixelsai/zero-core-tools without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.meltingpixelsai/zero-core-tools MCP server still maintained?
io.github.meltingpixelsai/zero-core-tools is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.