Loadster MCP server
com.loadster/loadster-mcploadster.comstreamable-httpv2.2.1Scanned
Load testing and synthetic monitoring platform: test with Playwright, Browser Bot, or Protocol Bots.
62 tools: 15 can delete or cancel things, 13 change things and 34 only read.
- Reads private data · 6
- Reads text others write · 7
- Can send data out · 0
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
15 tools here can delete or cancel things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Loadster MCP server can do
The Loadster MCP server is published by loadster.com, a domain the MCP Registry verified. It has 62 tools. It can delete or cancel things (15 tools: delete_dataset, update_dataset, delete_monitor, enable_monitor and 11 more) and create or change data (13 tools: append_dataset_rows, create_dataset, submit_feedback, create_monitor and 9 more). 34 tools only read.
6 tools read private data (get_scripting_api, get_dataset, list_datasets and 3 more); 7 tools bring in text other people can write (get_scripting_api, enable_monitor, get_monitor_cycle_detail and 4 more).
The fixed checks matched 2 findings (credentials-mention and tool-shadowing). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 13, 2026, version 2.2.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
62 tools
Deletes or cancels 15Claude Code: deny
delete_datasetDelete a dataset from a project.No findings
Why it is in this group
- The name "delete_dataset" says "delete": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Delete a dataset from a project.
Annotations the server declares
- title: Delete Dataset
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
delete_monitorDelete a Monitor from a project.No findings
Why it is in this group
- The name "delete_monitor" says "delete": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Delete a Monitor from a project. Its Incidents are deleted with it and it is removed from any status pages; the Script it played is left alone. To stop a Monitor running without losing it, use disable_monitor instead, which needs the "Launch" access level; below that level the user disables the Monitor in the Dashboard. Never delete a Monitor just to stop it.
Annotations the server declares
- title: Delete Monitor
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
delete_scenarioDelete a scenario from a project.No findings
Why it is in this group
- The name "delete_scenario" says "delete": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Delete a scenario from a project. The scripts its populations referenced are left alone.
Annotations the server declares
- title: Delete Scenario
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
delete_scriptDelete a script from a project.No findings
Why it is in this group
- The name "delete_script" says "delete": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Delete a script from a project.
Annotations the server declares
- title: Delete Script
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
delete_script_assetDelete a file attached to a script.No findings
Why it is in this group
- The name "delete_script_asset" says "delete": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Delete a file attached to a script.
Annotations the server declares
- title: Delete Script Asset
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
enable_monitorEnable a disabled Monitor so its Cycles run on its schedule.Reads text others writeNo findings
Why it is in this group
- The name "enable_monitor" says "enable": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Enable a disabled Monitor so its Cycles run on its schedule. Enabling starts a Cycle at once, and the result's startedCycleId names it; startedCycleId is absent when no Cycle started, because the Monitor was already enabled, recent Cycles reached the limit on immediate Cycles, or the start failed. An enabled Monitor runs Cycles unattended until disable_monitor stops it. Its Cycles burn Fuel unless the account has a plan that includes monitoring, which covers them up to its limits; get_documentation topic 'faqs/plan-or-fuel' explains how. Enable only after the user confirms in this conversation. Idempotent: on an enabled Monitor it changes nothing, starts no Cycle, and returns the current state. An unclaimed Trial is refused until the user creates an account.
Annotations the server declares
- title: Enable Monitor
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
import_scriptImport an open-source load test (JMeter .jmx, k6 .js, or Locust .py) into an existing script, converting it to Loadster commands.No findings
Why it is in this group
- The name "import_script" says "import": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Import an open-source load test (JMeter .jmx, k6 .js, or Locust .py) into an existing script, converting it to Loadster commands. An import may create script assets, datasets, and a scenario; replace=true also replaces the script's existing commands and variables. Returns action items to review. For OpenAPI/Swagger or Postman, read the spec yourself and build commands with create_script instead.
Annotations the server declares
- title: Import Script
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
launch_load_testLaunch a saved Scenario as a Load Test, exactly as stored.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Launch a saved Scenario as a Load Test, exactly as stored. Its Populations send real traffic to the user's site. Like the Dashboard's Launch button, it runs on the account's plan when get_scenario shows no Fuel estimate and runs the whole test on Fuel when it shows one. Read the Scenario with get_scenario first, tell the user the Fuel estimate range and the fuelBalance, or that the plan covers it when there is no estimate, and launch only with the user's approval. If the plan can't run the test right now, the refusal gives the reason and burns no Fuel, and the user can try to launch from the Dashboard instead. If the call times out, check list_load_tests before launching again. A Scenario with launchBlockers is refused, and the refusal lists them. Trial, plan, Fuel and other checks apply as in the Dashboard, and a refusal carries their message. The result carries the new Load Test's id, its stage and the Dashboard link; follow it with get_load_test_status and stop it with stop_load_test.
Annotations the server declares
- title: Launch Load Test
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
put_script_assetUpload or replace a script asset from base64 content.No findings
Why it is in this group
- The name "put_script_asset" says "put": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Upload or replace a script asset from base64 content. Use the path as the key a command references — e.g. set an HTTP command's requestBody to { "key": "<path>" } to give it a request body, or list the path in a browser upload step's files.
Annotations the server declares
- title: Put Script Asset
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
stop_load_testStop a Load Test.No findings
Why it is in this group
- The name "stop_load_test" says "stop": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Stop a Load Test. By default the stop is graceful, as the Dashboard's Stop button does: each bot finishes the iteration it is on before it stops, so the last iterations complete and are reported in full. With immediate set to true the Load Test is killed instead: bots stop mid-iteration, cutting their last iterations short, and the test ends sooner. Stop gracefully unless the user asks to kill the test or the target needs relief now; a Load Test already STOPPING gracefully can still be killed with immediate. A running Load Test moves to STOPPING and then ends; one that has not started yet is canceled either way. A Load Test that has already ended is refused. The result carries its stage after the stop; follow it with get_load_test_status, and read the Test Report with get_load_test_report once it has finished.
Annotations the server declares
- title: Stop Load Test
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
stop_scriptStop a running play.No findings
Why it is in this group
- The name "stop_script" says "stop": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Stop a running play. Errors if the run does not exist; once the stop takes effect, get_play_status reports the run as stopped.
Annotations the server declares
- title: Stop Script
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
update_datasetUpdate an existing dataset.No findings
Why it is in this group
- The name "update_dataset" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Update an existing dataset. Each of name, values, and tags is optional: a field left out keeps its stored value, so a rename leaves the table alone. Values sent become the entire table, so send the complete table including every row you want to keep; an empty table clears the rows. To add rows, call append_dataset_rows instead.
Annotations the server declares
- title: Update Dataset
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
update_load_test_notesReplace the notes on a finished Load Test's Test Report — the only thing on a Load Test this surface edits.No findings
Why it is in this group
- The name "update_load_test_notes" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Replace the notes on a finished Load Test's Test Report — the only thing on a Load Test this surface edits. Ask the user before writing: notes belong to the user, and advising on a test never requires writing them. The text sent becomes the report's entire notes, so first read the current notes with get_load_test_report and preserve the user's content in what you send.
Annotations the server declares
- title: Update Load Test Notes
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
update_monitorUpdate an existing Monitor's exposed configuration: name, Script, frequency, engine ids, failure and recovery thresholds, tags, and the acceptable-metric thresholds.No findings
Why it is in this group
- The name "update_monitor" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Update an existing Monitor's exposed configuration: name, Script, frequency, engine ids, failure and recovery thresholds, tags, and the acceptable-metric thresholds. Each is optional: a field left out keeps its stored value, and a list sent replaces the whole list, never merging into it. The thresholds object works the same way: left out, the limits stay as they are; sent, it replaces all of them, so a limit left out of it is cleared and an empty object clears every limit. Read the current configuration with get_monitor before changing the thresholds. Everything outside those fields is untouched: an update never changes whether the Monitor is enabled, and never touches its notification policies or maintenance windows, so a config edit cannot stop a running Monitor, start a stopped one, or unhook the user's alerting. To start a disabled Monitor, call enable_monitor at the "Launch" access level; below that level a call is refused, and the user enables it in the Dashboard at the returned link.
Annotations the server declares
- title: Update Monitor
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
update_scenarioUpdate an existing scenario.No findings
Why it is in this group
- The name "update_scenario" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Update an existing scenario. Each of name, populations, and tags is optional: a field left out keeps its stored value. Populations sent replace the whole list, never merging into it, so to change one, send the others alongside it, each with the id get_scenario reported, or they are dropped and the ones you send are new populations. The same save rules and summary as create_scenario apply.
Annotations the server declares
- title: Update Scenario
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
Changes things 13Claude Code: ask
append_dataset_rowsAdd rows to the end of an existing dataset, sending only the new rows — the rows already in the table stay as they are, so there is no need to read them first.No findings
Why it is in this group
- The description's first verb is "add": a word for a change.
Description, as the server wrote it Add rows to the end of an existing dataset, sending only the new rows — the rows already in the table stay as they are, so there is no need to read them first. Every row must have as many columns as the table already has; a row that doesn't is rejected and nothing at all is written. Appending to an empty dataset takes the column count from the first row.
Annotations the server declares
- title: Append Dataset Rows
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
create_datasetCreate a new dataset in a project.No findings
Why it is in this group
- The name "create_dataset" says "create": a word for a change.
Description, as the server wrote it Create a new dataset in a project. Loadster treats every row as data and addresses columns by zero-based index — a header row would be fed to bots like any other row, so don't add one when authoring values. Unless the user explicitly asked for a dataset, confirm with them before creating one.
Annotations the server declares
- title: Create Dataset
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
create_monitorCreate a Monitor in a project, initially disabled.No findings
Why it is in this group
- The name "create_monitor" says "create": a word for a change.
Description, as the server wrote it Create a Monitor in a project, initially disabled. An enabled Monitor runs on its schedule, unattended. Its Cycles burn Fuel unless the account has a plan that includes monitoring, which covers them up to its limits. Enable it with enable_monitor at the "Launch" access level; below that level a call is refused, and the user enables it in the Dashboard at the link the returned summary carries. Read the 'monitoring' topic before choosing a frequency or thresholds.
Annotations the server declares
- title: Create Monitor
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
create_projectCreate a project for the connected team and return its id, name, and dashboard link.No findings
Why it is in this group
- The name "create_project" says "create": a word for a change.
Description, as the server wrote it Create a project for the connected team and return its id, name, and dashboard link. Prefer an existing project: call list_projects first, and create a new one only if the team has none or the user explicitly asked for one. When unsure, ask the user before creating.
Annotations the server declares
- title: Create Project
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
create_scenarioCreate a scenario in a project — saving costs nothing and starts nothing.No findings
Why it is in this group
- The name "create_scenario" says "create": a word for a change.
Description, as the server wrote it Create a scenario in a project — saving costs nothing and starts nothing. Launch it with launch_load_test at the "Launch" access level; below that level a call is refused, and the user launches it from the Dashboard at the link. The save is refused for an engineId list_engines doesn't offer, a stage shorter than the minimum, or more bots or populations than the account allows, and the refusal names the limit. The summary's launchBlockers are reasons the user could not launch it right now; they never stop the save, so tell the user about a blocker instead of rewriting the scenario to avoid it. The 'load-test-scenarios' topic covers what the stages and ramps actually do.
Annotations the server declares
- title: Create Scenario
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
create_scriptCreate a new script in a project.No findings
Why it is in this group
- The name "create_script" says "create": a word for a change.
Description, as the server wrote it Create a new script in a project. Read the relevant get_documentation topics and use the schema tools first to build valid commands for the bot type. HTTP is a Protocol Bot script, BROWSER is a Browser Bot script, and PLAYWRIGHT is a Playwright script. "Browser script" is ambiguous: Browser Bot and Playwright are different types, so if the user's wording doesn't say which, ask before creating. Don't create multiple scripts of the same type for one task. Edit and reuse a script you created earlier in the session (same type, created by you, not used in a scenario or monitor elsewhere) instead of making a new one for a probe or a retry. Like every write on this surface, returns a summary — the server-assigned facts and a dashboard link — never the object you sent; the matching get tool reads it back.
Annotations the server declares
- title: Create Script
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
disable_monitorDisable a Monitor, stopping its scheduled Cycles and the Fuel or plan usage they bring; disabling closes the Monitor's open Incidents.No findings
Why it is in this group
- The name "disable_monitor" says "disable": a word for a change.
Description, as the server wrote it Disable a Monitor, stopping its scheduled Cycles and the Fuel or plan usage they bring; disabling closes the Monitor's open Incidents. Idempotent. Disabling, and enabling again with enable_monitor, both need the "Launch" access level; below that level a call is refused, and the user disables or re-enables the Monitor in the Dashboard at the link get_monitor returns.
Annotations the server declares
- title: Disable Monitor
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
duplicate_scriptDuplicate a script, optionally with a new name and into another project the token can access.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Duplicate a script, optionally with a new name and into another project the token can access. Returns the copy's summary.
Annotations the server declares
- title: Duplicate Script
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
play_scriptStart playing a saved script.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "start": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Start playing a saved script. Returns immediately with a run id and a queued status, since a play can take anywhere from a few seconds (HTTP) to several minutes (browser or Playwright); read the results with get_play_status.
Annotations the server declares
- title: Play Script
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
restore_script_revisionRestore a script to a past revision, saving that revision's commands as a new revision.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Restore a script to a past revision, saving that revision's commands as a new revision.
Annotations the server declares
- title: Restore Script Revision
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
submit_feedbackOptional.1 finding
Why it is in this group
- The name "submit_feedback" says "submit": a word for a change.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...rsation data: the user's prompts, their credentials, or anything from their account. Feedba..."
Description, as the server wrote it Optional. Sends a note about this tool surface to the Loadster team, who read it to fix what the surface got wrong. Nothing requires it and no task depends on it. A note is about the tools themselves: what worked, what was missing or confusing, what needed a workaround. It should not carry conversation data: the user's prompts, their credentials, or anything from their account. Feedback is at most 2000 characters; a longer submission is rejected rather than truncated.
Annotations the server declares
- title: Submit Feedback
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
update_projectRename a project and return its id, name, and dashboard link.No findings
Why it is in this group
- The name "update_project" says "update": a word for a change.
Description, as the server wrote it Rename a project and return its id, name, and dashboard link. The project's scripts, scenarios and other contents stay as they are. A name that another project of the team already has is refused. Every write against a user's existing data needs their explicit confirmation first.
Annotations the server declares
- title: Update Project
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
update_scriptUpdate an existing script.No findings
Why it is in this group
- The name "update_script" says "update": a word for a change.
Description, as the server wrote it Update an existing script. Each of name, type, commands, variables, and tags is optional: a field left out keeps its stored value, an empty list clears that list, and a non-empty list replaces the whole list, never merging into it. A script's type cannot be changed: type, if sent, must match the script's bot type, so to switch types create a new script of the desired type instead. Sending commands or variables saves a new revision; a name or tags alone save no revision. Read the script with get_script before changing it, never rebuild it from list_scripts. Every write against a user's existing data needs their explicit confirmation first.
Annotations the server declares
- title: Update Script
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Only reads 34Show 34 read-only tools
get_command_schemaGet the recursive schema for one command type, so you can build a valid command object.No findings
Why it is in this group
- The name "get_command_schema" says "get": a word for reading.
Description, as the server wrote it Get the recursive schema for one command type, so you can build a valid command object. Some fields carry a 'notes' string describing accepted keys that aren't reflectable, such as element action options and locator attributes.
Annotations the server declares
- title: Get Command Schema
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_datasetGet a single dataset's shape — name, row and column counts, tag names, dashboard link — plus a leading window of its rows: the first five in table order by default, more with offse…Reads private dataNo findings
Why it is in this group
- The name "get_dataset" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "get" and "table": it reads databases.
Description, as the server wrote it Get a single dataset's shape — name, row and column counts, tag names, dashboard link — plus a leading window of its rows: the first five in table order by default, more with offset and limit. Compare rowOffset and the rows returned against rowCount to see how much you are not looking at. Loadster serves every row to bots, but a user's imported data may still start with a header-looking row — don't assume either way; ask before treating or removing it.
Annotations the server declares
- title: Get Dataset
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_documentationList the Loadster manual's topics with their keys and URLs, or read up to 3 topics' text by key.No findings
Why it is in this group
- The name "get_documentation" says "get": a word for reading.
Description, as the server wrote it List the Loadster manual's topics with their keys and URLs, or read up to 3 topics' text by key. Pass one key as topic, or up to 3 keys as topics. Omit both to list every topic.
Annotations the server declares
- title: Get Documentation
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_exampleGet a small, valid worked example script for a bot type to use as a starting point.No findings
Why it is in this group
- The name "get_example" says "get": a word for reading.
Description, as the server wrote it Get a small, valid worked example script for a bot type to use as a starting point.
Annotations the server declares
- title: Get Example Script
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_incidentGet a single Incident: when it opened and closed, every notification that went out with its delivery outcome, the status events recorded on it, and the ids of the Cycles that opene…No findings
Why it is in this group
- The name "get_incident" says "get": a word for reading.
Description, as the server wrote it Get a single Incident: when it opened and closed, every notification that went out with its delivery outcome, the status events recorded on it, and the ids of the Cycles that opened and closed it. To reconstruct what happened, read those Cycles with get_monitor_cycle_detail, and cross-read the Monitor's configuration and its Script so the diagnosis names the concrete step, URL, or threshold at fault rather than a vague symptom. The 'monitoring' topic covers advising on thresholds or noise.
Annotations the server declares
- title: Get Incident
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_load_test_reportGet a finished Load Test's Test Report — aggregate totals, the error and advice picture behind the Dashboard's advice tile, per-Population outcomes, and each engine's average and p…No findings
Why it is in this group
- The name "get_load_test_report" says "get": a word for reading.
Description, as the server wrote it Get a finished Load Test's Test Report — aggregate totals, the error and advice picture behind the Dashboard's advice tile, per-Population outcomes, and each engine's average and peak CPU; an unfinished test answers with an error naming its status. The advice buckets and detection flags are heuristics, not a diagnosis of this test: where the totals, percentiles, per-URL counts and Populations contradict a bucket or a flag, or show something it never names, say so and follow the data. Before advising the user, read the get_documentation topic 'analyzing-test-results' and cross-read the Scenario and the played Scripts, so your advice names concrete elements — a specific URL, Population, bot count, or script step — instead of repeating the error buckets back.
Annotations the server declares
- title: Get Load Test Report
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_load_test_statusGet a Load Test's live status, as the Dashboard's live test view shows it: stage, elapsed time, Bots started, running, peak and planned per Population, Iterations, response time pe…No findings
Why it is in this group
- The name "get_load_test_status" says "get": a word for reading.
Description, as the server wrote it Get a Load Test's live status, as the Dashboard's live test view shows it: stage, elapsed time, Bots started, running, peak and planned per Population, Iterations, response time percentiles, throughput, errors by type, and each engine's region, online state and, while the test runs, current CPU percentage. Use it to tell the user how a test in progress is going, and to tell an overloaded engine from a slow target. Call it no more often than every 10 seconds; the numbers do not move faster than that. Once the test is over, the status says so in its note; stop polling and read the Test Report with get_load_test_report.
Annotations the server declares
- title: Get Load Test Status
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_load_test_url_timingsGet a finished Load Test's response times per URL, slowest first by the total time all hits to the URL took: hits, average, minimum and maximum response time, and average time to f…Reads text others writeNo findings
Why it is in this group
- The name "get_load_test_url_timings" says "get": a word for reading.
What it can reach
- untrusted-inputThe name "get_load_test_url_timings" says "get" and "url": it reads web pages, which anyone can write.
- untrusted-inputThe description's first sentence says "get" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it Get a finished Load Test's response times per URL, slowest first by the total time all hits to the URL took: hits, average, minimum and maximum response time, and average time to first byte, in milliseconds. Use it to name the slow pages behind the percentiles in get_load_test_report. Compare urlOffset and the URLs returned against totalUrls to see how much you have not read; page on with offset.
Annotations the server declares
- title: Get Load Test URL Timings
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_monitorGet a single Monitor's full configuration and dashboard link.No findings
Why it is in this group
- The name "get_monitor" says "get": a word for reading.
Description, as the server wrote it Get a single Monitor's full configuration and dashboard link. Configuration only — a Monitor's steps are its Script's commands, so read them with get_script. To start a disabled Monitor, call enable_monitor at the "Launch" access level; below that level a call is refused, and the user enables it in the Dashboard at the link. The 'monitoring' topic covers what a Monitor's configuration should be.
Annotations the server declares
- title: Get Monitor
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_monitor_cycle_detailGet one Cycle in full: status, failure message, the engine it ran from, timestamps, and every metric the Monitor's thresholds judge.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_monitor_cycle_detail" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "get" and "message": it reads messages.
- untrusted-inputThe description's first sentence says "get" and "message": it reads messages, which other people can write.
Description, as the server wrote it Get one Cycle in full: status, failure message, the engine it ran from, timestamps, and every metric the Monitor's thresholds judge. Its scriptRunId is a played run like any other — pass it with the project id to get_play_status for per-step results and get_step_detail for the exact request and response that failed — and it names the scriptId it checked, so cross-read the Script and point advice at a concrete step or URL. Works with a cycle id from list_monitor_cycles or from an Incident's cycle references. The 'monitoring' topic covers what the thresholds should be.
Annotations the server declares
- title: Get Monitor Cycle Detail
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_monitoring_summaryGet the Monitoring Summary for a project: the aggregate health picture across its Monitors over a period, defaulting to the last 7 days, with per-Monitor and per-day aggregates for…No findings
Why it is in this group
- The name "get_monitoring_summary" says "get": a word for reading.
Description, as the server wrote it Get the Monitoring Summary for a project: the aggregate health picture across its Monitors over a period, defaulting to the last 7 days, with per-Monitor and per-day aggregates for trends (times in seconds; performance score 0-100). Drill down instead of asking for more: list_incidents for what opened and closed in the period, list_monitor_cycles for one Monitor's individual Cycles. Read the 'monitoring' topic before interpreting uptime or health for the user.
Annotations the server declares
- title: Get Monitoring Summary
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_play_statusGet the current state of a play, with per-step results and log that fill in as it progresses, optionally waiting for it to finish.No findings
Why it is in this group
- The name "get_play_status" says "get": a word for reading.
Description, as the server wrote it Get the current state of a play, with per-step results and log that fill in as it progresses, optionally waiting for it to finish. After play_script, call this with waitSeconds instead of sleeping between polls; the results are complete once running is false. Each step's has-flags (hasBody, hasLog, and their siblings) say which get_step_detail parts would return something for that step, so drill down only where a flag is true. On a Playwright run the whole runner log belongs to the command step that ran the spec file — hasLog points there. A step's screenshotKeys are in capture order; a Playwright step lists the script's own page.screenshot calls in order, with the runner's final screenshot of the test last.
Annotations the server declares
- title: Get Play Status
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_scenarioGet a single scenario including its Populations, plus a dashboard link and its launch readiness: the account's fuelBalance; launchBlockers, where an empty list means it can launch …No findings
Why it is in this group
- The name "get_scenario" says "get": a word for reading.
Description, as the server wrote it Get a single scenario including its Populations, plus a dashboard link and its launch readiness: the account's fuelBalance; launchBlockers, where an empty list means it can launch as it stands; and estimatedFuelLow and estimatedFuelHigh, the low and high ends of the Fuel estimate the Dashboard shows. The estimate is present whenever the test would burn Fuel, which is every test on an account without a plan, and on one with a plan, any test the plan does not cover; launch_load_test then runs the whole test on Fuel. Without an estimate, it runs on the account's plan and burns no Fuel. get_documentation topic 'faqs/plan-or-fuel' explains when a plan or Fuel applies. A field left out of a population is at its default: iterations and iterationsPerUser unlimited, aggressionMultiplier 1.0, and bandwidth unthrottled. Read get_documentation topic 'load-test-scenarios' for what the stages and ramps actually do.
Annotations the server declares
- title: Get Scenario
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_screenshotFetch a screenshot captured during a play as a viewable image.No findings
Why it is in this group
- The name "get_screenshot" says "get": a word for reading.
Description, as the server wrote it Fetch a screenshot captured during a play as a viewable image. Use the screenshotKey from a step in get_play_status.
Annotations the server declares
- title: Get Screenshot
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_scriptGet a single script including its full command list and variables, plus a dashboard link.No findings
Why it is in this group
- The name "get_script" says "get": a word for reading.
Description, as the server wrote it Get a single script including its full command list and variables, plus a dashboard link. The variables are the script's dataset bindings — the ${...} references in its commands resolve through them.
Annotations the server declares
- title: Get Script
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_script_assetRead a script asset's content as base64.No findings
Why it is in this group
- The name "get_script_asset" says "get": a word for reading.
Description, as the server wrote it Read a script asset's content as base64.
Annotations the server declares
- title: Get Script Asset
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_script_revisionGet a specific past revision of a script, including its commands, so you can inspect or diff it.No findings
Why it is in this group
- The name "get_script_revision" says "get": a word for reading.
Description, as the server wrote it Get a specific past revision of a script, including its commands, so you can inspect or diff it.
Annotations the server declares
- title: Get Script Revision
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_scripting_apiList the scripting API scopes (bot, http, browser, ...) available in code blocks, or fetch one scope's members with their signatures and docs.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_scripting_api" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "doc": it reads documents.
- untrusted-inputThe description's first sentence says "list" and "http": it reads web pages, which anyone can write.
Description, as the server wrote it List the scripting API scopes (bot, http, browser, ...) available in code blocks, or fetch one scope's members with their signatures and docs.
Annotations the server declares
- title: Get Scripting API
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_step_detailRead the payloads get_play_status leaves out — response bodies, headers, captured values, console messages, network activity, page HTML, logs — for one or more steps of a play, cho…Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_step_detail" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "read" and "message": it reads messages.
- untrusted-inputThe description's first sentence says "read" and "message": it reads messages, which other people can write.
Description, as the server wrote it Read the payloads get_play_status leaves out — response bodies, headers, captured values, console messages, network activity, page HTML, logs — for one or more steps of a play, choosing the parts per call. Ask for several steps at once: a failing request and the earlier step that captured the token it used is one call. Use this instead of adding a validator or code block to the script just to echo a response back to yourself. Parts are bot-type-shaped, and asking for a part a run has no source for returns an error naming what it does have.
Annotations the server declares
- title: Get Step Detail
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_variable_schemaGet the schema for binding a script variable to a dataset, including the accepted update and selection strategies.No findings
Why it is in this group
- The name "get_variable_schema" says "get": a word for reading.
Description, as the server wrote it Get the schema for binding a script variable to a dataset, including the accepted update and selection strategies. A variable is a named row cursor bound to one whole dataset by dataSetId: on each pull it holds an entire row, advancing per occurrence, per iteration, or per bot ('vuser') depending on updateStrategy, with rows taken sequentially or randomly per selectionStrategy. Reference it as ${name} in command fields or bot.getVariable('name') in Playwright code. After changing bindings or references, run validate_script to cross-check them.
Annotations the server declares
- title: Get Variable Schema
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_command_typesList the command (step) types available for a bot type, with a description and the bot types each applies to.No findings
Why it is in this group
- The name "list_command_types" says "list": a word for reading.
Description, as the server wrote it List the command (step) types available for a bot type, with a description and the bot types each applies to. Use this before authoring commands.
Annotations the server declares
- title: List Command Types
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_datasetsList the datasets in a project with their id, name, row/column counts, and tag names (without the full value table).Reads private dataNo findings
Why it is in this group
- The name "list_datasets" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "table": it reads databases.
Description, as the server wrote it List the datasets in a project with their id, name, row/column counts, and tag names (without the full value table). Tags are shared across the team: to tag an item, reuse a name the list tools already report, and create a new tag only when the user asks for one.
Annotations the server declares
- title: List Datasets
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_enginesList everywhere a population can run, with the customer's own limits a scenario is written against.No findings
Why it is in this group
- The name "list_engines" says "list": a word for reading.
Description, as the server wrote it List everywhere a population can run, with the customer's own limits a scenario is written against. Each entry's id is what a population's engineId names — never invent one. Type CLOUD is a single Loadster cloud region, WILDCARD is a pattern ('north-america-*', '*') that lets Loadster pick a region inside it when the test launches, and PRIVATE is one of the customer's own Loadster Engines, the only kind that can reach a host on their network. The per-population caps and stage bounds are enforced when a scenario is saved; capacities, locked regions, and the per-region and per-engine caps matter only at launch and never stop a save. While limits.freeTrialCustomer is true, an entry with locked true can be saved onto but not launched from, so put a trial's populations on an entry with locked false and keep the scenario's peak within limits.maxFreeTrialBotsPerTest.
Annotations the server declares
- title: List Engines
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_incidentsList a project's Incidents — open ones first, then the most recently closed; unresolved only by default, with includeResolved for incident archaeology over a since/until window and…No findings
Why it is in this group
- The name "list_incidents" says "list": a word for reading.
Description, as the server wrote it List a project's Incidents — open ones first, then the most recently closed; unresolved only by default, with includeResolved for incident archaeology over a since/until window and monitorId to ask about one Monitor. An Incident opens when a Monitor's consecutive failing Cycles reach its failure threshold, and closes after enough consecutive passes, or when the Monitor is disabled. Rows are lean; read one Incident's notifications, statuses, and cycle references with get_incident. The 'monitoring' topic covers how Incidents notify.
Annotations the server declares
- title: List Incidents
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_load_testsList a project's Load Tests, a window of summary rows at a time: the ones in progress first, each with its stage, then the finished ones, newest first.No findings
Why it is in this group
- The name "list_load_tests" says "list": a word for reading.
Description, as the server wrote it List a project's Load Tests, a window of summary rows at a time: the ones in progress first, each with its stage, then the finished ones, newest first. A Load Test is a run of a Scenario at scale by many bots; launch_load_test launches one and stop_load_test stops one, at the "Launch" access level; below that level a call to either is refused and the user does it in the Dashboard. Nothing on this surface deletes one. Follow a test in progress with get_load_test_status; read a finished test's Test Report with get_load_test_report.
Annotations the server declares
- title: List Load Tests
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_monitor_cyclesList a Monitor's Cycles, newest first — one row per Cycle with its status, timestamps, the engine id it ran from, and headline response times; a Cycle with no status yet is schedul…No findings
Why it is in this group
- The name "list_monitor_cycles" says "list": a word for reading.
Description, as the server wrote it List a Monitor's Cycles, newest first — one row per Cycle with its status, timestamps, the engine id it ran from, and headline response times; a Cycle with no status yet is scheduled or still running. Window with since/until and limit to spot patterns — flapping around a threshold, slow drift, failures from one region — then drill into one Cycle's full metrics and failure message with get_monitor_cycle_detail. The 'monitoring' topic explains what each status means.
Annotations the server declares
- title: List Monitor Cycles
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_monitoring_locationsList everywhere a Monitor's Cycles can run from.No findings
Why it is in this group
- The name "list_monitoring_locations" says "list": a word for reading.
Description, as the server wrote it List everywhere a Monitor's Cycles can run from. Each entry's id is what a Monitor's engineIds names — never invent one. Type CLOUD is one of Loadster's shared monitoring locations, and PRIVATE is one of the customer's own Loadster Engines, the only kind that can reach a host on their network. Monitoring locations are their own set, not the load test regions list_engines offers. Read this before create_monitor or update_monitor.
Annotations the server declares
- title: List Monitoring Locations
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_monitorsList the Monitors in a project.No findings
Why it is in this group
- The name "list_monitors" says "list": a word for reading.
Description, as the server wrote it List the Monitors in a project. A Monitor is a scheduled, low-volume check that runs a Script on a frequency to verify health and alert on failure; each execution is a Cycle. Each row is a summary without the thresholds and engine ids; read one Monitor's full configuration with get_monitor. Read get_documentation topic 'monitoring' for how Monitors, Cycles, and Incidents behave. Tags are shared across the team: to tag an item, reuse a name the list tools already report, and create a new tag only when the user asks for one.
Annotations the server declares
- title: List Monitors
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_projectsList the Loadster projects the current token can access, each with its id and name.1 finding
Why it is in this group
- The name "list_projects" says "list": a word for reading.
Findings
- Warn
The description contains "Every other tool", wording about other tools or servers.
What this check looks forMatched text
description: "...can access, each with its id and name. Every other tool takes one of these ids. When the team h..."
Description, as the server wrote it List the Loadster projects the current token can access, each with its id and name. Every other tool takes one of these ids. When the team has no projects, the result says so and points at create_project. Prefer an existing project: call list_projects first, and create a new one only if the team has none or the user explicitly asked for one. When unsure, ask the user before creating.
Annotations the server declares
- title: List Projects
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_scenariosList the scenarios in a project with their id, name, version, population count, peak bots, total duration in milliseconds, and tag names — without the populations, fuel estimate, a…No findings
Why it is in this group
- The name "list_scenarios" says "list": a word for reading.
Description, as the server wrote it List the scenarios in a project with their id, name, version, population count, peak bots, total duration in milliseconds, and tag names — without the populations, fuel estimate, and launch blockers get_scenario reports. A Scenario is a saved load test configuration: a named list of Populations (the Dashboard calls them "bot groups"), each of which runs one script with its own load shape on one engine or region. Saving a scenario costs nothing and runs nothing. Launch it with launch_load_test at the "Launch" access level; below that level a call is refused, and the user launches it from the Dashboard. Tags are shared across the team: to tag an item, reuse a name the list tools already report, and create a new tag only when the user asks for one.
Annotations the server declares
- title: List Scenarios
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_script_assetsList the files attached to a script (request bodies, upload files, Playwright support files).Reads private dataNo findings
Why it is in this group
- The name "list_script_assets" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "file": it reads files.
Description, as the server wrote it List the files attached to a script (request bodies, upload files, Playwright support files). Each path is the key a command references.
Annotations the server declares
- title: List Script Assets
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_script_revisionsList a script's past revisions (newest first) with version, save time, author, and step count.No findings
Why it is in this group
- The name "list_script_revisions" says "list": a word for reading.
Description, as the server wrote it List a script's past revisions (newest first) with version, save time, author, and step count.
Annotations the server declares
- title: List Script Revisions
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_scriptsList the scripts in a project with their id, name, bot type, step count, current revision version, and tag names (without the full command list).No findings
Why it is in this group
- The name "list_scripts" says "list": a word for reading.
Description, as the server wrote it List the scripts in a project with their id, name, bot type, step count, current revision version, and tag names (without the full command list). Tags are shared across the team: to tag an item, reuse a name the list tools already report, and create a new tag only when the user asks for one.
Annotations the server declares
- title: List Scripts
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
validate_scriptStructurally validate a list of commands for a bot type before saving or playing, reporting any issues by command index.No findings
Why it is in this group
- The name "validate_script" says "validate": a word for reading.
Description, as the server wrote it Structurally validate a list of commands for a bot type before saving or playing, reporting any issues by command index. Pass the script's variables as well and it also cross-checks the bindings against the ${...} and bot.getVariable reads in the commands, warning about a read nothing supplies, a binding nothing reads, and a per-occurrence variable read more than once in an iteration. Warnings never make a script invalid and never stop a save — all three are legal scripts.
Annotations the server declares
- title: Validate Script
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data6
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write7
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:41 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 28
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://api.loadster.com/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://loadster.com
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 28 tools that change things (15 destructive, 13 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.loadster.com/mcp: tools/list returned 62 tools to an anonymous client, including delete_dataset (destructive), update_dataset (destructive), delete_monitor (destructive), enable_monitor (destructive), update_monitor (destructive) and 23 more
Posture changes
- Nov 13, 2026
- HTTP status of an anonymous initialize: 401 to 200
- tools/list served without credentials: no to yes
- Tools that change things, listed without credentials: 0 to 28
- Protocol version: none to 2025-06-18
- WWW-Authenticate on 401: yes to not observed
- resource_metadata in WWW-Authenticate: https://api.loadster.com/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://api.loadster.com to https://loadster.com
Findings
Matches of fixed checks, with the text they matched.
- Warnlist_projects
The description contains "Every other tool", wording about other tools or servers.
What this check looks forMatched text
description: "...can access, each with its id and name. Every other tool takes one of these ids. When the team h..."
- Infosubmit_feedback
The description mentions "credentials".
What this check looks forMatched text
description: "...rsation data: the user's prompts, their credentials, or anything from their account. Feedba..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools2 changed.~2 changedView diff
- Changed:stop_load_testDeletes or cancelsannotations
- Changed:stop_scriptDeletes or cancelsannotations
PostureRemote posture changed. HTTP status of an anonymous initialize: 401 -> 200; tools/list served without credentials: no -> yes; Tools that change things, listed without credentials: 0 -> 28 (and 4 more).View diff
- HTTP status of an anonymous initialize: 401 to 200
- tools/list served without credentials: no to yes
- Tools that change things, listed without credentials: 0 to 28
- Protocol version: none to 2025-06-18
- WWW-Authenticate on 401: yes to not observed
- resource_metadata in WWW-Authenticate: https://api.loadster.com/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://api.loadster.com to https://loadster.com
Tools8 changed.~8 changedView diff
- Changed:create_monitorChanges thingsdescription
- Changed:create_scenarioChanges thingsdescription
- Changed:delete_monitorDeletes or cancelsdescription
- Changed:disable_monitorChanges thingsdescription
- Changed:get_monitorOnly readsdescription
- Changed:list_load_testsOnly readsdescription
- Changed:list_scenariosOnly readsdescription
- Changed:update_monitorDeletes or cancelsdescription
Install
Pinned to version 2.2.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http loadster https://api.loadster.com/mcpclaude mcp add --transport http loadster https://api.loadster.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__loadster__get_screenshot",
"mcp__loadster__get_command_schema",
"mcp__loadster__get_example",
"mcp__loadster__get_scripting_api",
"mcp__loadster__get_variable_schema",
"mcp__loadster__list_command_types",
"mcp__loadster__validate_script",
"mcp__loadster__get_dataset",
"mcp__loadster__list_datasets",
"mcp__loadster__list_engines",
"mcp__loadster__get_documentation",
"mcp__loadster__get_incident",
"mcp__loadster__get_monitor",
"mcp__loadster__get_monitor_cycle_detail",
"mcp__loadster__get_monitoring_summary",
"mcp__loadster__list_incidents",
"mcp__loadster__list_monitor_cycles",
"mcp__loadster__list_monitoring_locations",
"mcp__loadster__list_monitors",
"mcp__loadster__get_load_test_report",
"mcp__loadster__get_load_test_status",
"mcp__loadster__get_load_test_url_timings",
"mcp__loadster__list_load_tests",
"mcp__loadster__get_scenario",
"mcp__loadster__list_scenarios",
"mcp__loadster__get_play_status",
"mcp__loadster__get_script",
"mcp__loadster__get_script_asset",
"mcp__loadster__get_script_revision",
"mcp__loadster__get_step_detail",
"mcp__loadster__list_projects",
"mcp__loadster__list_script_assets",
"mcp__loadster__list_script_revisions",
"mcp__loadster__list_scripts"
],
"ask": [
"mcp__loadster__append_dataset_rows",
"mcp__loadster__create_dataset",
"mcp__loadster__submit_feedback",
"mcp__loadster__create_monitor",
"mcp__loadster__disable_monitor",
"mcp__loadster__create_scenario",
"mcp__loadster__create_project",
"mcp__loadster__create_script",
"mcp__loadster__duplicate_script",
"mcp__loadster__play_script",
"mcp__loadster__restore_script_revision",
"mcp__loadster__update_project",
"mcp__loadster__update_script"
],
"deny": [
"mcp__loadster__delete_dataset",
"mcp__loadster__update_dataset",
"mcp__loadster__delete_monitor",
"mcp__loadster__enable_monitor",
"mcp__loadster__update_monitor",
"mcp__loadster__stop_load_test",
"mcp__loadster__update_load_test_notes",
"mcp__loadster__delete_scenario",
"mcp__loadster__launch_load_test",
"mcp__loadster__update_scenario",
"mcp__loadster__delete_script",
"mcp__loadster__delete_script_asset",
"mcp__loadster__import_script",
"mcp__loadster__put_script_asset",
"mcp__loadster__stop_script"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as loadster. Review it before you use it.
Capability tags behind 10 rules
- mcp__loadster__get_scripting_api private-data, untrusted-input
- mcp__loadster__get_dataset private-data
- mcp__loadster__list_datasets private-data
- mcp__loadster__enable_monitor untrusted-input
- mcp__loadster__get_monitor_cycle_detail private-data, untrusted-input
- mcp__loadster__get_load_test_url_timings untrusted-input
- mcp__loadster__launch_load_test untrusted-input
- mcp__loadster__get_step_detail private-data, untrusted-input
- mcp__loadster__list_script_assets private-data
- mcp__loadster__play_script untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.loadster/loadster-mcp/verify?hash=d0276a4b624f0f55ce85ac5984c2ef924a8d535390b876b1d77b80a137ad44d8" | jq -e '.changed == false'Pinned hash d0276a4b624f, from Nov 13, 2026, 20:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.loadster/loadster-mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.loadster/loadster-mcp)Source: MCP Registry · repository. Synced Nov 13, 2026, 20:17 UTC.
Loadster MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Loadster MCP server safe?
- No scan can promise that. What its definitions show: 62 tools, 28 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Loadster MCP server delete data?
- Yes. 15 tools can delete, cancel or revoke something: delete_dataset, update_dataset, delete_monitor, enable_monitor, update_monitor, stop_load_test and 9 more.
Can the Loadster MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Loadster MCP server have?
- 62 tools: 15 destructive, 13 write, 34 read. delete_dataset, update_dataset, delete_monitor, enable_monitor, update_monitor, stop_load_test, update_load_test_notes, delete_scenario and 54 more.
Does the Loadster MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Loadster MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Loadster MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 13, 2026. Every change is on this page and in its Atom feed.