Developer · Local MCP server
Rekt
REKT Store - browse and buy REKT drinks with AI-discounted pricing from any MCP client.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.osfrekt/rekt- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-03-24
- Updated
- 2026-03-24
- Publisher
- osfrekt (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/osfrekt) · how
- Repository
- github.com/osfrekt/rekt-store
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | rekt-mcp-server | 1.0.0 | stdio |
How to connect Rekt
Rekt runs locally from a Node.js package published to the npm registry: rekt-mcp-server version 1.0.0. 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 rekt-mcp-server@1.0.0. It reads the environment variable API_BASE_URL; set it in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"rekt": {
"command": "npx",
"args": [
"-y",
"rekt-mcp-server@1.0.0"
],
"env": {
"API_BASE_URL": "<value>"
}
}
}
}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 developer servers
| Server | Runs |
|---|---|
| RegiaBI chartsChart code that fits your data first try, as source you own: you pay to author it, never to run it. | Local · stdio |
| RegulaOffline AI governance code indicators (EU AI Act, Korea, Colorado). Indication, not legal advice. | Local · stdio |
| Regulatory MonitorFederal Register monitoring and regulations.gov tracking. 4 MCP tools for regulatory compliance. | Remote · HTTPLive check: ✗ no handshake |
| Regulatory SignalsAudit GitHub repos for security, compliance, and EU AI Act exposure from Claude or Cursor. | Local · stdio |
| RelayMCP relay server for Claude Desktop <-> Claude Code communication. | Local · stdio |
| RelayShield Security IntelligenceBreach, SIM swap, infostealer, domain lookalikes, MCP registry risk, prompt-injection detection. | Local · stdio |
| RelaystationPay-per-call agent infrastructure: file storage & handoff, compute tools, messaging, e-sign, KYC. | Remote · HTTPLive check: ✓ handshake |
| Release GatePre-deploy security auditor for AI agent code - the risks generic SAST misses. | Local · stdio |