Skip to content

Testsy MCP server

dev.testsy/testsytestsy.devstreamable-httpv1.1.6Scanned

Run plain-English QA tests on websites and mobile apps, then inspect each check and its evidence.

48 tools: 15 can delete or cancel things, 16 change things and 17 only read.

Tools: 15 delete, 0 irreversible, 16 write, 17 read.
  • Reads private data · 2
  • Reads text others write · 7
  • Can send data out · 4
  • 7 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.
Govern this server →

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 Testsy MCP server can do

The Testsy MCP server is published by testsy.dev, a domain the MCP Registry verified. It has 48 tools. It can delete or cancel things (15 tools: update_project, delete_project, update_test, delete_test and 11 more) and create or change data (16 tools: set_browse_from, create_project, create_test, duplicate_test and 12 more). 17 tools only read.

2 tools read private data (list_test_files and list_credentials); 7 tools bring in text other people can write (get_network, set_browse_from, run_test and 4 more); 4 tools can send data out of your system (create_test, plan_test, add_endpoint and 1 more). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

The fixed checks matched 7 findings (credentials-mention and annotation-conflict). 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 20, 2026, version 1.1.6.

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.

48 tools

Deletes or cancels 15Claude Code: deny
  • add_test_fileAdd a file the tester can upload during the test: up to 25 MB, up to 10 files per test.No findings

    Why it is in this group

    • The name "add_test_file" says "add": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Add a file the tester can upload during the test: up to 25 MB, up to 10 files per test. REST: send the raw bytes as the body with the file name in the X-File-Name header (or ?name=), or JSON {name, contentBase64}. MCP: name and contentBase64. A file with the same name replaces the old one. Reference: https://testsy.dev/docs/mcp/

    Annotations the server declares

    • title: Add a test file
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
  • delete_buildDelete a build.No findings

    Why it is in this group

    • The name "delete_build" says "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Delete a build. Runs that used it keep their results; a build a test pins cannot be deleted. Reference: https://testsy.dev/docs/mcp/

    Annotations the server declares

    • title: Delete a build
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
  • delete_credentialDelete a sign-in account.No findings

    Why it is in this group

    • The name "delete_credential" says "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Delete a sign-in account. Tests that sign in with it stop running until it is added again or they are edited. Reference: https://testsy.dev/docs/mcp/

    Annotations the server declares

    • title: Delete a sign-in account
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
  • delete_endpointDelete an endpoint.No findings

    Why it is in this group

    • The name "delete_endpoint" says "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Delete an endpoint. Reference: https://testsy.dev/docs/mcp/

    Annotations the server declares

    • title: Delete an endpoint
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
  • delete_projectArchive a project: its tests stop running; past runs stay in the run history.No findings

    Why it is in this group

    • The name "delete_project" says "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Archive a project: its tests stop running; past runs stay in the run history. Reference: https://testsy.dev/docs/mcp/

    Annotations the server declares

    • title: Archive a project
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
  • delete_scheduleDelete a schedule.No findings

    Why it is in this group

    • The name "delete_schedule" says "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Delete a schedule. Reference: https://testsy.dev/docs/mcp/

    Annotations the server declares

    • title: Delete a schedule
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
  • delete_testArchive a test: it stops running; past runs stay in the run history.No findings

    Why it is in this group

    • The name "delete_test" says "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Archive a test: it stops running; past runs stay in the run history. Reference: https://testsy.dev/docs/mcp/

    Annotations the server declares

    • title: Archive a test
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
  • delete_test_fileRemove one of a test's files.No findings

    Why it is in this group

    • The name "delete_test_file" says "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Remove one of a test's files. Reference: https://testsy.dev/docs/mcp/

    Annotations the server declares

    • title: Delete a test file
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
  • run_projectStart a run of every test in a project (a suite).Reads text others writeNo findings

    Why it is in this group

    • The name "run_project" says "run": 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
    Start a run of every test in a project (a suite). Each started run has a watchUrl to watch it live without signing in. buildIds: builds to use; each app test runs the one of its own app. Tests that could not start are listed in skipped with the reason. REST: send an Idempotency-Key header to make a retry safe. Reference: https://testsy.dev/docs/mcp/

    Annotations the server declares

    • title: Run a project
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
  • run_testStart a run of one test.Reads text others writeNo findings

    Why it is in this group

    • The name "run_test" says "run": 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
    Start a run of one test. Runs take minutes: poll get_run until final is true. watchUrl opens the run live without signing in. App tests run the newest build of their app unless buildId names another (see list_builds). watchUrl is a view-only link anyone can open (no sign-in) to watch the run live and read its result for a while after it ends; give it to the person waiting for the result. Absent when the workspace turned watch links off. REST: send an Idempotency-Key header so a retried request does not start a second run. Reference: https://testsy.dev/docs/mcp/

    Annotations the server declares

    • title: Run a test
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
  • stop_runStop a queued or running run.No findings

    Why it is in this group

    • The name "stop_run" says "stop": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Stop a queued or running run. A run you stop is not counted. Reference: https://testsy.dev/docs/mcp/

    Annotations the server declares

    • title: Stop a run
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • update_projectRename a project or change its description.No findings

    Why it is in this group

    • The name "update_project" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Rename a project or change its description. Reference: https://testsy.dev/docs/mcp/

    Annotations the server declares

    • title: Update a project
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • update_testChange a test: its title, start address, requirement, plan or options.2 findings

    Why it is in this group

    • The name "update_test" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    Findings

    • Info

      The input schema at properties.plan.description mentions "credentials".

      Matched text

      inputSchema.properties.plan.description: "...s[], checks[], record[], assumptions[], credentials[]}. Stored as the approved checklist; t..."

      What this check looks for
    • Info

      The input schema at properties.options.description mentions "credentials".

      Matched text

      inputSchema.properties.options.description: "...s a step; fail = any of them fails it), credentials (names of the project's sign-in account..."

      What this check looks for
    Description, as the server wrote it
    Change a test: its title, start address, requirement, plan or options. Only the fields you pass change; within `options`, only the options you pass change and the others keep their values. Reference: https://testsy.dev/docs/mcp/

    Annotations the server declares

    • title: Update a test
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
Changes things 16Claude Code: ask
  • add_credentialStore a sign-in account the tester can use.No findings

    Why it is in this group

    • The name "add_credential" says "add": a word for a change.
    Description, as the server wrote it
    Store a sign-in account the tester can use. The password is encrypted, never returned, and never sent to the tester's AI: the tester types it. Tests refer to the account by name ("Sign in as the account \"customer\""). Through MCP the password passes through your AI agent: prefer adding passwords in the web app or over the REST API from a secret store. Reference: https://testsy.dev/docs/mcp/

    Annotations the server declares

    • title: Add a sign-in account
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • add_endpointSave the definition of one call into your own system that the tester may make during a run (for example "create a voucher").Can send data outNo findings

    Why it is in this group

    • The name "add_endpoint" says "add": a word for a change.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Save the definition of one call into your own system that the tester may make during a run (for example "create a voucher"). This only stores the definition: it sends no request itself. The tester sees only the name, the description and what the call returned. bodyTemplate may contain {{param}} placeholders the tester fills in. Headers (for example Authorization) are encrypted and never returned. Reference: https://testsy.dev/docs/mcp/

    Annotations the server declares

    • title: Save an endpoint definition
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • complete_build_uploadFinish the upload with every part's etag.No findings

    Why it is in this group

    • The name "complete_build_upload" says "upload": a word for a change.
    Description, as the server wrote it
    Finish the upload with every part's etag. The build is checked (app id, version, whether our devices can run it) and returned. Use the returned build.id in run_test {buildId} or run_project {buildIds} to run the new build. Uploading alone does not start a run. The command from create_build_upload completes the upload itself; call this only after uploading parts to the signed links yourself. Also accepts the signed completeUrl instead of an API key. Reference: https://testsy.dev/docs/mcp/

    Annotations the server declares

    • title: Complete a build upload
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • create_build_uploadStart a build upload and get signed links that upload the file without an API key: run the returned command in a shell, or PUT each part and POST complete to the links.No findings

    Why it is in this group

    • The name "create_build_upload" says "create": a word for a change.
    Description, as the server wrote it
    Start a build upload and get signed links that upload the file without an API key: run the returned command in a shell, or PUT each part and POST complete to the links. The build is then checked and ready to run. For AI agents: tool arguments cannot carry a build, so hand the bytes to a shell command. command downloads the command-line tool and uploads the file (parts, then complete). Without it: PUT the raw bytes of part n (partBytes each, the last one shorter) to partUrlTemplate with {partNumber} replaced, then POST {parts: [{partNumber, etag}]} to completeUrl. The links expire at expiresAt and work only for this upload. Call find_build first to skip uploading a file that is already there. Reference: https://testsy.dev/docs/mcp/

    Annotations the server declares

    • title: Create signed upload links
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • create_projectCreate a project, for example one per site or app.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 example one per site or app. Reference: https://testsy.dev/docs/mcp/

    Annotations the server declares

    • title: Create a project
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • create_scheduleRun a test by itself: on chosen weekdays, or monthly on a day, at a time in a time zone.No findings

    Why it is in this group

    • The name "create_schedule" says "create": a word for a change.
    Description, as the server wrote it
    Run a test by itself: on chosen weekdays, or monthly on a day, at a time in a time zone. Each scheduled run counts like any other run. Reference: https://testsy.dev/docs/mcp/

    Annotations the server declares

    • title: Create a schedule
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • create_testCreate a test of a website (url) or of an app (platform android or ios, and appId; device phone or tablet and osVersion, default a phone on the latest OS).Can send data out3 findings

    Why it is in this group

    • The name "create_test" says "create": a word for a change.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...in the text: name a sign-in account in `credentials`. Reference: https://testsy.dev/docs/mc..."

      What this check looks for
    • Info

      The input schema at properties.plan.description mentions "credentials".

      Matched text

      inputSchema.properties.plan.description: "...s[], checks[], record[], assumptions[], credentials[]}. Stored as the approved checklist; t..."

      What this check looks for
    • Info

      The input schema at properties.options.description mentions "credentials".

      Matched text

      inputSchema.properties.options.description: "...s a step; fail = any of them fails it), credentials (names of the project's sign-in account..."

      What this check looks for
    Description, as the server wrote it
    Create a test of a website (url) or of an app (platform android or ios, and appId; device phone or tablet and osVersion, default a phone on the latest OS). Pass `plan` (from plan_test, after the requester confirmed it): it is stored as the approved checklist and the tester follows it as written. Or pass `requirement`, plain-language text the tester plans itself at run time. Never put passwords in the text: name a sign-in account in `credentials`. Reference: https://testsy.dev/docs/mcp/

    Annotations the server declares

    • title: Create a test
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • duplicate_testCopy a test under a new title: the test's info is copied over (start address, requirement, plan, options and files).No findings

    Why it is in this group

    • The description's first verb is "copy": a word for a change.
    Description, as the server wrote it
    Copy a test under a new title: the test's info is copied over (start address, requirement, plan, options and files). Its run history and schedules stay with the original. The copy counts toward the plan's test limit. Without `title` it is named "<original title> (copy)". Pass `projectId` to put the copy in another project of the workspace. Reference: https://testsy.dev/docs/mcp/

    Annotations the server declares

    • title: Duplicate a test
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • get_runA run: its status, and once final the verdict, the headline, each check's result with the reason, the values read, and links to the video, screenshots and the result page.1 finding

    Why it is in this group

    • The name "get_run" says "get": a word for reading.
    • The description's first verb is "run": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "get_run" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "get_run" says "get": a word for reading.

      What this check looks for
    Description, as the server wrote it
    A run: its status, and once final the verdict, the headline, each check's result with the reason, the values read, and links to the video, screenshots and the result page. Reference: https://testsy.dev/docs/mcp/

    Annotations the server declares

    • title: Get a run
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • import_buildFetch a build from an https link (an EAS, Bitrise, S3 or GitHub artifact link, up to the build size limit) into the project; it is checked and ready to run.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "import_build" says "import": 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.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Fetch a build from an https link (an EAS, Bitrise, S3 or GitHub artifact link, up to the build size limit) into the project; it is checked and ready to run. Nothing to upload from your side. The link must be https to a public host name; up to 3 redirects are followed. headers (optional, at most 5: Authorization or X-… names) are sent to the first host only, for a private artifact store. The file name comes from Content-Disposition or the link; it must be an .apk or a zipped .app. Run the result with run_test {buildId} or run_project {buildIds}. Call find_build first when the file may already be there. Reference: https://testsy.dev/docs/mcp/

    Annotations the server declares

    • title: Import a build from a link
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • list_endpointsCalls into your own systems the tester may make during a run (for example "create a voucher").1 finding

    Why it is in this group

    • The name "list_endpoints" says "list": a word for reading.
    • The description's first verb is "call": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "list_endpoints" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "list_endpoints" says "list": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Calls into your own systems the tester may make during a run (for example "create a voucher"). Headers are never returned. Reference: https://testsy.dev/docs/mcp/

    Annotations the server declares

    • title: List endpoints
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • plan_testHave the assistant draft a test from a plain-language description, or revise a plan, without saving anything.Can send data outNo 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 read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Have the assistant draft a test from a plain-language description, or revise a plan, without saving anything. Returns the proposed steps, checks, values to record, assumptions and any questions only the requester can answer. Show the plan to the requester; to change it, call again with `plan` and `change`; to answer questions, pass `answers`. Once they confirm, pass the plan to create_test. When no question is open the plan has passed the planning review (review.ok). Pass projectId so the assistant knows the project's sign-in accounts and endpoints. Each call uses one assistant draft of the workspace's daily allowance. Reference: https://testsy.dev/docs/mcp/

    Annotations the server declares

    • title: Draft or revise a plan
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • set_browse_fromChoose the country our browsers and devices reach your sites and app servers from (web and app tests), or automatic: the site's own country (an app test then uses our default count…Reads text others writeNo findings

    Why it is in this group

    • The name "set_browse_from" says "set": a word for a change.

    What it can reach

    • untrusted-inputThe name "set_browse_from" says "browse": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Choose the country our browsers and devices reach your sites and app servers from (web and app tests), or automatic: the site's own country (an app test then uses our default country). Reference: https://testsy.dev/docs/mcp/

    Annotations the server declares

    • title: Set the browsing country
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • update_schedulePause or resume a schedule.No findings

    Why it is in this group

    • The name "update_schedule" says "update": a word for a change.
    Description, as the server wrote it
    Pause or resume a schedule. Reference: https://testsy.dev/docs/mcp/

    Annotations the server declares

    • title: Pause or resume a schedule
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 17Show 17 read-only tools
  • find_buildIs this build already uploaded?No findings

    Why it is in this group

    • The name "find_build" says "find": a word for reading.
    Description, as the server wrote it
    Is this build already uploaded? Looks up the project's newest ready build by the file's sha256, else by a native fingerprint; build is null when neither matches. A sha256 match means the exact file is uploaded: run it with run_test {buildId} / run_project {buildIds} instead of uploading again. A fingerprint match (a hash of the native inputs the uploader stored with the build, for example @expo/fingerprint) means the native build is unchanged, so CI can skip building it. The command-line tool does this for files: testsy-ai build find / build ensure. Reference: https://testsy.dev/docs/mcp/

    Annotations the server declares

    • title: Find a build
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_buildOne build: its app id, version, status and any warnings.No findings

    Why it is in this group

    • The name "get_build" says "get": a word for reading.
    Description, as the server wrote it
    One build: its app id, version, status and any warnings. Reference: https://testsy.dev/docs/mcp/

    Annotations the server declares

    • title: Get a build
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_networkHow our browsers reach your sites: the static addresses to allow-list, the country they browse from, and the countries available.Reads text others writeNo findings

    Why it is in this group

    • The name "get_network" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "browse": it reads web pages, which anyone can write.
    Description, as the server wrote it
    How our browsers reach your sites: the static addresses to allow-list, the country they browse from, and the countries available. Reference: https://testsy.dev/docs/mcp/

    Annotations the server declares

    • title: Get network settings
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_projectOne project.No findings

    Why it is in this group

    • The name "get_project" says "get": a word for reading.
    Description, as the server wrote it
    One project. Reference: https://testsy.dev/docs/mcp/

    Annotations the server declares

    • title: Get a project
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_testOne test: its start address, requirement, plan, options and latest run.No findings

    Why it is in this group

    • The name "get_test" says "get": a word for reading.
    Description, as the server wrote it
    One test: its start address, requirement, plan, options and latest run. Reference: https://testsy.dev/docs/mcp/

    Annotations the server declares

    • title: Get a test
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_usagePlan, runs used this billing period, included runs, extra-run packs and runs left.No findings

    Why it is in this group

    • The name "get_usage" says "get": a word for reading.
    Description, as the server wrote it
    Plan, runs used this billing period, included runs, extra-run packs and runs left. Reference: https://testsy.dev/docs/mcp/

    Annotations the server declares

    • title: Get usage
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_workspaceThe workspace this key belongs to: its id, name and plan, and this period's usage.No findings

    Why it is in this group

    • The name "get_workspace" says "get": a word for reading.
    Description, as the server wrote it
    The workspace this key belongs to: its id, name and plan, and this period's usage. Reference: https://testsy.dev/docs/mcp/

    Annotations the server declares

    • title: Get the workspace
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • list_buildsThe app builds uploaded to a project (Android .apk, iOS Simulator .app zipped), newest first, with the largest size and part size for uploads.No findings

    Why it is in this group

    • The name "list_builds" says "list": a word for reading.
    Description, as the server wrote it
    The app builds uploaded to a project (Android .apk, iOS Simulator .app zipped), newest first, with the largest size and part size for uploads. Reference: https://testsy.dev/docs/mcp/

    Annotations the server declares

    • title: List builds
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • list_credentialsThe sign-in accounts stored for a project: names, usernames and sites.Reads private dataNo findings

    Why it is in this group

    • The name "list_credentials" says "list": a word for reading.

    What it can reach

    • private-dataThe name "list_credentials" says "list" and "credential": it reads secrets.
    Description, as the server wrote it
    The sign-in accounts stored for a project: names, usernames and sites. Passwords are never returned. Reference: https://testsy.dev/docs/mcp/

    Annotations the server declares

    • title: List sign-in accounts
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • list_devicesThe phones and tablets app tests can run on, and their OS versions (latest first).No findings

    Why it is in this group

    • The name "list_devices" says "list": a word for reading.
    Description, as the server wrote it
    The phones and tablets app tests can run on, and their OS versions (latest first). Pass device and osVersion to create_test, update_test, run_test or run_project. A new app test runs on a phone with the latest OS unless you choose otherwise; the version is saved with the test, so it keeps its OS until you change it. Reference: https://testsy.dev/docs/mcp/

    Annotations the server declares

    • title: List devices
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • list_projectsThe projects in this workspace (a project groups the tests of one site or app).No findings

    Why it is in this group

    • The name "list_projects" says "list": a word for reading.
    Description, as the server wrote it
    The projects in this workspace (a project groups the tests of one site or app). Reference: https://testsy.dev/docs/mcp/

    Annotations the server declares

    • title: List projects
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • list_runsRecent runs, newest first, optionally for one test or project or with one status; or the runs with the given ids.No findings

    Why it is in this group

    • The name "list_runs" says "list": a word for reading.
    Description, as the server wrote it
    Recent runs, newest first, optionally for one test or project or with one status; or the runs with the given ids. Reference: https://testsy.dev/docs/mcp/

    Annotations the server declares

    • title: List runs
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • list_schedulesWhen tests run by themselves: every schedule in the workspace, or those of one test or project.No findings

    Why it is in this group

    • The name "list_schedules" says "list": a word for reading.
    Description, as the server wrote it
    When tests run by themselves: every schedule in the workspace, or those of one test or project. Reference: https://testsy.dev/docs/mcp/

    Annotations the server declares

    • title: List schedules
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • list_test_filesFiles a test can upload during its steps (for example an import file).Reads private dataNo findings

    Why it is in this group

    • The name "list_test_files" says "list": a word for reading.

    What it can reach

    • private-dataThe name "list_test_files" says "list" and "file": it reads files.
    • private-dataThe description's first sentence says "file": it reads files.
    Description, as the server wrote it
    Files a test can upload during its steps (for example an import file). Reference: https://testsy.dev/docs/mcp/

    Annotations the server declares

    • title: List a test's files
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • list_testsThe tests of a project, each with its latest run.No findings

    Why it is in this group

    • The name "list_tests" says "list": a word for reading.
    Description, as the server wrote it
    The tests of a project, each with its latest run. Reference: https://testsy.dev/docs/mcp/

    Annotations the server declares

    • title: List tests
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • wait_runWait up to seconds (default 25, at most 55) for a run to finish, then return it: one call instead of polling get_run every few seconds.No findings

    Why it is in this group

    • The name "wait_run" says "wait": a word for reading.
    Description, as the server wrote it
    Wait up to seconds (default 25, at most 55) for a run to finish, then return it: one call instead of polling get_run every few seconds. Call it again while final is false. The answer comes back the moment the run is final (verdict, checks and evidence in), or when the time is up with final false — then call wait_run again. Runs take 2 to 20 minutes, so expect several calls for a long run; each costs nothing while it waits. Reference: https://testsy.dev/docs/mcp/

    Annotations the server declares

    • title: Wait for a run
    • readOnlyHint: true
    • destructiveHint: false
    • 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.

56 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 2 private-data tools breaks every one.

Reads private data2
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 out4
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__testsy__list_credentials",
      "mcp__testsy__list_test_files"
    ]
  }
}

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.

Tools listed without sign-in

Looked at Nov 15, 2026, 13:22 UTC, unchanged since Nov 15, 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
31
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://app.testsy.dev/.well-known/oauth-protected-resource/mcp
Authorization servers
https://app.testsy.dev
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 31 tools that change things (10 destructive, 21 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://app.testsy.dev/mcp: tools/list returned 48 tools to an anonymous client, including delete_project (destructive), delete_test (destructive), delete_test_file (destructive), delete_credential (destructive), delete_endpoint (destructive) and 26 more

    What this check looks for

Posture changes

  1. Nov 15, 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 31
    • Protocol version: none to 2025-06-18
    • WWW-Authenticate on 401: yes to not observed
    • resource_metadata in WWW-Authenticate: https://app.testsy.dev/.well-known/oauth-protected-resource/mcp to none

Findings

Matches of fixed checks, with the text they matched.

2 warn5 info
  • The server marks "list_endpoints" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "list_endpoints" says "list": a word for reading.

    What this check looks for
  • The server marks "get_run" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "get_run" says "get": a word for reading.

    What this check looks for
  • The description mentions "credentials".

    Matched text

    description: "...in the text: name a sign-in account in `credentials`. Reference: https://testsy.dev/docs/mc..."

    What this check looks for
  • The input schema at properties.plan.description mentions "credentials".

    Matched text

    inputSchema.properties.plan.description: "...s[], checks[], record[], assumptions[], credentials[]}. Stored as the approved checklist; t..."

    What this check looks for
  • The input schema at properties.options.description mentions "credentials".

    Matched text

    inputSchema.properties.options.description: "...s a step; fail = any of them fails it), credentials (names of the project's sign-in account..."

    What this check looks for
  • The input schema at properties.plan.description mentions "credentials".

    Matched text

    inputSchema.properties.plan.description: "...s[], checks[], record[], assumptions[], credentials[]}. Stored as the approved checklist; t..."

    What this check looks for
Show 1 more finding
  • The input schema at properties.options.description mentions "credentials".

    Matched text

    inputSchema.properties.options.description: "...s a step; fail = any of them fails it), credentials (names of the project's sign-in account..."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools48 changed.~48 changedView diff
  2. Tools1 added, 2 changed.+1 added~2 changedView diff
  3. 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 -> 31 (and 3 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 31
    • Protocol version: none to 2025-06-18
    • WWW-Authenticate on 401: yes to not observed
    • resource_metadata in WWW-Authenticate: https://app.testsy.dev/.well-known/oauth-protected-resource/mcp to none

Install

Pinned to version 1.1.6. Values in angle brackets are yours to fill in.

claude mcp add --transport http testsy https://app.testsy.dev/mcp
claude mcp add --transport http testsy https://app.testsy.dev/mcp

Run 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.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__testsy__get_workspace",
      "mcp__testsy__get_usage",
      "mcp__testsy__get_network",
      "mcp__testsy__list_projects",
      "mcp__testsy__get_project",
      "mcp__testsy__list_tests",
      "mcp__testsy__get_test",
      "mcp__testsy__list_test_files",
      "mcp__testsy__list_credentials",
      "mcp__testsy__list_runs",
      "mcp__testsy__wait_run",
      "mcp__testsy__list_share_links",
      "mcp__testsy__list_schedules",
      "mcp__testsy__list_devices",
      "mcp__testsy__list_builds",
      "mcp__testsy__get_build",
      "mcp__testsy__find_build"
    ],
    "ask": [
      "mcp__testsy__set_browse_from",
      "mcp__testsy__create_project",
      "mcp__testsy__create_test",
      "mcp__testsy__duplicate_test",
      "mcp__testsy__plan_test",
      "mcp__testsy__add_credential",
      "mcp__testsy__list_endpoints",
      "mcp__testsy__add_endpoint",
      "mcp__testsy__get_run",
      "mcp__testsy__create_watch_link",
      "mcp__testsy__create_share_link",
      "mcp__testsy__create_schedule",
      "mcp__testsy__update_schedule",
      "mcp__testsy__create_build_upload",
      "mcp__testsy__import_build",
      "mcp__testsy__complete_build_upload"
    ],
    "deny": [
      "mcp__testsy__update_project",
      "mcp__testsy__delete_project",
      "mcp__testsy__update_test",
      "mcp__testsy__delete_test",
      "mcp__testsy__add_test_file",
      "mcp__testsy__delete_test_file",
      "mcp__testsy__delete_credential",
      "mcp__testsy__delete_endpoint",
      "mcp__testsy__run_test",
      "mcp__testsy__run_project",
      "mcp__testsy__stop_run",
      "mcp__testsy__revoke_watch_link",
      "mcp__testsy__delete_share_link",
      "mcp__testsy__delete_schedule",
      "mcp__testsy__delete_build"
    ]
  }
}

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 testsy. Review it before you use it.

Capability tags behind 12 rules
  • mcp__testsy__get_network untrusted-input
  • mcp__testsy__set_browse_from untrusted-input
  • mcp__testsy__create_test outbound
  • mcp__testsy__plan_test outbound
  • mcp__testsy__list_test_files private-data
  • mcp__testsy__list_credentials private-data
  • mcp__testsy__add_endpoint outbound
  • mcp__testsy__run_test untrusted-input
  • mcp__testsy__run_project untrusted-input
  • mcp__testsy__create_watch_link untrusted-input
  • mcp__testsy__create_share_link untrusted-input
  • mcp__testsy__import_build untrusted-input, outbound

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/dev.testsy/testsy/verify?hash=d6177eaa9f26e62168f11b2e05bdd2b1f1cb25e840ec34c6c6cdd4c780c57a00" | jq -e '.changed == false'

Pinned hash d6177eaa9f26, from Nov 20, 2026, 05:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/dev.testsy/testsy/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for dev.testsy/testsy
[![Anlyon Radar](https://radar.anlyon.com/badge/dev.testsy/testsy.svg)](https://radar.anlyon.com/servers/dev.testsy/testsy)

Source: MCP Registry · repository. Synced Nov 20, 2026, 05:17 UTC.

Testsy MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Testsy MCP server safe?

No scan can promise that. What its definitions show: 48 tools, 31 of which can change, send or delete something, and 7 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 Testsy MCP server delete data?

Yes. 15 tools can delete, cancel or revoke something: update_project, delete_project, update_test, delete_test, add_test_file, delete_test_file and 9 more.

Can the Testsy 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 Testsy MCP server have?

48 tools: 15 destructive, 16 write, 17 read. update_project, delete_project, update_test, delete_test, add_test_file, delete_test_file, delete_credential, delete_endpoint and 40 more.

Does the Testsy MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Testsy MCP server send data to outside services?

4 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): create_test, plan_test, add_endpoint and import_build.

Has the Testsy MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 20, 2026. Every change is on this page and in its Atom feed.