Developer Tools

boosthis.com

Provides developer authentication and account creation for the Boosthis platform.

1 endpoint26 known toolsFirst detected August 4, 2026Last detected September 4, 2026

ENDPOINT 1

https://www.boosthis.com/mcp

No auth detected

MCP server metadata

Name: Boosthis
Version: 1.0.0-alpha.164

Capabilities

tools

Server instructions

This Boosthis connection is not configured yet — no project key on this connection. This connection reached Boosthis and the server answered it, so nothing is down and there is nothing to retry. The handshake was completed deliberately, so that the real cause could be said in words rather than arriving as a server that cannot be reached. While the connection stays in this state its ADDRESS opens nothing: no project data, no kit, no rule text, and no fix text, and no project is identified. A tool call is refused with the same reason given here unless the call carries a credential of its own — an account token, or an install id with its read token — which that tool verifies for itself. The tool list is still visible because it is our own published catalogue and holds no customer data; the answers behind it are shut. WHY: No credential was sent with this request. A Boosthis AI connection carries its project key inside the server address it is added with: the address ends in a / followed by the project key (/mcp/<project>/<project-key>), and no other field has to be filled in. An address saved without that last part carries nothing to authenticate with, which is what is left when a tool keeps an older ?key= address as the part before the ? alone. WHAT A WORKING CONNECTION CARRIES: one address, with the project key already inside it — the address ends in a / followed by the project key (/mcp/<project>/<project-key>), and no other field has to be filled in. The key is part of the address itself, so a tool that saves only the site and the path keeps it. Once the address carries a key we accept, this connection comes back under the project's own name and every tool answers normally. WHO CARRIES THAT OUT: The address a connection was saved with is changed where it was added, so the repair belongs to whoever added this connection to their AI tool, who already holds the project key: the same connection, added again with the key as the last part of the address itself (/mcp/<project>/<project-key>) rather than after a ?. That is not a restatement of the address that just failed here: an address ending in ?key= is kept by some tools as the part before the ? alone, which drops the key and leaves exactly this state. A saved connection is changed where it was added: in most AI tools that is a settings screen a chat cannot reach, and where this one lives in a configuration file the assistant can open, correcting it there is the whole repair. Otherwise it goes back to the developer who added it rather than being worked around — an install completed by another route looks finished while this connection stays dead, with no rules, no fix text, no connection status, no update checks and no install verification, and nothing on either side saying so. WHO OPERATES THIS CONNECTION: Boosthis is a trade name of Veqtara Tech Company, registered in the Kingdom of Saudi Arabia under commercial registration number 7054832287. What it reads, what it never reads and what it never does unasked is public at https://www.boosthis.com/about — no key, no account.

Known tools 26

boosthis_list_rules

Every Boosthis performance rule available to this runtime, as ids and titles.

Inferred read-only

boosthis_get_rule

Full detail for one rule: title, when_to_apply, evidence, and - for a registered project - the prescriptive fix_template.

Inferred read-only

boosthis_get_integration_kit

A Boosthis kit for THIS project - no upload; the single-use address needs no key, include_files no shell.

Potential side effects

boosthis_get_removal_kit

Everything involved in removing Boosthis from this project: the removal sequence, every kit file, the package entries, the config file, the calls to strip, and the Boosthis entries in an AI tool's config.

Inferred read-only

boosthis_match_rules_for_code

Ranks Boosthis rules against a code snippet using each rule's id tokens and when_to_apply text, up to 8 candidates.

Inferred read-only

boosthis_check_for_update

Whether a newer Boosthis kit exists for this project, without fetching it: latest_version, update_available, comparison (behind/current/ahead/unknown), the changelog for every release behind, a severity (cosmetic/recommended/important/security) and a plain-language recommendation.

Inferred read-only

boosthis_verify_kit

Tamper-evidence check: re-hashes every vendored Boosthis-owned file against the shipped manifest.

Inferred read-only

boosthis_session_summary

Per-screen p50/p75/p95 and worst rating, worst screens first, with p99, spike ratio and stdev spread where the server has them.

Inferred read-only

boosthis_recent_samples

The most recent per-screen performance samples, newest first, optionally filtered to one screen.

Inferred read-only

boosthis_budgets

The auto-learned baseline (older p95) against the recent p95 for each screen, and which screens regressed.

Inferred read-only

boosthis_what_should_i_look_at_next

A triage ordering: the worst-rated and slowest screens first, each with a one-line reason.

Inferred read-only

boosthis_snapshot

The whole Boosthis bubble for one install - the latest upload: boot ladder, frame meters (Speed / Smoothness / Scroll / Stability / Render), Frustration and Idle axes, per-route rows, per-screen diagnosis, session summary and budgets.

Potential side effects

boosthis_crash_risk

The crash classes this app has already recorded - uncaught errors, unhandled rejections and caught render near-misses - newest first, each with an error name, a redacted top frame, an occurrence bucket and relatedRules, joined with the JS-thread (ANR-style) Stability summary and stabilityRules.

Inferred read-only

boosthis_full_stack_trace

One user action stitched across the stack as a waterfall of spans - layer, code-defined route label, duration, start offset, rating - plus a full-stack score against the shared TTI thresholds, a summary of where the time went, and slowestLayerRules.

Inferred read-only

boosthis_connection_status

What Boosthis knows about this account's installs (same check over plain HTTPS: GET /api/connection-status, project key as bearer): for each, the runtime, the state it is in, when it was last heard from, and what that state means.

Inferred read-only

boosthis_which_kits

Names which Boosthis kits this project needs, from the manifest file names already visible in it - package.

Inferred read-only

boosthis_verify_kit_install

Check a Boosthis kit's FILES ON DISK are byte-perfect (same check over plain HTTPS: POST https://www.

Potential side effects

boosthis_maintenance_mix

The Maintenance Mix: of the issues a project actually fixed, how many were fixed before users felt them (flagged by a Boosthis rule, app still healthy) versus after a crash or a visible poor rating.

Inferred read-only

boosthis_trend

One project's last 30 days: for each finished day, how many measurements arrived, the typical and worst-case screen time, how many were rated poor, new crashes, and alerts opened and closed - plus a plain-English verdict comparing the last 7 days with the 7 before.

Inferred read-only

boosthis_vigilance

One project's standing Vigilance verdict and every watch behind it, worst first: what each watches, what it says now, and the evidence (how many measurements, over which window, on which part, when the app was last heard from).

Inferred read-only

boosthis_jobs

Every scheduled job this project reports, each in one state: on time; late; app unheard, meaning reporting stopped before the run was due, so the job is not blamed; never reported a run; or no rhythm declared, so it is remembered and not watched.

Inferred read-only

boosthis_alerts

This account's Boosthis alerts in the same words the dashboard uses.

Inferred read-only

boosthis_promises

The standing promises this project's developer has recorded - what they want kept as the project changes.

Inferred read-only

boosthis_remember_promise

Saves something the developer wants kept true from now on - a screen that has to stay fast, a problem that must not come back, a rhythm that has to hold - as a promise on the project, in their words, so it survives into later sessions and other assistants.

Inferred read-only

boosthis_check_claim

Holds a sentence an assistant is about to say against what the running app actually did.

Inferred read-only

boosthis_release_check

How the last release held up, from the running app after it shipped.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.boosthis]
url = "https://www.boosthis.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "boosthis": {
      "type": "http",
      "url": "https://www.boosthis.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: boosthis
Remote MCP URL: https://www.boosthis.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "boosthis": {
      "url": "https://www.boosthis.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "boosthis": {
      "type": "http",
      "url": "https://www.boosthis.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "boosthis",
  "transport": "streamable-http",
  "url": "https://www.boosthis.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for boosthis.com was fetched 2026-08-21T10:39:55.006Z.

Trust status Trusted

boosthis.com is assessed as Trusted: Domain has an established technology history spanning over a year.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.