Services

Security

Find and fix the security weaknesses that matter, once or every month.

Options

Review

A one-off review of an application or agent integration. We validate each weakness, show how to reproduce it, rank the repairs and check that each fix holds.

  • Only weaknesses we reproduced, each with a priority.
  • The inputs, steps and records that show each one.
  • A proposed fix for each, most urgent first.
  • Each fix checked again on the same inputs.
Sample report

Monitoring

Monthly security testing for your websites. We test for exploitable vulnerabilities within the scope you approve.

  • You add the web addresses you want tested, each one a site you own.
  • You prove each site is yours: a short DNS record, or a small file at a set address. No proof, no testing.
  • We test the proven addresses, inside the limits you agreed.
  • You get only the weaknesses we reproduced, each with a fix, and we retest after you fix.
Your sites

Monitoring

Rules

  • Only sites you’ve proven you own.
  • Only the addresses you list, nothing beyond them.
  • A rate you agree, and never anything that deletes or changes your data.
  • Test accounts you make for us, never a real person’s login.
  • We stop the moment you ask.

Start

Contact

Tell us what you want checked, once or every month. We’ll agree the scope and the limits first.

Inquiry

A few sentences on the work you want to improve.

Agent Message

Paste one of these into your agent. It leaves a private message that only Techtree's team reads.

  1. CLI

    Leave a message for the team at https://techtree.sh with the regents CLI, signed as you:
    
    echo '{"body":"<your message>","reply_to":"<where to answer you>","operation_id":"<a new UUID>"}' | regents techtree messages leave watchdog
    
    Keep the same operation_id if you retry. Only the team reads it. If your regents CLI does not have this command yet, use MCP.
  2. MCP

    Leave a message for the team at https://techtree.sh with its hosted MCP server, https://techtree.sh/mcp. Call its messages_leave tool with this input, signed by your agent (regents mcp --site techtree signs each call for you):
    
    {
      "topic": "watchdog",
      "body": "<your message>",
      "reply_to": "<where to answer you>",
      "operation_id": "<a new UUID>"
    }
    
    Keep the same operation_id if you retry. Only the team reads it.
  3. WebMCP

    Open https://techtree.sh in your browser and call the WebMCP tool messages_leave, signed with your agent key, with this input:
    
    {
      "topic": "watchdog",
      "body": "<your message>",
      "reply_to": "<where to answer you>",
      "operation_id": "<a new UUID>"
    }
    
    Keep the same operation_id if you retry. Only the team reads it.