Developer · Remote MCP server
Zero Core Tools
Web scraping, code review, content gen, sentiment. Zero Core Tools.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.meltingpixelsai/zero-core-tools- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Package
- npm
- Published
- 2026-04-30
- Updated
- 2026-04-30
- Publisher
- meltingpixelsai (GitHub) · 5 servers with pages here
- Website
- relayzero.ai
- Repository
- github.com/meltingpixelsai/harvey-tools
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://tools.rugslayer.com/mcp | None |
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @meltingpixels/zero-core-tools | 1.0.0 | HTTP |
How to connect Zero Core Tools
Zero Core Tools is a remote MCP server: there is nothing to install. Its endpoint is https://tools.rugslayer.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: @meltingpixels/zero-core-tools version 1.0.0. The package starts a local server that speaks MCP over Streamable HTTP; the client then connects to it by URL.
Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from meltingpixelsai (GitHub)
| Server | Runs |
|---|---|
| DrainbrainAI-powered Solana token rug pull detection with ML ensemble scoring and honeypot detection. | Local · stdio |
| RelayzeroAgent economy on Solana — USDC via x402. Ships a BuyerAgent SDK + relayzero pay CLI. | Remote & Local · HTTP |
| Zero Core IntelDrainBrain token safety, CORTEX trading signals, social trends. Zero Core Intel. | Remote & Local · HTTP |
| Zero Core VerifyPost-tx outcome verification via LLM-as-judge. Zero Core Verify. | Remote & Local · HTTP |
More developer servers
| Server | Runs |
|---|---|
| Zenrows MCPZenrows MCP server — Fetch, Extract, Batch, and Browser Sessions for AI coding assistants. | Remote & Local · HTTP, stdio |
| Zentric Protocol MCPPrompt injection + PII detection for LLM apps and agent pipelines. Deterministic, sub-25ms. | Local · stdio |
| ZephexMCP gateway with 10 tools for code analysis, architecture, package audit & security. | Remote · HTTP |
| Zephyr Scale MCPZephyr Scale on self-hosted Jira Server/DC: test cases, cycles, executions, plans and attachments. | Local · stdio |
| ZeroCMSAI-native Git-based CMS for Astro. Create and publish content in the browser, without learning git. | Remote · HTTP |
| Zeroidagent MCPA paid remote MCP for ZeroID, built to return verdicts, receipts, usage logs, and audit-ready JSON. | Remote · HTTP |
| Zerolangcompiler MCPA paid remote MCP for ZeroLang, built to return verdicts, receipts, usage logs, and audit-ready JSON. | Remote · HTTP |