Tenpace Review Router MCP Server
io.github.Patrax/review-router
answering
Tenpace Review Router is answering right now. Last checked 4 min ago. It exposes 5 tools.
Human-authenticated setup for routing GitHub pull requests into the right Slack channel.
The linked repository no longer exists on GitHub — it was deleted or made private.
Uptime history
40 hours of history · worst hour 75%
40 hours agonow
100.0%
Uptime 24h
91 of 91 checks
5
Tools
read from the server
480 ms
Response time
average over 24h
open, no key
Access
streamable-http
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.
run in your terminal
claude mcp add review-router --transport http https://api.tenpace.com/mcp~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"review-router": {
"url": "https://api.tenpace.com/mcp"
}
}
}~/.codex/config.toml
[mcp_servers.review-router]
url = "https://api.tenpace.com/mcp".cursor/mcp.json
{
"mcpServers": {
"review-router": {
"url": "https://api.tenpace.com/mcp"
}
}
}.vscode/mcp.json
{
"mcpServers": {
"review-router": {
"url": "https://api.tenpace.com/mcp"
}
}
}Available tools 5
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
apply
apply_review_router_setup
Idempotently create or reconcile the route after the person completing setup signed in, claimed the current intent, and connected both providers.
preview
preview_review_router_setup
Read the exact current intent version and locked setup plan before asking a human to continue.
review
get_review_router_setup_status
Read structured progress and the next required human action.
send
send_review_router_test
After route application, idempotently send one real Slack setup message through the production delivery path.
start
start_review_router_setup
Create an inert GitHub-to-Slack setup plan and return one browser sign-in URL for the person completing setup.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://api.tenpace.com/mcp | streamable-http | answering | 522 ms | 4 min ago |
Tenpace Review Router — questions
Answers built from our own checks of this server.
What can Tenpace Review Router do?
It exposes 5 tools, read directly from the server on our last check. Among them: apply_review_router_setup, get_review_router_setup_status, preview_review_router_setup, send_review_router_test, start_review_router_setup. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
Is Tenpace Review Router 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 480 ms. The bar chart above shows every period we have measured.
Is Tenpace Review Router still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect Tenpace Review Router?
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.
Does Tenpace Review Router need an API key?
No. Tenpace Review Router completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Tenpace Review Router?
It answers our handshake in 480 ms on average, which is faster than 24% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.