Signature Maker MCP server
io.signaturemaker/signature-makersignaturemaker.iostreamable-httpv1.0.0Scanned
Write your name as a signature in 24 styles, with PNG, SVG and a practice sheet.
5 tools: 4 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
4 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Signature Maker MCP server can do
The Signature Maker MCP server is published by signaturemaker.io, a domain the MCP Registry verified. It has 5 tools. It can create or change data (4 tools: make_signature, handwritten_signature, signature_ideas and signature_practice_sheet), but cannot delete data. 1 tool only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 2 findings (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 11, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
5 tools
Changes things 4Claude Code: ask
handwritten_signatureWrites a name in six handwritten hand styles for each of three name formats, full name, initial and surname, and monogram, 18 versions in all.1 finding
Why it is in this group
- The description's first verb is "write": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "handwritten_signature" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "write": a word for a change.
Description, as the server wrote it Writes a name in six handwritten hand styles for each of three name formats, full name, initial and surname, and monogram, 18 versions in all. Returns a PNG picture and an SVG for each version.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Handwritten signature versions
make_signatureWrites a name as a signature in one of 24 script styles, with name format, slant, size, underline, ink and natural hand.1 finding
Why it is in this group
- The description's first verb is "write": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "make_signature" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "write": a word for a change.
Description, as the server wrote it Writes a name as a signature in one of 24 script styles, with name format, slant, size, underline, ink and natural hand. Returns the image as a transparent PNG and an SVG, plus a link to the same signature on Signature Maker.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Make a signature
signature_ideasGives ideas for opening a signature with the first capital letter of a name, A to Z: three ways to draw the capital, how to start and join it, and six hand styles shown on the name…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Gives ideas for opening a signature with the first capital letter of a name, A to Z: three ways to draw the capital, how to start and join it, and six hand styles shown on the name.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Signature ideas
signature_practice_sheetMakes a practice sheet for a name with six boxes to trace and six to write freehand.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Makes a practice sheet for a name with six boxes to trace and six to write freehand. Returns a PDF on A4 or US Letter and a picture of the page.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Signature practice sheet
Only reads 1Show 1 read-only tool
signature_stylesLists the 24 signature styles with the name written in each, filterable by elegant, casual or bold.No findings
Why it is in this group
- The description's first verb is "list": a word for reading.
Description, as the server wrote it Lists the 24 signature styles with the name written in each, filterable by elegant, casual or bold. Returns a picture of the name in every style and a link to open each style on Signature Maker.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Signature styles
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 19, 2026, 17:22 UTC, unchanged since Nov 12, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 4
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://signaturemaker.io/api/mcp: tools/list returned 5 tools to an anonymous client, including make_signature (write), handwritten_signature (write), signature_ideas (write), signature_practice_sheet (write)
Findings
Matches of fixed checks, with the text they matched.
- Warnmake_signature
The server marks "make_signature" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "write": a word for a change.
The server marks "handwritten_signature" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "write": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http signature-maker https://signaturemaker.io/api/mcpclaude mcp add --transport http signature-maker https://signaturemaker.io/api/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__signature-maker__signature_styles"
],
"ask": [
"mcp__signature-maker__make_signature",
"mcp__signature-maker__handwritten_signature",
"mcp__signature-maker__signature_ideas",
"mcp__signature-maker__signature_practice_sheet"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as signature-maker. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.signaturemaker/signature-maker/verify?hash=b9af8f1f149c1169eb1ea75cc337a2731437758da997bdea120b4c363a2442b8" | jq -e '.changed == false'Pinned hash b9af8f1f149c, from Nov 11, 2026, 18:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.signaturemaker/signature-maker/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.signaturemaker/signature-maker)Source: MCP Registry · repository. Synced Nov 11, 2026, 18:18 UTC.
Signature Maker MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Signature Maker MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, 4 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Signature Maker MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Signature Maker MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Signature Maker MCP server have?
- 5 tools: 4 write, 1 read. make_signature, handwritten_signature, signature_ideas, signature_practice_sheet and signature_styles.
Does the Signature Maker MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Signature Maker MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Signature Maker MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 11, 2026.