Transica
REMOTE · TRANSICA-MCP.TRANSICA.DEV
Checks whether a web page is ready for AI agents and whether an MCP server meets directory rules
Available components
Last scanned (10 hours ago)
Scores higher than 79% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Search and Retrieval
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. 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 298 tokens (~149/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 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 2 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
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.
- 5 Nov 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.
- 3 Nov 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.
- 2 Nov 26 −2
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 124 → 149 ▼ functional
- Schema quality: excellent → good functional
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 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.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 24 Oct 26 75
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 5 Nov 2026 · Probed https://transica-mcp.transica.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=transica.dev | CN=WE1,O=Google Trust Services,C=US | 30 Sept 2026 | 29 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 49804f59f7f097f513b79173edbccfe7 |
| SANs: transica.dev, *.transica.dev | ||||||
| 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 insecure
Validation of transica-mcp.transica.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| transica.dev. | absent | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://transica-mcp.transica.dev/mcp | Verified | 200 | |
| http (plaintext) | http://transica-mcp.transica.dev/mcp | HTTPS enforced | 301 | https://transica-mcp.transica.dev/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_mcp_server_directory_rules Check MCP server directory rules ~132
Returns server details, tool counts, directory-specific results, individual checks, and a full report link after connecting to a public remote MCP server and reading its tool list without calling tools. Use it when someone asks whether an MCP server meets ChatGPT or Claude directory requirements; for scanning a regular webpage's AI readiness, use scan_webpage_ai_readiness instead. Pass url as the public MCP server address to check its connection, sign-in, domain, and tool rules.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Address of the public remote MCP server to check, such as https://mcp.example.com/mcp. |
No output schema declared.
No examples provided.
scan_webpage_ai_readiness Scan a webpage for AI readiness ~116
Returns a readiness score, passed and failed checks, category results, top fixes, limitations, and a report link for one public webpage. Use it when someone asks whether a webpage is accessible and usable by AI agents; for checking an MCP server's directory compliance, use check_mcp_server_directory_rules instead. Pass url to scan the page directly, or use the reportUrl to revisit the detailed results.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Public webpage address to scan, such as https://example.com or example.com/pricing. |
No output schema declared.
No examples provided.
How do I install the Transica MCP server?
Transica is a hosted endpoint at https://transica-mcp.transica.dev/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 · transica-mcp.transica.dev
claude mcp add --transport http dev-transica-transica 'https://transica-mcp.transica.dev/mcp'
What is the Transica MCP server?
Transica is an MCP server listed in the public MCP registry as dev.transica/transica. Checks whether a web page is ready for AI agents and whether an MCP server meets directory rules. This page covers its hosted endpoint (https://transica-mcp.transica.dev/mcp).
Is the Transica MCP server safe to use?
Transica scores 79 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 Transica MCP server expose?
Transica exposes 2 tools: scan_webpage_ai_readiness, check_mcp_server_directory_rules. Their descriptions and schemas cost roughly 248 tokens of context every time the server is loaded.
Does the Transica MCP server require authentication?
No. We connected to Transica without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Transica MCP server still maintained?
Transica is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.