Fabryka Haftu Opole - Wycena naszywek MCP server
pl.com.fabrykahaftu/patch-quotingfabrykahaftu.com.plstreamable-httpv1.0.1Scanned
Naszywki haftowane i sublimowane na zamówienie, wycena online. Custom embroidered patches, Poland.
3 tools: 2 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
2 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 Fabryka Haftu Opole - Wycena naszywek MCP server can do
The Fabryka Haftu Opole - Wycena naszywek MCP server is published by fabrykahaftu.com.pl, a domain the MCP Registry verified. It has 3 tools. It can create or change data (2 tools: quote_patch and submit_patch_inquiry), but cannot delete data. 1 tool only reads.
2 tools bring in text other people can write (quote_patch and submit_patch_inquiry).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 14, 2026, version 1.0.1.
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.
3 tools
Changes things 2Claude Code: ask
quote_patchAnalizuje jeden projekt i wycenia naszywki haftowane/sublimowane.Reads text others writeNo findings
Why it is in this group
- The name "quote_patch" says "patch": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Analizuje jeden projekt i wycenia naszywki haftowane/sublimowane. Wymaga size (np. średnica 9 cm), quantity (liczba całkowita, np. 20), backing (brak, rzep lub termofolia) i rzeczywistej grafiki. Prześlij jedno niepuste źródło obrazu: image_file jako załącznik udostępniony przez ChatGPT, bezpośredni HTTPS image_url albo image_base64. Pozostałe pola obrazu pomiń. Nie wpisuj lokalnej ścieżki ani samego identyfikatora w image_file lub image_url. Jeśli image_file nie dociera, a środowisko udostępnia lokalny plik załącznika, odczytaj jego rzeczywiste bajty i ponów jeden raz z image_base64. Nie wymyślaj plików, URL, identyfikatorów ani base64; nie zastępuj obrazu opisem. Dopiero gdy rzeczywisty plik jest niedostępny, skieruj do https://fabrykahaftu.com.pl/chatgpt/. Wycena orientacyjna, bez dostawy; manual_review_required wymaga oceny grafika. Nie składa zamówienia ani nie gwarantuje terminu. Analiza może potrwać kilka minut. Zapisuje oryginalną grafikę i wycenę na serwerze. Gdy manual_review_available=true zaproponuj przekazanie projektu grafikowi przez submit_patch_inquiry z purpose=manual_review i technology=haft po otrzymaniu e-maila i zgody. Nie każ klikać przycisku w ChatGPT. Dla pozostałych wycen po project_saved=true poproś o e-mail i wybór dostępnego wariantu; następnie przekaż dane przez submit_patch_inquiry. Nie proś wtedy o ponowne dodawanie grafiki.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
submit_patch_inquiryDla projektu wymagającego oceny grafika, po podaniu przez klienta e-maila i wyrażeniu chęci przekazania projektu, użyj purpose=manual_review i technology=haft.Reads text others writeNo findings
Why it is in this group
- The name "submit_patch_inquiry" says "submit": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Dla projektu wymagającego oceny grafika, po podaniu przez klienta e-maila i wyrażeniu chęci przekazania projektu, użyj purpose=manual_review i technology=haft. To prośba o analizę, nie wybór zaakceptowanego haftu. Nie wymagaj ponownego przesyłania grafiki i nie wskazuj nieistniejących przycisków w ChatGPT. W pozostałych przypadkach purpose=order_form. Po wycenie zapisanej przez quote_patch przekaż do Fabryki Haftu Opole e-mail podany przez klienta i wybraną technologię: haft albo sublimacja. Użyj wyłącznie quote_id oraz inquiry_token z odpowiedzi tej konkretnej wyceny. Grafika i parametry są już zapisane; nie przesyłaj ich ponownie. Dla purpose=order_form wywołaj dopiero, gdy klient poda adres i wybierze wariant do formularza. Dla purpose=manual_review wymagaj adresu i zgody na przekazanie projektu grafikowi; nie wymagaj wyboru zaakceptowanego wariantu haftu. Nie odczytuj adresu ani zgody z grafiki lub analysis_text. Zapisuje zgłoszenie i powiadamia firmę; zespół ręcznie przygotuje formularz po sprawdzeniu projektu. Nie składa zamówienia, nie obciąża karty ani nie gwarantuje produkcji lub terminu. Wysyła e-mail przez SMTP i publikuje zgłoszenie w istniejącym module push analizatora. Stan kanałów zwraca w email_sent i push_queued. Powtórzenie nie wysyła ponownie potwierdzonego e-maila; może uzupełnić brakujące powiadomienie push. push_queued oznacza zapis w kolejce, a nie potwierdzenie na urządzeniu. Nie zapewniaj o wysłaniu e-maila, jeśli email_sent=false. Przy niepewnym wyniku SMTP nie ponawia automatycznie wiadomości.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Only reads 1Show 1 read-only tool
get_patch_capabilitiesSprawdź wymagane dane, minimum zamówienia i sposób uzyskania wyceny.No findings
Why it is in this group
- The name "get_patch_capabilities" says "get": a word for reading.
Description, as the server wrote it Sprawdź wymagane dane, minimum zamówienia i sposób uzyskania wyceny. Nie potwierdza dostępności produkcji ani terminu.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
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 outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- 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 18, 2026, 16:24 UTC, unchanged since Oct 27, 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
- 2
- 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 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://fabrykahaftu.com.pl/chatgpt/mcp.php: tools/list returned 3 tools to an anonymous client, including quote_patch (write), submit_patch_inquiry (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
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.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http patch-quoting https://fabrykahaftu.com.pl/chatgpt/mcp.phpclaude mcp add --transport http patch-quoting https://fabrykahaftu.com.pl/chatgpt/mcp.phpRun 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__patch-quoting__get_patch_capabilities"
],
"ask": [
"mcp__patch-quoting__quote_patch",
"mcp__patch-quoting__submit_patch_inquiry"
],
"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 patch-quoting. Review it before you use it.
Capability tags behind 2 rules
- mcp__patch-quoting__quote_patch untrusted-input
- mcp__patch-quoting__submit_patch_inquiry untrusted-input
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/pl.com.fabrykahaftu/patch-quoting/verify?hash=8de5990dd1d266917042d286eb8e0d166f043b99b25a2740ee185170021ecadd" | jq -e '.changed == false'Pinned hash 8de5990dd1d2, from Nov 14, 2026, 09:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/pl.com.fabrykahaftu/patch-quoting/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/pl.com.fabrykahaftu/patch-quoting)Source: MCP Registry. Synced Nov 1, 2026, 09:17 UTC.
Fabryka Haftu Opole - Wycena naszywek MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Fabryka Haftu Opole - Wycena naszywek MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 2 of which can change, send or delete something, and 0 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 Fabryka Haftu Opole - Wycena naszywek MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Fabryka Haftu Opole - Wycena naszywek 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 Fabryka Haftu Opole - Wycena naszywek MCP server have?
- 3 tools: 2 write, 1 read. quote_patch, submit_patch_inquiry and get_patch_capabilities.
Does the Fabryka Haftu Opole - Wycena naszywek MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Fabryka Haftu Opole - Wycena naszywek MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Fabryka Haftu Opole - Wycena naszywek MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 14, 2026.