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.

Tailor

REMOTE · MCP.TAILOR.TECH

Tailor Platform for AI assistants: search, list and read the platform documentation.

Available components

0 this week 89 Trust /100

Last scanned (12 hours ago)

Scores higher than 96% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Code Search and Documentation

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 Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability86
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 395 tokens (~131/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (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.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
    • Server version: 2026.11.04-0 → 2026.11.09-0 functional
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 7 Nov 26 0
    • Stability: 0.97 → pass security
  • 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
  • 5 Nov 26 0
    • Stability: 0.97 → pass security
  • 4 Nov 26 0
    • Stability: pass → 0.97 functional
    • Server version: 2026.10.22-0 → 2026.11.04-0 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.tailor.tech/

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=tailor.tech CN=Certainly Intermediate R1,O=Certainly,C=US 6 Nov 2026 6 Dec 2026 RSA 2048 SHA256-RSA 78dbc2835711c192874b13d3cc16422cf893
SANs: *.tailor.tech, tailor.tech
CN=Certainly Intermediate R1,O=Certainly,C=US (CA) CN=Starfield Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US 22 Jun 2022 21 Jun 2032 RSA 2048 SHA256-RSA 11831cde4cb573e5

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.tailor.tech. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
tech. DS published 2185 13 Verified
tailor.tech. 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
x-content-type-options nosniff
x-frame-options DENY
referrer-policy origin-when-cross-origin

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.tailor.tech/ Verified 200
http (plaintext) http://mcp.tailor.tech/ HTTPS enforced 301 https://mcp.tailor.tech/
MCP tools · 3 exposed · ~395 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
fetch_knowledge ~118

Return the Markdown source of one documentation page, addressed by an id from search_knowledge or list_knowledge. The first line is the page's URL, for citation. Long pages come back as a heading outline instead; pass section to read one part of them.

NameTypeReqDescription
idstringyespage identifier exactly as returned by search_knowledge or list_knowledge, for example docs:sdk/quickstart.md
sectionstring–return only this section of the page, matched case-insensitively against its level-two headings

No output schema declared.

No examples provided.

list_knowledge ~125

List the documentation table of contents: the id, title, source, section and summary of every page. Use this to see what exists when a search does not find the right words; prefer search_knowledge when you know what you are looking for. Narrow the listing with source or section, since the full listing is large and is cut at 500 entries.

NameTypeReqDescription
sectionstring–restrict the listing to one table-of-contents section, matched case-insensitively
sourcestring–restrict the listing to one knowledge source; omit to list every source

No output schema declared.

No examples provided.

search_knowledge ~152

Search the body text of Tailor Platform's public documentation and return matching pages with an excerpt. Start here for most questions, then pass an id to fetch_knowledge to read a page in full. Matching is literal and case-insensitive, so prefer the exact terms that would appear in the docs. This covers published documentation only; it cannot see a user's own application data.

NameTypeReqDescription
limitinteger–maximum number of pages to return; defaults to 10, capped at 50
querystringyeswords to look for in the documentation body, matched case-insensitively as a substring
sourcestring–restrict the search to one knowledge source; omit to search every source

No output schema declared.

No examples provided.

Install

How do I install the Tailor MCP server?

Tailor is a hosted endpoint at https://mcp.tailor.tech/, 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.tailor.tech

# add to Claude Code
claude mcp add --transport http tech-tailor-mcp 'https://mcp.tailor.tech/'
Common questions

What is the Tailor MCP server?

Tailor is an MCP server listed in the public MCP registry as tech.tailor/mcp. Tailor Platform for AI assistants: search, list and read the platform documentation. This page covers its hosted endpoint (https://mcp.tailor.tech/).

Is the Tailor MCP server safe to use?

Tailor scores 89 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 Tailor MCP server expose?

Tailor exposes 3 tools: fetch_knowledge, list_knowledge, search_knowledge. Their descriptions and schemas cost roughly 395 tokens of context every time the server is loaded.

Does the Tailor MCP server require authentication?

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

Is the Tailor MCP server still maintained?

Tailor 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 Tailor MCP server?

VerifyMCP ran 13 checks on Tailor, 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.