Built with WordPress, hosted on Fastly. Domain registered in 2023.
formesign.com is built with WordPress, hosted on Fastly. It measures traffic with Google Analytics and Google Tag Manager.
| Technology | Version | First seen |
|---|---|---|
| CMS & Site Builders1 | ||
| – | 9 Nov 2026 | |
| WordPress Plugins1 | ||
| – | 9 Nov 2026 | |
| Frontend Build Tools & CSS2 | ||
| – | 9 Nov 2026 | |
| Web Servers, Languages & Backend Frameworks3 | ||
| – | 9 Nov 2026 | |
| CDN & Hosting2 | ||
| – | 9 Nov 2026 | |
| Analytics & Tag Management3 | ||
| – | 9 Nov 2026 | |
| Advertising & Affiliate Tracking1 | ||
| – | 9 Nov 2026 | |
| Fonts & Icon Fonts3 | ||
| – | 9 Nov 2026 | |
| Video, Audio & Media Delivery2 | ||
| – | 9 Nov 2026 | |
Registration from the registry's RDAP record, the certificate the site serves, and its rank in public traffic lists.
The crew hasn’t read this site’s colors yet. We read a palette when we capture a site’s screenshot, busiest sites first. Meanwhile, browse palettes from other sites.
Counted from every stack change we've recorded: of the sites we watched running one of this site's tools, how many went on to add another. A pattern across sites, not a forecast for this one.
From what the site says about itself, and account IDs it shares with other sites.
aspmx.l.google.comalt1.aspmx.l.google.comalt2.aspmx.l.google.comalt4.aspmx.l.google.comalt3.aspmx.l.google.comns74.domaincontrol.comns73.domaincontrol.comgoogle-site-verification=3-PDF2AWNRn269t4cFlEEBejalc7YUoj4pcHU1sfcj0v=spf1 include:dc-aa8e722993._spfm.formesign.com ~allgoogle-site-verification=tBYdtG_pswUC1gR_qwsZbEMWD5g2fLsfeOCeMkTWkAYv=DMARC1; p=quarantine; rua=mailto:support@guesswork.co User-agent: * Disallow: /dashboard/ Disallow: /admin/ Disallow: /stripe/
# Formesign > Agent guidance for Formesign: electronic signatures and signing workflows for Google Forms, Docs, and Sheets. Formesign serves teams creating signed agreements, waivers, consent forms, patient intake documents, safety forms, approvals, and repeatable signing workflows. - [Formesign](https://formesign.com/) - [Signatures in Google Forms](https://formesign.com/esign/) - [Compliance forms](https://formesign.com/compliance/) - MCP endpoint: `https://formesign.com/mcp/103888281684397228046` ## Before using MCP Ask the user to sign in and authorize the Formesign account they want to use. The endpoint's numeric `ownerId` selects the product connector; it is not the user's account ID. Do not request or put a customer `userId` in the URL. Never expose credentials or tokens. ## Create or update forms - **New signature form:** use `create_form`. It creates and publishes from `format` (`html` or `markdown`), optional `language`, and a text `document`; it does not accept binary image/PDF uploads. For agreements and consent documents, preserve wording verbatim. Create fields only for actual blanks, checkboxes, and signature lines; keep separate signer blocks separate. Do not send real sensitive personal data in the document text. Creating a form alone does not establish legal sufficiency or HIPAA compliance. It returns a preview; do not call `preview` again in the same turn. - **Existing form:** first call `list_forms`, find the intended form, and use its returned `publishId`; never guess IDs. Use `update_form` with `publishId` and `instruction` to add, change, or remove a field or section on the live form. Preserve approved legal text and do not overwrite signed-response or audit history. Use `get_form` to inspect it and `preview` when asked to view it. - **Full replacement:** `overwrite_form` and `is_actively_collecting_responses` are not implemented. Do not simulate replacement with `update_form`. The planned `overwrite_form` should support `overwrite: "auto" | "force"`, check response activity since creation, and enforce the check in the same write operation. `force` should only follow the user's explicit request; signed responses and audit history need defined preservation behavior. The standard product MCP tools are `create_form`, `list_forms`, `get_form`, `update_form`, `preview`, and `progress`. `progress` opens the settings checklist, including signature-workflow setup; it does not autonomously configure every setting. `list_submissions` and `analyze_submissions` are disabled. The separate `edit_form` tool is restricted to an API-key-protected edit-only route.
| – |
| 9 Nov 2026 |
| – |
| 9 Nov 2026 |
| – | 9 Nov 2026 |
| – |
| 9 Nov 2026 |
| – |
| 9 Nov 2026 |
| – | 9 Nov 2026 |
| – |
| 9 Nov 2026 |
| – | 9 Nov 2026 |
| – |
| 9 Nov 2026 |