Developer · Remote MCP server
Chartwire
Generate chart code (Recharts, Chart.js, ECharts, Plotly) from a prompt.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.outturndev/chartwire- Version
- 0.1.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-05-13
- Updated
- 2026-05-13
- Publisher
- outturndev (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/outturndev) · how
- Website
- chartwire.helpfulbutton140.workers.dev
- Repository
- github.com/outturndev/chartwire
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://chartwire.helpfulbutton140.workers.dev/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401
- Checked on
- 2026-10-05
How to connect Chartwire
Chartwire is a remote MCP server: there is nothing to install. Its endpoint is https://chartwire.helpfulbutton140.workers.dev/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.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. 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 developer servers
| Server | Runs |
|---|---|
| ChapaRead, compare, and verify public developer impact profiles and Chapa badges. | Remote · HTTPLive check: ✓ handshake |
| ChaprolaServerless API backend: query, JOIN, pivot, batch ops, email, FHIR, programs via HTTP. | Local · stdio |
| chargehandRuns coding-agent workers on a codebase question; every claim in the answer carries evidence. | Local · stdio |
| ChargerDojoOCPI versions, what changed between them, and which modules and journeys ChargerDojo tests. | Remote · HTTPLive check: ✓ handshake |
| ChassisScaffold an Express 5 + TypeScript backend: database, auth, optional Next.js front end. | Local · stdio |
| ChatCrystalLocal-first AI PKM memory for coding conversations. | Local · stdio |
| ChatRailInspect WhatsApp connections, groups, message delivery, schedules and webhooks in ChatRail. | Remote · HTTPLive check: sign-in required |
| cheapestinference.comDiscover unlimited LLM inference pools, get USDC quotes, subscribe on Base, check key status. | Remote · HTTPLive check: ✓ handshake |