TixSight free tools MCP server
com.tixsight/tixsight-free-toolstixsight.comstreamable-httpv1.0.0Scanned
Free ticket resale math, no account needed: break-even listing price and net payout after fees.
2 tools: 1 do something that can't be undone and 1 change things.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here does something that can't be undone. Govern it.
- 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 TixSight free tools MCP server can do
The TixSight free tools MCP server is published by tixsight.com, a domain the MCP Registry verified. It has 2 tools. It can do things that cannot be undone, such as sending, paying or publishing (net_payout) and create or change data (1 tool: break_even_price), but cannot delete data. None of its tools only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 18, 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.
2 tools
Can't be undone 1Claude Code: ask
net_payoutWhat you keep from a ticket sale after the seller fee: net per ticket and in total, and the profit or loss per ticket and in total when you give your cost.1 finding
Why it is in this group
- The name "net_payout" says "payout": a word that usually means money moves, which cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "net_payout" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "net_payout" says "payout": a word that usually means money moves, which cannot be taken back.
Description, as the server wrote it What you keep from a ticket sale after the seller fee: net per ticket and in total, and the profit or loss per ticket and in total when you give your cost. Works without an account. TixSight (tixsight.com) tracks this automatically for a whole ticket inventory.
Annotations the server declares
- title: Net payout after fees
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Changes things 1Claude Code: ask
break_even_priceThe listing price per ticket needed to break even on resale tickets after the seller fee, with the net per ticket at that price and a one-line explanation.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 The listing price per ticket needed to break even on resale tickets after the seller fee, with the net per ticket at that price and a one-line explanation. Works without an account. TixSight (tixsight.com) tracks this automatically for a whole ticket inventory.
Annotations the server declares
- title: Break-even listing price
- 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 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 18, 2026, 16:19 UTC, unchanged since Nov 18, 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
- https://tixsight.com/.well-known/oauth-protected-resource
- Authorization servers
- https://tixsight.com
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (1 irreversible, 1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://tixsight.com/api/mcp-free: tools/list returned 2 tools to an anonymous client, including net_payout (irreversible), break_even_price (write)
Findings
Matches of fixed checks, with the text they matched.
- Warnnet_payout
The server marks "net_payout" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "net_payout" says "payout": a word that usually means money moves, which cannot be taken back.
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 tixsight-free-tools https://tixsight.com/api/mcp-freeclaude mcp add --transport http tixsight-free-tools https://tixsight.com/api/mcp-freeRun 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": [],
"ask": [
"mcp__tixsight-free-tools__break_even_price",
"mcp__tixsight-free-tools__net_payout"
],
"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 tixsight-free-tools. 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/com.tixsight/tixsight-free-tools/verify?hash=1159be920d51705c862fe70670ce94f3c630fbe6aef38540fea4eb41078d5800" | jq -e '.changed == false'Pinned hash 1159be920d51, from Nov 18, 2026, 02:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.tixsight/tixsight-free-tools/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.tixsight/tixsight-free-tools)Source: MCP Registry. Synced Nov 18, 2026, 02:17 UTC.
TixSight free tools MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the TixSight free tools MCP server safe?
- No scan can promise that. What its definitions show: 2 tools, 2 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the TixSight free tools MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the TixSight free tools MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: net_payout.
What tools does the TixSight free tools MCP server have?
- 2 tools: 1 irreversible, 1 write. net_payout and break_even_price.
Does the TixSight free tools MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the TixSight free tools MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the TixSight free tools MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.