Tenpace Review Router
REMOTE · API.TENPACE.COM · SCANNED AUG 3
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 →
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 Usability67
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (fair).Partial
- 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 Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · api.tenpace.com
claude mcp add --transport http patrax-review-router https://api.tenpace.com/mcp
[mcp_servers.patrax-review-router] url = "https://api.tenpace.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"patrax-review-router": {
"type": "remote",
"url": "https://api.tenpace.com/mcp",
"enabled": true
}
}
} openclaw mcp add patrax-review-router --url https://api.tenpace.com/mcp --transport streamable-http
mcp_servers:
patrax-review-router:
url: "https://api.tenpace.com/mcp" {
"mcpServers": {
"patrax-review-router": {
"type": "http",
"url": "https://api.tenpace.com/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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “start_review_router_setup” rewrote its description, which is the text the model reads security
- Tool “preview_review_router_setup” rewrote its description, which is the text the model reads security
- Tool “apply_review_router_setup” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.1.0 → 1.1.1 functional
- Server version: 1.0.0 → 1.1.0 functional
- Tool “apply_review_router_setup” changed its title: Apply approved Review Router setup → Apply Review Router setup cosmetic
- 1 Aug 26 70
First indexed and scored.
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 3 Aug 2026 · Probed https://api.tenpace.com/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=YE1,O=Let's Encrypt,C=US | 17 Jun 2026 | 15 Sept 2026 | ECDSA 256 | ECDSA-SHA384 | 578510d6bd58c0c555a14169ac7d4543d49 |
| SANs: *.tenpace.com, tenpace.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 |
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 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.tenpace.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.tenpace.com/mcp | HTTPS enforced | 308 | https://api.tenpace.com/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.
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.