Developer · Remote MCP server
Opencrater MCP
Monetize your MCP server or CLI: live OpenCrater network stats + how maintainers earn USDC.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.open-crater/opencrater-mcp- Version
- 0.1.1
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-06-23
- Updated
- 2026-06-23
- Publisher
- open-crater (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/open-crater) · how
- Repository
- github.com/open-crater/opencrater-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://opencrater.to/mcp | None |
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 200)
- Handshake
- opencrater 0.2.0 · protocol 2025-06-18
- Tools discovered
- 3:
opencrater_network_stats,opencrater_supported_tools,opencrater_get_started - Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | opencrater-mcp | 0.1.1 | stdio |
How to connect Opencrater MCP
Opencrater MCP is a remote MCP server: there is nothing to install. Its endpoint is https://opencrater.to/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: opencrater-mcp version 0.1.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y opencrater-mcp@0.1.1.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"opencrater-mcp": {
"command": "npx",
"args": [
"-y",
"opencrater-mcp@0.1.1"
]
}
}
}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 |
|---|---|
| OpenClaw FinOpsVerified cloud cost forecasting for AI agents. AWS, GCP, Azure pricing matrix. | Remote · HTTPLive check: sign-in required |
| Openclaw Health MCPMCP server for OpenClaw deployment health: gateway, resources, errors, skills, upgrades, disk. | Local · stdio |
| opencode subagentsRun Claude Code subagents on cheaper opencode models (DeepSeek, opencode Go) with native parity. | Local · stdio |
| Opencode WorkbenchProvision an OpenCode workbench and MCP stack on any Linux box, local or over SSH. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| Opendesignguard MCPPaid remote MCP for agent design system guard MCP, structured receipts, audit logs, and reviewer-rea. | Remote · HTTPLive check: ✗ no handshake |
| OpenDocsWrite, organize and publish documentation sites, help centers and SOPs on OpenDocs.cloud. | Remote · HTTPLive check: sign-in required |
| Openflowkit MCPLocal-first OpenFlowKit diagramming tools for Claude, Cursor, Windsurf & other MCP clients. | Local · stdio |
| Opengate MCPCheck whether an AI answer is grounded in its context - deterministic, no LLM judge. | Local · stdio |