Tenpace Review Router
REMOTE · API.TENPACE.COM · SCANNED SEP 20
Human-authenticated setup for routing GitHub pull requests into the right Slack channel.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 399 tokens (~66/item across 6 items; 5 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 79% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Tenpace Review Router MCP server?
Tenpace Review Router is a hosted endpoint at https://api.tenpace.com/v1/review-router/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.tenpace.com
claude mcp add --transport http tenpace-app-review-router 'https://api.tenpace.com/v1/review-router/mcp'
{
"mcpServers": {
"tenpace-app-review-router": {
"url": "https://api.tenpace.com/v1/review-router/mcp"
}
}
} {
"servers": {
"tenpace-app-review-router": {
"type": "http",
"url": "https://api.tenpace.com/v1/review-router/mcp"
}
}
} [mcp_servers.tenpace-app-review-router] url = "https://api.tenpace.com/v1/review-router/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"tenpace-app-review-router": {
"type": "remote",
"url": "https://api.tenpace.com/v1/review-router/mcp",
"enabled": true
}
}
} openclaw mcp add tenpace-app-review-router --url 'https://api.tenpace.com/v1/review-router/mcp' --transport streamable-http
mcp_servers:
tenpace-app-review-router:
url: "https://api.tenpace.com/v1/review-router/mcp" {
"McpServers": {
"tenpace-app-review-router": {
"Transport": "http",
"Url": "https://api.tenpace.com/v1/review-router/mcp"
}
}
} assistant mcp add tenpace-app-review-router -t streamable-http -u 'https://api.tenpace.com/v1/review-router/mcp'
{
"mcpServers": {
"tenpace-app-review-router": {
"type": "http",
"url": "https://api.tenpace.com/v1/review-router/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 1 Sept 26 0
- Stability: 0.97 → pass security
- 31 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 3 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://api.tenpace.com/v1/review-router/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=tenpace.com | CN=YE2,O=Let's Encrypt,C=US | 15 Aug 2026 | 13 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 55734cb63714ac04872a88b52af6a2eb6bc |
| SANs: *.tenpace.com, tenpace.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.tenpace.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| tenpace.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.tenpace.com/v1/review-router/mcp | Verified | 200 | |
| http (plaintext) | http://api.tenpace.com/v1/review-router/mcp | HTTPS enforced | 308 | https://api.tenpace.com/v1/review-router/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
apply_review_router_setup Apply Review Router setup ~59
Idempotently create or reconcile the route after the person completing setup signed in, claimed the current intent, and connected both providers.
| Name | Type | Req | Description |
|---|---|---|---|
| agentToken | string | yes | Secret returned at creation |
| setupId | string | yes | Setup-session ID |
No output schema declared.
No examples provided.
get_review_router_setup_status Get Review Router setup status ~44
Read structured progress and the next required human action.
| Name | Type | Req | Description |
|---|---|---|---|
| agentToken | string | yes | Secret returned at creation |
| setupId | string | yes | Setup-session ID |
No output schema declared.
No examples provided.
preview_review_router_setup Preview Review Router setup ~50
Read the exact current intent version and locked setup plan before asking a human to continue.
| Name | Type | Req | Description |
|---|---|---|---|
| agentToken | string | yes | Secret returned at creation |
| setupId | string | yes | Setup-session ID |
No output schema declared.
No examples provided.
send_review_router_test Send Review Router verification message ~52
After route application, idempotently send one real Slack setup message through the production delivery path.
| Name | Type | Req | Description |
|---|---|---|---|
| agentToken | string | yes | Secret returned at creation |
| setupId | string | yes | Setup-session ID |
No output schema declared.
No examples provided.
start_review_router_setup Start Review Router setup ~111
Create an inert GitHub-to-Slack setup plan and return one browser sign-in URL for the person completing setup.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotencyKey | string | – | – |
| preset | string | – | – |
| repository | string | yes | GitHub repository in owner/repository format |
| reviewerMentions | string | – | – |
| slackChannel | string | yes | Slack channel name, with or without # |
| slackWorkspace | string | – | Optional exact workspace name, Slack team ID, or Tenpace workspace ID |
No output schema declared.
No examples provided.
What is the Tenpace Review Router MCP server?
Tenpace Review Router is an MCP server listed in the public MCP registry as io.github.tenpace-app/review-router. Human-authenticated setup for routing GitHub pull requests into the right Slack channel. This page covers its hosted endpoint (https://api.tenpace.com/v1/review-router/mcp).
Is the Tenpace Review Router MCP server safe to use?
Tenpace Review Router scores 88 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Tenpace Review Router MCP server expose?
Tenpace Review Router exposes 5 tools: start_review_router_setup, get_review_router_setup_status, preview_review_router_setup, apply_review_router_setup, send_review_router_test. Their descriptions and schemas cost roughly 316 tokens of context every time the server is loaded.
Does the Tenpace Review Router MCP server require authentication?
No. We connected to Tenpace Review Router without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Tenpace Review Router MCP server still maintained?
Tenpace Review Router is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.