Free MCP servers and Skills that connect ConnectWise PSA, HaloPSA, HubSpot, and Servosity backup to the AI you already use - Claude, ChatGPT, Copilot, Codex. Local SQLite mirror, and your data stays l
8h +2★ 79Business
Introduction
The maker's introduction consists of the line above. Read the repository README for more details. Repository README ↗
Scope disputes usually come down to one sentence: "I thought that was included." A PDF and an email that says "looks good" do not settle it, and every "one small change" after that is a discount nobody agreed to. SignedScope records what was shown, what was approved or rejected, who signed and when, in a form neither side can edit without verification failing.
Screenshots
1. Agency creates a sign-off
2. Client reviews and signs
3. Signed receipt with evidence
4. Change request shown as a diff
5. Anyone can verify a link
6. An edited link fails verification
How it works
Seal. The agency lists in-scope items, UAT checks and out-of-scope exclusions. POST /api/seal returns v1.<base64url(json)>.<hmac>. That token is the whole document.
Sign. The client opens /sign#<token>. The data sits in the URL fragment, so it is not part of the page request. The page then sends it in the body of an API call that checks the signature and stores nothing. They accept or reject each item (a rejection needs a comment), acknowledge the exclusions and sign. POST /api/sign checks the token and returns a signed receipt that embeds the document, its SHA-256, the decisions, the signer, a timestamp, the country and a UA hash.
Verify./verify (or POST /api/verify) recomputes the HMAC. If the document changed, verification fails.
Change request. "Start a change request" on a receipt seals revision n+1 linked to the baseline receipt's hash. The client sees added, changed and removed items compared with what they approved.
Prices and payment. Any in-scope or UAT line can carry a price, in one of 15 currencies. The receipt records the accepted total and, on a change request, the signed baseline it is compared with. An optional Pay link (Stripe, Wise, Omise, PayPal or Payoneer hosts only) is shown to the client after signing. SignedScope never handles the money.
Draft from a message.POST /api/draft turns a pasted client message or brief into draft lines. With ANTHROPIC_API_KEY set it uses Claude; otherwise a rule-based splitter. Nothing is sealed until the agency reviews it.
Free (this repo)
Pro, planned, $19/mo flat
Agency, planned, $49/mo flat
Unlimited sign-offs, receipts, priced change requests, your own Pay link
Yes
Yes
Yes
Saved workspace, email notifications, branding, PDF, invoices and tax via Stripe Connect
No
Yes
Yes
5 seats, custom domain, API/webhooks
No
No
Yes
Security model
Integrity comes from HMAC-SHA256 with a server secret, compared in constant time. A token cannot be forged or edited without SIGNING_SECRET.
Signer identity is self-declared: the receipt shows what the person who opened the link entered. It is a sign-off record, not an eIDAS or ESIGN qualified signature.
Rotating the secret makes every existing link fail verification. Key IDs (v2.<kid>.…) would fix that, and they are on the roadmap.
Inputs are size-limited (64 KB body, up to 100 items of 600 characters each, and about 60,000 characters per link). Waitlist sign-ups are rate-limited per IP (5 per 10 min), with counters in Blob under a keyed hash, so raw IPs are never stored. The UI renders everything with textContent, under a strict CSP.
Self-host
git clone https://github.com/tahmidbintaslim/signedscope && cd signedscope
npm install && npm test
# Vercel: set SIGNING_SECRET (32+ random chars); optional ANTHROPIC_API_KEY for AI drafts, BLOB_READ_WRITE_TOKEN for the waitlist,
# STRIPE_LINK_PRO / STRIPE_LINK_AGENCY for checkout redirects
# Accounts and the /app workspace: SUPABASE_URL, SUPABASE_ANON_KEY, SUPABASE_SERVICE_ROLE_KEY (see docs/SETUP-ACCOUNTS.md)
npx vercel deploy
No framework and no build step: static files in public/ plus Node functions in api/. Accounts use Supabase (Postgres with Row Level Security); the schema is in supabase/migrations/, and the browser client is vendored in public/vendor/ so the CSP can stay script-src 'self'. Fonts (Plus Jakarta Sans, JetBrains Mono; OFL) are self-hosted under public/fonts/.
Run it locally
SIGNING_SECRET=$(openssl rand -base64 32) npm run dev # http://localhost:3000, no Vercel CLI needed
Tests: npm test runs unit and server tests; set PGTEST_URL to a Postgres URL to also run the Row Level Security tests (CI does). node test/browser/app.e2e.js drives the workspace in a browser against an in-memory Supabase.
scripts/capture-screenshots.js regenerates the app screenshots in docs/img/, and scripts/capture-demo.js records docs/img/demo.gif and public/og.png, both from a real run against the dev server (BASE=http://localhost:3000).
Payments: Pro and Agency are not built yet, so the landing page links to the waitlist. The /api/checkout route and the Stripe test-mode links stay in place for when live mode is approved.
Roadmap
Key IDs and secret rotation
Accounts and a workspace: clients, projects, saved AI estimates, document status (sent, viewed, signed), payments, activity, two-step sign-in
Proposals and agreements: written sections, AI-drafted text, clause library (templates, not legal advice), payment schedule that becomes payment requests on approval, print or save as PDF
Document vault (private files per project, 7-day share links), email on sign/view, daily overdue-payment reminders
Logo and colors on documents, Thai and Bangla clause text, team seats
Subscription billing for Pro and Plus (Stripe), provider-confirmed payment status (webhooks)
Pro: invoices, pay links and tax through Stripe Connect (each agency a connected account)
Email OTP to confirm signer identity (optional per document)
Import from Markdown, Notion or Google Docs checklists
Agency: webhooks, seats, custom domain
Author
Tahmid Rafi, Lead Full Stack Software Engineer & Solutions Architect, Bangkok.
