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.

io.github.theluckystrike/meeting-notes-transcript-summary

REMOTE · MCP.ZOVO.ONE

Turn meeting notes or transcripts into a clean structured summary document from chat.

Available components

−13 this week 80 Trust /100

Last scanned (14 hours ago)

Scores higher than 77% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Documents and Files

Recent critical change

Authorization (17 Nov 2026). See the changelog before you install this server.

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 Usability78
  • 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
  • Context-footprint check failed: tool/resource definitions use about 2590 tokens (~161/item across 16 items; 14 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management96
  • Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 0 breaking changes, 1 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage95
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 84% of tool parameters carry a description.Partial
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 16 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
What we tested

Checks we ran (13)

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

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.

  • 17 Nov 26 −13
    • Authorization: pass → fail ▼ critical
    • Stability: pass → fail ▼ security
  • 12 Nov 26 0
    • Stability: 0.97 → pass security
  • 11 Nov 26 +1

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

  • 10 Nov 26 −1
    • Stability: pass → 0.93 functional
  • 8 Nov 26 0
    • Stability: 0.97 → pass security
  • 7 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Stability: pass → 0.97 functional
  • 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
  • 2 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “doc_delete_upload” is now declared destructive security
    • Tool “doc_upload” is now declared destructive security
    • Destructive annotations: All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. functional
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 21 Nov 2026 · Probed https://mcp.zovo.one/mcp/meeting-notes-transcript-summary

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=zovo.one CN=WE1,O=Google Trust Services,C=US 31 Oct 2026 29 Jan 2027 ECDSA 256 ECDSA-SHA256 39e1adfa4eb6500e0e3d48868766e3e9
SANs: zovo.one, mcp.zovo.one, *.mcp.zovo.one
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.zovo.one. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
one. DS published 64939 8 Verified
zovo.one. 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=15552000; includeSubDomains; preload
x-content-type-options nosniff

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.zovo.one/mcp/meeting-notes-transcript-summary Verified 200
http (plaintext) http://mcp.zovo.one/mcp/meeting-notes-transcript-summary HTTPS enforced 301 https://mcp.zovo.one/mcp/meeting-notes-transcript-summary
MCP tools · 14 exposed · ~2,365 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
business_set ~399

Store the sender details printed on every proposal, contract and letter, plus the currency, VAT, terms and prefix defaults. It writes the SAME shared profile as the invoice server's business_set.

NameTypeReqDescription
addressstring–Postal address, newlines allowed
bankstring–Bank name / BIC
brand_colorstring–Letterhead colour as a hex code, e.g. 1F3864 (Pro)
default_currencystring–ISO code, e.g. EUR, USD. Default EUR
default_tax_ratenumber–Default VAT percent, quoted on proposals
emailstring–Your own email address, printed on every letterhead. Leave it out unless the user gave it: a document that shows an address nobody supplied is worse than one that shows [add: email]
ibanstring–IBAN or account number for payment
invoice_prefixstring–Reference prefix used by mcp-invoice; this profile has the same field shape as mcp-invoice, so one profile serves both
logo_pathstring–Path to a PNG or JPG logo for the letterhead (Pro)
namestringyesYour business or freelancer name, printed on the letterhead of every proposal, contract and letter
payment_terms_daysnumber–Default days until payment is due. Default 14
phonestring–Your own phone number. Same rule as email: only if the user gave it
tax_ratenumber–Alias for default_tax_rate
timezonestring–IANA zone you work in, e.g. Europe/Warsaw. Shared with time-tracker and timezone as your home zone
vatnumber–Alias for default_tax_rate
vat_idstring–VAT / tax registration id
vat_ratenumber–Alias for default_tax_rate

No output schema declared.

No examples provided.

contract_create ~229

Call this tool to produce a freelance service agreement .docx. Returns the reference, the fee and the file path. It is a template skeleton for a lawyer to review, not legal advice. Free tier: 3 agreements per month.

NameTypeReqDescription
clausesarray–Extra clauses to append, one paragraph each
clientstringyesThe client's legal name
end_datestring–YYYY-MM-DD, omit for an open-ended engagement
feeobjectyes–
governing_lawstring–e.g. 'the laws of Poland'
out_pathstring–Where to write the .docx. Defaults to the data directory
overwriteboolean–Replace out_path if a file is already there. Default false: an existing file is never overwritten
servicesstringyesWhat you will do, one or two sentences. The document adds parties, term, fee and schedule, plus standard clauses on intellectual property, confidentiality, independent contractor status, liability, t…
start_datestringyesYYYY-MM-DD

No output schema declared.

No examples provided.

doc_create ~213

Call this tool to write a real .docx file from structured sections. Returns the file path, the number of blocks written and the layout used. Free and unlimited.

NameTypeReqDescription
datestring–Date line for the letter layout, default today
out_pathstring–Where to write the .docx. Defaults to the data directory
overwriteboolean–Replace out_path if a file is already there. Default false: an existing file is never overwritten
recipientstring–Addressee block for the letter layout
sectionsarrayyesSections in order. Each one may carry a heading, paragraphs, a bullet or numbered list and a table
stylestring–Layout, default plain. plain is the title and the body; letter adds a sender block top right, a date and the addressee; proposal adds a letterhead band and a cover title
titlestringyesDocument title, used as the top heading and the file name

No output schema declared.

No examples provided.

doc_delete_upload ~56

Delete one document uploaded for your token: name is the name it was uploaded under, without .docx. doc_files lists them. A name nothing is stored under is refused and nothing is deleted.

NameTypeReqDescription
namestringyes–

No output schema declared.

No examples provided.

doc_files ~20

List the documents uploaded for your token, with their sizes.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

doc_fill_template ~183

Call this tool to replace {{placeholders}} in a .docx and write a new file, reporting what was filled, unfilled or ignored. Call it with no values to list them. Free: templates up to 10 placeholders.

NameTypeReqDescription
docx_base64string–The .docx template itself, base64-encoded, instead of uploading it first
out_pathstring–Where to write the filled .docx. Defaults to <template>-filled.docx
overwriteboolean–Replace out_path if a file is already there. Default false: an existing file is never overwritten
template_pathstring–Name of a template uploaded with doc_upload
valuesobject–Placeholder name to value, e.g. {client: "Acme", fee: "EUR 4,500.00"}

No output schema declared.

No examples provided.

doc_from_markdown ~182

Call this tool to turn markdown into a .docx, returning the file and a count of blocks by type. Headings, lists, GFM tables and code fences are honoured. Empty markdown is refused, and so is overwriting without the flag.

NameTypeReqDescription
markdownstringyesThe markdown source. ATX headings, paragraphs, bullet and numbered lists, GFM pipe tables and fenced code blocks as monospace are honoured, as are **bold**, *italic* and `code` inline
out_pathstring–Where to write the .docx. Defaults to the data directory
overwriteboolean–Replace out_path if a file is already there. Default false: an existing file is never overwritten
stylestring––
titlestring–Document title; defaults to the first heading in the markdown

No output schema declared.

No examples provided.

doc_read ~110

Call this tool to extract the text of an existing .docx. Returns an outline of the headings and the full text in document order, or the block structure. Free and unlimited.

NameTypeReqDescription
docx_base64string–The .docx itself, base64-encoded, instead of uploading it first
formatstring–text (default) returns the readable text, json returns the block structure in document order
pathstring–Name of a document uploaded with doc_upload

No output schema declared.

No examples provided.

doc_to_html ~122

Call this tool to convert a .docx to semantic HTML you can open in a browser and print to PDF. Returns the path of the .html file. This is the supported PDF route; no PDF is rendered here. Free and unlimited.

NameTypeReqDescription
out_pathstring–Name for the downloaded .html file
overwriteboolean–Replace out_path if a file is already there. Default false: an existing file is never overwritten
pathstringyesName of a document uploaded with doc_upload, or a document this server just wrote

No output schema declared.

No examples provided.

doc_upload ~302

Send an existing Word document to this hosted endpoint. There is no filesystem here, so instead of a path you upload the file once with doc_upload and then pass its name as `path` to doc_read, doc_to_html and doc_fill_template. Give exactly one of docx_base64 or url. url: fetch a public file instead of pasting base64 (recommended above about 10 KB): a 13 KB base64 paste can take minutes to write out, while a url costs one line and the fetch happens here (10 second timeout, at most 3 redirects, public http(s) hosts only, 2 MB cap). Uploads are kept for your token between calls; doc_read and doc_fill_template also take docx_base64 directly; that file is stored under the name you give (default 'inline' / 'template') and can be removed with doc_delete_upload. Documents this server writes come back as a download link valid for one hour.

NameTypeReqDescription
docx_base64string–The .docx file, base64-encoded
namestringyesName to refer to this document by: 1-64 characters of letters, digits, underscore or dash, e.g. "contract"
urlstring–url: fetch a public file instead of pasting base64 (recommended above about 10 KB). Public http(s) only; private, link-local and this endpoint's own zone are refused

No output schema declared.

No examples provided.

license_activate ~76

Turn Pro on for this connection with key, an MCPL1.<payload>.<signature> issued at checkout for this server or the bundle. Data under your token stays; a wrong or expired key changes nothing. license_status confirms it.

NameTypeReqDescription
keystringyesLicense key from checkout, MCPL1.<payload>.<signature>

No output schema declared.

No examples provided.

license_status ~55

Report this endpoint's licence state for your token as JSON: the product, the tier free or pro, why it is not Pro, and the checkout URL. Call it to explain a free-tier refusal. No arguments, nothing changes.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

proposal_create ~269

Call this tool to produce a client-ready .docx proposal from summary, scope, deliverables, timeline, price and terms. Returns the reference, the total and the file path. Free tier: 3 proposals or contracts per month.

NameTypeReqDescription
clientstringyesClient name, printed as 'Prepared for'. The letterhead comes from your business_set profile
deliverablesarray–What the client receives, one bullet each. Omitted from the document if not given or empty
out_pathstring–Where to write the .docx. Defaults to the data directory
overwriteboolean–Replace out_path if a file is already there. Default false: an existing file is never overwritten
priceobjectyes–
project_titlestringyesProject title
scopearray–What is in scope, one bullet each. Omitted from the document if not given or empty
summarystring–One or two paragraphs on the problem and the approach. Omitted from the document if not given
timelinearray–Phases and their durations, rendered as a table. Omitted from the document if not given or empty
valid_untilstring–YYYY-MM-DD, the date the quote expires

No output schema declared.

No examples provided.

proposal_update ~149

Rewrite an existing proposal in place from its reference. Only the fields you pass change; the rest comes from the data stored at creation. Returns the fields that changed and the file path.

NameTypeReqDescription
clientstring––
deliverablesarray––
priceobject––
project_titlestring––
referencestringyesThe proposal reference, e.g. PROP-2026-0001. The same file and the same reference number are kept, so no second document is burned against the free-tier monthly count
scopearray––
summarystring––
timelinearray––
valid_untilstring––

No output schema declared.

No examples provided.

Install

How do I install the io.github.theluckystrike/meeting-notes-transcript-summary MCP server?

io.github.theluckystrike/meeting-notes-transcript-summary is a hosted endpoint at https://mcp.zovo.one/mcp/meeting-notes-transcript-summary, 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 · mcp.zovo.one

# add to Claude Code
claude mcp add --transport http theluckystrike-meeting-notes-transcript-summary 'https://mcp.zovo.one/mcp/meeting-notes-transcript-summary'
Common questions

What is the io.github.theluckystrike/meeting-notes-transcript-summary MCP server?

io.github.theluckystrike/meeting-notes-transcript-summary is an MCP server listed in the public MCP registry as io.github.theluckystrike/meeting-notes-transcript-summary. Turn meeting notes or transcripts into a clean structured summary document from chat. This page covers its hosted endpoint (https://mcp.zovo.one/mcp/meeting-notes-transcript-summary).

Is the io.github.theluckystrike/meeting-notes-transcript-summary MCP server safe to use?

io.github.theluckystrike/meeting-notes-transcript-summary scores 80 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 io.github.theluckystrike/meeting-notes-transcript-summary MCP server expose?

io.github.theluckystrike/meeting-notes-transcript-summary exposes 14 tools: business_set, doc_create, doc_from_markdown, doc_read, doc_to_html, and 9 more. Their descriptions and schemas cost roughly 2,365 tokens of context every time the server is loaded.

Does the io.github.theluckystrike/meeting-notes-transcript-summary MCP server require authentication?

No. We connected to io.github.theluckystrike/meeting-notes-transcript-summary without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.theluckystrike/meeting-notes-transcript-summary MCP server still maintained?

io.github.theluckystrike/meeting-notes-transcript-summary is still listed as active in the MCP registry. We last reached this channel on 21 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 io.github.theluckystrike/meeting-notes-transcript-summary MCP server?

VerifyMCP ran 13 checks on io.github.theluckystrike/meeting-notes-transcript-summary, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 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.