Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Talkform

REMOTE · WWW.TALKFORM.AI · 2 COMPONENTS

Collect reviewed human answers through hosted handoffs, plus local templates and config validation.

+3 this week 69 Trust /100

Last scanned (8 hours ago)

Scores higher than 54% of remote servers

Reachable. Last reached 6 Nov 2026.

Category Developer Tools

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability77
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 824 tokens (~68/item across 12 items; 11 tools + 1 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
  • Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (27% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
  • Supports UI / widget rendering.Pass
What we tested

Checks we ran (14)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol
  • Capabilities

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Oct 26 0
    • Tool “talkform.delete_webhook” rewrote its description, which is the text the model reads security
    • Tool “talkform.get_handoff” rewrote its description, which is the text the model reads security
    • Tool “talkform.get_webhook” rewrote its description, which is the text the model reads security
    • Tool “talkform.register_agent” rewrote its description, which is the text the model reads security
    • Tool “talkform.get_result” rewrote its description, which is the text the model reads security
    • Tool “talkform.configure_webhook” rewrote its description, which is the text the model reads security
    • Tool “talkform.create_handoff” rewrote its description, which is the text the model reads security
    • Tool “talkform.delete_handoff” rewrote its description, which is the text the model reads security
    • Stability: unverified → 0.03 ▲ functional
    • “talkform.delete_webhook” added an optional parameter “projectId” cosmetic
    • “talkform.get_webhook” added an optional parameter “projectId” cosmetic
    • “talkform.configure_webhook” added an optional parameter “projectId” cosmetic
    • “talkform.create_handoff” added an optional parameter “projectId” cosmetic
  • 27 Oct 26 65

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 6 Nov 2026 · Probed https://www.talkform.ai/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.talkform.ai CN=YR1,O=Let's Encrypt,C=US 11 Sept 2026 10 Dec 2026 RSA 2048 SHA256-RSA 6944c621a375dd75059ce83f7439b92af97
SANs: *.talkform.ai, talkform.ai
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.talkform.ai. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ai. DS published 1814, 3799 8, 8 Verified
talkform.ai. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy default-src 'self'; base-uri 'self'; object-src 'none'; script-src 'self' 'unsafe-inline' https://clerk.talkform.ai https://challenges.cloudflare.com https://*.protect.clerk.com https://analytics.ahrefs.com https://us-assets.i.posthog.com https://www.googletagmanager.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; img-src 'self' data: blob: https:; font-src 'self' https://fonts.gstatic.com data:; connect-src 'self' https://clerk.talkform.ai https://*.protect.clerk.com:* https://api.openai.com https://analytics.ahrefs.com https://us.i.posthog.com https://us-assets.i.posthog.com https://www.google-analytics.com https://analytics.google.com; media-src 'self' blob:; frame-src 'self' https://clerk.talkform.ai https://challenges.cloudflare.com https://*.protect.clerk.com https://share.synthesia.io https://*.synthesia.io https://*.heygen.com; frame-ancestors 'self' https:; form-action 'self'; worker-src 'self' blob:; manifest-src 'self'
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(self), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.talkform.ai/api/mcp Verified 200
http (plaintext) http://www.talkform.ai/api/mcp HTTPS enforced 308 https://www.talkform.ai/api/mcp
MCP tools · 11 exposed · ~706 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
talkform.configure_webhook ~69

Configures one HTTPS endpoint for completed handoffs in an authorized project. Replaces any active endpoint and returns the signing secret once. Requires handoffs:write permission. Optional projectId selects an owned OAuth account project.

NameTypeReqDescription
projectIdstring––
urlstringyes–

No output schema declared.

No examples provided.

talkform.create_handoff ~125

Stores a validated voice interview or text interview and returns a private respondent link plus shareText. config.fields[].promptTitle supplies each question; config.branding.fromName and branding.purpose identify the originating product. Omitted mode selects voice; text mode is available. Requires a project API key or scoped OAuth. Optional projectId selects an owned account project; required when the account has several projects. Matching idempotency keys replay the existing handoff.

NameTypeReqDescription
configobjectyes–
idempotencyKeystringyes–
projectIdstring––

No output schema declared.

No examples provided.

talkform.delete_handoff ~43

Permanently deletes stored configuration and answers for an authorized project or OAuth account. Requires user confirmation and handoffs:delete permission.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

talkform.delete_webhook ~49

Disables an authorized project's active webhook and cancels pending deliveries. Requires handoffs:write permission. Optional projectId selects an owned OAuth account project.

NameTypeReqDescription
projectIdstring––

No output schema declared.

No examples provided.

talkform.get_handoff ~39

Checks a hosted handoff owned by the authorized project or OAuth account. Requires handoffs:read permission.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

talkform.get_result ~54

Returns completed structured answers for an authorized project or OAuth account with handoffs:read permission. Pending results return result_pending. Results expire 7 days after submission. No transcript is returned.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

talkform.get_template ~31

Returns one public template as a structured, reviewable conversational form draft.

NameTypeReqDescription
idstringyes–
NameTypeReqDescription
draftobjectyes–
previewobjectyes–

No examples provided.

talkform.get_webhook ~55

Returns active webhook metadata and recent delivery metadata for an authorized project. Signing secrets are never returned. Requires handoffs:read permission. Optional projectId selects an owned OAuth account project.

NameTypeReqDescription
projectIdstring––

No output schema declared.

No examples provided.

talkform.list_templates ~20

Lists the public conversational-form templates available for review.

Input schema present but exposes no named parameters.

NameTypeReqDescription
templatesarrayyes–

No examples provided.

talkform.prepare_form ~122

Turns interview questions into a validated, shareable form draft. Each promptTitle is the respondent-facing question; fromName, purpose and branding identify the originating product. Optional theme colors use hex values. Returns a draft without storing or publishing it.

NameTypeReqDescription
brandingobject––
descriptionstring––
fieldsarrayyes–
fromNamestring––
instructionsstring––
modestring––
purposestring––
themeobject––
titlestringyes–
NameTypeReqDescription
draftobjectyes–
previewobjectyes–

No examples provided.

talkform.register_agent ~99

Creates a persistent machine-owned project and returns its API key secret once. No email, sign-in, or human identity is created. A UUIDv4 idempotency key identifies registration; retries never replay the secret. Machine projects receive 10 hosted handoffs per day. Voice is available in hosted interviews under shared realtime limits.

NameTypeReqDescription
environmentstring––
idempotencyKeystringyes–
namestring––

No output schema declared.

No examples provided.

Install

How do I install the Talkform MCP server?

Talkform is a hosted endpoint at https://www.talkform.ai/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · www.talkform.ai

# add to Claude Code
claude mcp add --transport http msanchezgrice-talkform 'https://www.talkform.ai/api/mcp'
Common questions

What is the Talkform MCP server?

Talkform is an MCP server listed in the public MCP registry as io.github.msanchezgrice/talkform. Collect reviewed human answers through hosted handoffs, plus local templates and config validation. This page covers its hosted endpoint (https://www.talkform.ai/api/mcp).

Is the Talkform MCP server safe to use?

Talkform scores 69 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Talkform MCP server expose?

Talkform exposes 11 tools: talkform.list_templates, talkform.get_template, talkform.prepare_form, talkform.register_agent, talkform.create_handoff, and 6 more. Their descriptions and schemas cost roughly 706 tokens of context every time the server is loaded.

Does the Talkform MCP server require authentication?

No. We connected to Talkform without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Talkform MCP server still maintained?

Talkform is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Talkform MCP server?

VerifyMCP ran 14 checks on Talkform, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.