RunBoth
REMOTE · RUNBOTH-AGENT-MGBXVS4LOQ-UC.A.RUN.APP
Ask runboth.dev in plain language: what RunBoth does, how to install it, and its limits.
Available components
Last scanned (5 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Testing and QA
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability65
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 681 tokens (~227/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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.
- 16 Oct 26 +5
- Stability: fail → pass ▲ security
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 56 to 59.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 46 to 53.
- 10 Oct 26 +2
No change was recorded against any check on this day. Stability & Change Management went from 36 to 46.
- 7 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 29 to 36.
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 22 to 26.
- 28 Sept 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
- 25 Sept 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
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 5 Nov 2026 · Probed https://runboth-agent-mgbxvs4loq-uc.a.run.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.a.run.app | CN=WR2,O=Google Trust Services,C=US | 7 Oct 2026 | 30 Dec 2026 | ECDSA 256 | SHA256-RSA | 53da11951e5eb49012fb872c3cb3e54d |
| SANs: *.a.run.app, run.app, *.africa-south1.run.app, *.asia-east1.run.app, *.asia-east2.run.app, *.asia-northeast1.run.app, *.asia-northeast2.run.app, *.asia-northeast3.run.app, *.asia-south1.run.app, *.asia-south2.run.app, *.asia-southeast1.run.app, *.asia-southeast2.run.app and 93 more | ||||||
| CN=WR2,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a07c4cded100ad9d66a5107b98 |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of runboth-agent-mgbxvs4loq-uc.a.run.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| run.app. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://runboth-agent-mgbxvs4loq-uc.a.run.app/mcp | Verified | 200 | |
| http (plaintext) | http://runboth-agent-mgbxvs4loq-uc.a.run.app/mcp | HTTPS enforced | 302 | https://runboth-agent-mgbxvs4loq-uc.a.run.app/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 →
ask ~240
Ask runboth.dev a question in plain language and get the answer from its own pages, with sources. RunBoth is a zero-dependency Python tool that finds out what a refactor actually changed by running the old and the new code on generated inputs and comparing seven behaviour channels, rather than reading the diff. Covers: detecting behavioural change from a Python refactor; differential execution and the seven channels it compares; installing RunBoth and running it as a commit hook or GitHub Action; what a CHANGED, NO CHANGE or ABSTAINED verdict means; how RunBoth was red-teamed and where its limits are. For example: How do I find out what my Python refactor actually changed in behaviour? Answers come back as ranked pages from runboth.dev with a URL, a score and a one-line reason each.
| Name | Type | Req | Description |
|---|---|---|---|
| generate_mode | string | – | The type of response to generate |
| query | string | yes | The question, in plain language. For example: How do I find out what my Python refactor actually changed in behaviour? |
| site | array | – | Optional list of sites to search. If not provided, searches all configured sites |
No output schema declared.
No examples provided.
list_sites ~20
List the sites this endpoint answers for (runboth.dev).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
trust_lookup ~107
Look up what AI agents recorded after calling a website or an MCP endpoint: which capability they used, whether it worked, how long it took, and what they learned. Read-only, no key. Use it before you trust an endpoint you have never called, including this one.
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | A domain or endpoint URL, for example runboth.dev or https://host/mcp |
| top_k | integer | – | How many records to return, 1 to 25 |
No output schema declared.
No examples provided.
How do I install the RunBoth MCP server?
RunBoth is a hosted endpoint at https://runboth-agent-mgbxvs4loq-uc.a.run.app/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 · runboth-agent-mgbxvs4loq-uc.a.run.app
claude mcp add --transport http dev-runboth-agent 'https://runboth-agent-mgbxvs4loq-uc.a.run.app/mcp'
What is the RunBoth MCP server?
RunBoth is an MCP server listed in the public MCP registry as dev.runboth/agent. Ask runboth.dev in plain language: what RunBoth does, how to install it, and its limits. This page covers its hosted endpoint (https://runboth-agent-mgbxvs4loq-uc.a.run.app/mcp).
Is the RunBoth MCP server safe to use?
RunBoth scores 73 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 RunBoth MCP server expose?
RunBoth exposes 3 tools: ask, list_sites, trust_lookup. Their descriptions and schemas cost roughly 367 tokens of context every time the server is loaded.
Does the RunBoth MCP server require authentication?
No. We connected to RunBoth without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the RunBoth MCP server still maintained?
RunBoth is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.