SiteProxy is a powerful online proxy tool that leverages the latest technologies to enhance stability and compatibility. We are committed to providing simple, efficient, and secure proxy services to deliver the best internet access experience.
RSA + AES dual encryption technology to protect user login passwords and prevent man-in-the-middle attacks.View Principle
+----> google/youtube
+----------------+ |
| | |
user browser +-------------->+ siteproxy +-------> wikipedia
| | |
+----------------+ |
+----> chinese forums
[!CAUTION] This project must not be used for any illegal purposes. Users are responsible for their actions.
[!WARNING] Due to the support for multiple website logins, to reduce phishing risks, SiteProxy in version 2.0 obfuscates the code and prohibits modifying the default homepage URL.
A demonstration by a Telegram user of SiteProxy deployment and speed test with optimized IPs:

git clone https://github.com/netptop/siteproxy.gitsiteproxy/build/cf_page/_worker.js file with a text editor.http://localhost:5006 with your proxy server domain, e.g., https://your-proxy-domain.com (ensure to use https).user22334455 with your desired access password. If the password is empty, it means no password is required for access. Save the file.siteproxy/build/cf_page directory for deployment.https://your-proxy-domain.com/your-password/ (ensure the trailing slash exists). Remember to replace the domain and password with your own.build/worker.js file: link, and open it with a text editor.http://localhost:5006 with your proxy server domain, e.g., https://your-worker-domain.com (ensure to use https).user22334455 with your desired access password. If the password is empty, it means no password is required for access.worker.js file content into the Worker, save and deploy it.https://your-worker-domain.com/your-password/ (ensure the trailing slash exists, and replace with your own domain and password).certbot and nginx to create an SSL website. You can Google for specific usage.nginx, ensuring the /etc/nginx/conf.d/default.conf file contains the following:
nginx
server {
server_name your-proxy.domain.name;
location / {
proxy_pass http://localhost:5006;
}
}sudo systemctl restart nginxbash
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.7/install.sh | bash
source ~/.bashrc
nvm install v21git clone https://github.com/netptop/siteproxy.gitcd siteproxynode bundle.jsCtrl+C to end the program.config.json file, as follows:
json
{
"proxy_url": "https://your-proxy.domain.name", // Replace with your proxy server domain, ensure to use https
"token_prefix": "/user-SetYourPasswordHere/", // Set the website password to prevent unauthorized access, keep the slashes. Empty means no password.
"local_listen_port": 5006, // Do not modify to ensure consistency with nginx configuration
"description": "Note: token_prefix is equivalent to a website password, please set it carefully. The combination of proxy_url and token_prefix is the access URL."
}npm install -g foreverforever stopall && forever start bundle.jsproxy_url and token_prefix.Now, your proxy service has been successfully deployed and can be accessed through the browser.
git clone https://github.com/netptop/siteproxy.gitconfig.json file as follows:
json
{
"proxy_url": "https://your-proxy-domain.com", // Replace with your obtained proxy server domain
"token_prefix": "/user-SetYourPasswordHere/", // Set the website password to prevent unauthorized access, keep the slashes
"description": "Note: token_prefix is equivalent to a website password, please set it carefully. The combination of proxy_url and token_prefix is the access URL."
}docker-node subdirectory.sudo docker compose uphttps://your-proxy-domain.com/user-your-password/. Please replace the domain and password with your own.Telegram group: https://siteproxy.t.me E-mail: netptop@gmail.com
$ claude mcp add siteproxy \
-- python -m otcore.mcp_server <graph>