TraceTail
REMOTE · TRACETAIL.IO
Browser fingerprinting for web apps: integration code for any framework, docs search and pricing.
Available components
Last scanned (19 hours ago)
Scores higher than 92% of remote servers
Reachable. Last reached 22 Oct 2026.
Category Security
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 Security83
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability88
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1962 tokens (~57/item across 34 items; 6 tools + 28 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
- Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
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.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 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.
- 11 Oct 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.
- 10 Oct 26 +2
No change was recorded against any check on this day. Stability & Change Management went from 3 to 17. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Oct 26 77
First indexed and scored.
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 22 Oct 2026 · Probed https://tracetail.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=tracetail.io | CN=WE1,O=Google Trust Services,C=US | 16 Oct 2026 | 14 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 1f9c9d124a7b260113e6400791ab8b5e |
| SANs: tracetail.io, *.tracetail.io | ||||||
| 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 secure
Validation of tracetail.io. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| tracetail.io. | present | 2371 | 13 | Verified |
| tracetail.io. | Verified address RRset verified with the apex keys |
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; preload |
| content-security-policy | default-src 'none'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-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://tracetail.io/mcp | Verified | 200 | |
| http (plaintext) | http://tracetail.io/mcp | HTTPS enforced | 301 | https://tracetail.io/mcp |
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 →
check_setup_link Check a TraceTail setup link ~89
Where a setup link stands. The first check after the person finishes returns the API keys (and the server key, if requested); they are not shown again. While they're still on the page, check again every few seconds.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The id create_setup_link returned (sl_…). |
| token | string | yes | The token create_setup_link returned (tt_setup_…). |
No output schema declared.
No examples provided.
create_setup_link Create a TraceTail setup link ~157
Gets TraceTail API keys for the person you work for: returns a link to give them, where they sign in with an emailed code and add a card or continue without a card, and a token. Then call check_setup_link with its id and token every few seconds: once they've finished, it returns an API key for each site (and a server key if you asked), once.
| Name | Type | Req | Description |
|---|---|---|---|
| domains | array | yes | The sites to create API keys for, like ["example.com", "localhost"]; include localhost for local development. |
| string | – | The person's email, if you know it: it prefills the page. | |
| serverKey | boolean | – | Also create a server key, so the backend can verify identifications. |
No output schema declared.
No examples provided.
get_integration_code Get TraceTail integration code ~181
The exact install command and code to add TraceTail browser fingerprinting (a stable visitor ID for each browser, without cookies) to a web app built with the given framework, with where each file goes. Works without an API key (keyless mode, no sign-up); pass the site's public API key to fill it in.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | The site's public TraceTail API key (tt_…), if it has one. Leave out to use the placeholder. |
| firstPartyPath | string | – | The path of the site's first-party proxy, e.g. /k3v9, to load TraceTail from the site's own domain. |
| framework | string | yes | The app's framework: html (a plain script tag), javascript (any bundler), react, nextjs, vue, nuxt, angular or svelte. |
No output schema declared.
No examples provided.
get_pricing Get TraceTail pricing ~71
TraceTail's prices and limits (1,000 identification requests free every month, then $0.10 per 1,000), with the monthly cost at a given volume and the same volume on Fingerprint (FingerprintJS) for comparison.
| Name | Type | Req | Description |
|---|---|---|---|
| monthlyRequests | integer | – | Expected identification requests a month. |
No output schema declared.
No examples provided.
read_docs_page Read a TraceTail page ~61
Returns a page of the TraceTail site as Markdown: "/docs" (the full documentation), "/pricing", "/vs-fingerprintjs", "/" (overview) or a blog post.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | The page's path on tracetail.io. |
No output schema declared.
No examples provided.
search_docs Search the TraceTail documentation ~83
Searches TraceTail's documentation, pricing, comparison and blog for a topic (e.g. "next.js", "rate limits", "ad blockers", "GDPR", "server-side verification") and returns the matching sections with their URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many results to return (default 5). |
| query | string | yes | What to look for. |
No output schema declared.
No examples provided.
How do I install the TraceTail MCP server?
TraceTail is a hosted endpoint at https://tracetail.io/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 · tracetail.io
claude mcp add --transport http io-tracetail-tracetail 'https://tracetail.io/mcp'
What is the TraceTail MCP server?
TraceTail is an MCP server listed in the public MCP registry as io.tracetail/tracetail. Browser fingerprinting for web apps: integration code for any framework, docs search and pricing. This page covers its hosted endpoint (https://tracetail.io/mcp).
Is the TraceTail MCP server safe to use?
TraceTail scores 85 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 TraceTail MCP server expose?
TraceTail exposes 6 tools: get_integration_code, search_docs, read_docs_page, get_pricing, create_setup_link, check_setup_link. Their descriptions and schemas cost roughly 642 tokens of context every time the server is loaded.
Does the TraceTail MCP server require authentication?
No. We connected to TraceTail without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the TraceTail MCP server still maintained?
TraceTail is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.