TOS-Slayer MCP Server

by evozim Your server? Claim it

answering

TOS-Slayer is answering right now. Last checked 9 min ago.

Uptime history 48 days of history · worst day 99%

48 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

96 ms

Response time

average over 24h

authentication required

Access

sse

Nothing serious here today

Today is the operative word: we check TOS-Slayer every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add tos-slayer --transport http https://tos-slayer-mcp.vercel.app/api/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "tos-slayer": {
      "url": "https://tos-slayer-mcp.vercel.app/api/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.tos-slayer]
url = "https://tos-slayer-mcp.vercel.app/api/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "tos-slayer": {
      "url": "https://tos-slayer-mcp.vercel.app/api/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "tos-slayer": {
      "url": "https://tos-slayer-mcp.vercel.app/api/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Endpoints

URL	Transport	State	Latency	Checked
https://tos-slayer-mcp.vercel.app/api/mcp	sse	needs auth	96 ms	9 min ago

Alternatives to TOS-Slayer

same job, measured the same way

Configcat

by configcat

Enables AI agents to interact with ConfigCat, a feature flag service for teams.

953 installs/wk local only

ClaudeR - RStudio MCP Server

by imnmv

Connect RStudio to AI assistants for interactive R coding and data analysis.

1 670 installs/wk local only

Terms

by theluckystrike

Reusable contract terms and clauses assembled into a Word docx with variables filled.

local only

CLIO Darshan

by iowarp

Darshan I/O profiler MCP server for analyzing I/O trace files

local only

Kaseya BMS MCP

by servosity

CLI and MCP server for Kaseya BMS PSA: tickets, CRM, contracts, finance, and offline analytics.

local only

Contract Clause Library Assemble

by bestremotetools

Assemble a contract from a searchable clause library, with variables filled in or flagged as missing

local only

Hive Consult

by srotzin

Agent-to-agent reasoning-as-a-service: chain-of-thought, analysis, and decision support.

4 tools answering

Code Analyze MCP

by clouatre-labs

MCP server for code structure analysis using tree-sitter.

local only

TOS-Slayer — questions

Answers built from our own checks of this server.

Why is there no tool list for TOS-Slayer?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is TOS-Slayer working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 96 ms. The bar chart above shows every period we have measured.

How do I connect TOS-Slayer?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own credentials: it refuses anonymous clients.

Does TOS-Slayer need an API key?

Yes. Every time we knock, TOS-Slayer answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.

How fast is TOS-Slayer?

It answers our handshake in 96 ms on average, which is faster than 84% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.