212medya Growth Check
REMOTE · 212MEDYA.COM.TR
Audit a public website for B2B marketing readiness and AI search visibility.
Available components
Last scanned (5 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Marketing and SEO
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 Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (request_expert_review). See how to fix → View diagnostics → Fail
- 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 Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 923 tokens (~307/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.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 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 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.
- 4 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 3 Nov 26 66
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://212medya.com.tr/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=212medya.com.tr | CN=WE1,O=Google Trust Services,C=US | 29 Oct 2026 | 27 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | aaf3a05b801af21713b2b509bb1bc56d |
| SANs: 212medya.com.tr, *.212medya.com.tr | ||||||
| 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 212medya.com.tr. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| tr. | present | 46909 | 13 | Verified |
| com.tr. | present | 29425 | 13 | Verified |
| 212medya.com.tr. | present | 2371 | 13 | Verified |
| 212medya.com.tr. | 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=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://212medya.com.tr/mcp | Verified | 200 | |
| http (plaintext) | http://212medya.com.tr/mcp | HTTPS enforced | 301 | https://212medya.com.tr/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 →
audit_website Audit a website for B2B marketing ~284
Use this when the user wants a marketing audit of a public website, especially a B2B, manufacturer, exporter or service-business site: technical SEO, mobile performance (Google PageSpeed Insights), lead conversion (quote/contact forms, calls to action, click-to-call), trust signals (references, certifications, privacy policy, cookie consent), analytics and ad tracking tags, and language versions for target export markets. It fetches only the given page plus robots.txt and the sitemap, honors robots.txt, and returns category scores and prioritized fixes in English. Results for the same page are cached for up to 6 hours. Do not use it for AI crawler or AI search questions (use check_ai_search_readiness), for pages behind a login, or to monitor sites the user is not evaluating.
| Name | Type | Req | Description |
|---|---|---|---|
| include_performance | boolean | – | Run the Google PageSpeed Insights mobile test (adds up to 30 seconds). Defaults to true. |
| target_languages | array | – | Optional ISO 639-1 codes of the languages the business sells in, e.g. ["en","de","ar"]. Used to check for matching language versions. Defaults to ["en"]. |
| url | string | yes | Public website address to check, for example "example.com" or "https://www.example.com/en/". Only this page is analyzed, plus the site’s robots.txt and sitemap. |
| Name | Type | Req | Description |
|---|---|---|---|
| category_scores | object | yes | – |
| counts | object | yes | – |
| detected_tags | array | yes | – |
| findings | array | yes | – |
| notes | array | yes | – |
| overall_score | number | yes | – |
| top_priorities | array | yes | – |
| url | string | yes | – |
No examples provided.
check_ai_search_readiness Check AI search readiness ~211
Use this when the user asks whether a public website can be crawled, read and cited by AI assistants and AI search (ChatGPT search, Google AI Overviews, Bing/Copilot, Perplexity, Claude), or why AI tools do not show their company. It checks robots.txt rules for each AI crawler, Content-Signal directives, noindex/nosnippet restrictions, whether content is readable without JavaScript, FAQ content, Organization schema and sameAs links, the sitemap and llms.txt, and returns scores, a crawler access table and prioritized fixes in English. It does not measure how often the brand is actually mentioned in AI answers and does not test CDN or firewall bot blocking. Do not use it for general SEO or conversion audits (use audit_website).
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Public website address to check, for example "example.com" or "https://www.example.com/en/". Only this page is analyzed, plus the site’s robots.txt and sitemap. |
| Name | Type | Req | Description |
|---|---|---|---|
| category_scores | object | yes | – |
| counts | object | yes | – |
| crawler_access | array | yes | – |
| findings | array | yes | – |
| notes | array | yes | – |
| readiness_score | number | yes | – |
| top_priorities | array | yes | – |
| url | string | yes | – |
No examples provided.
request_expert_review Request a 212medya expert review ~321
Use this only when the user explicitly asks to be contacted by 212medya, the digital marketing agency that publishes this app — for example to get help fixing audit findings or a proposal for SEO, AI search visibility, ads, web design or international marketing. Before calling, show the user exactly which details will be sent (name, email, company, optional website and phone, topic, message) and get their confirmation. The details are emailed to 212medya's team and stored in 212medya's lead database; a specialist replies by email. Each call sends a new request, so do not retry after a success. Do not use it to save or share audit results, or when the user only wants information.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | Company or organization name. |
| string | yes | Email address where 212medya should reply. | |
| message | string | yes | Short description of what the user needs, written or approved by the user. May summarize relevant audit findings the user wants reviewed. |
| name | string | yes | The user's full name. |
| phone | string | – | Phone number, only if the user chose to share it. |
| preferred_language | string | – | Language the user prefers for the reply. |
| topic | string | yes | Main area the user wants help with. |
| user_confirmed | boolean | yes | Must be true, and only after the user has seen the details above and agreed to send them to 212medya. |
| website | string | – | Company website, if the user provided it. |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | – |
| submitted | boolean | yes | – |
No examples provided.
How do I install the 212medya Growth Check MCP server?
212medya Growth Check is a hosted endpoint at https://212medya.com.tr/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 · 212medya.com.tr
claude mcp add --transport http tr-com-212medya-growth-check 'https://212medya.com.tr/mcp'
What is the 212medya Growth Check MCP server?
212medya Growth Check is an MCP server listed in the public MCP registry as tr.com.212medya/growth-check. Audit a public website for B2B marketing readiness and AI search visibility. This page covers its hosted endpoint (https://212medya.com.tr/mcp).
Is the 212medya Growth Check MCP server safe to use?
212medya Growth Check scores 67 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 212medya Growth Check MCP server expose?
212medya Growth Check exposes 3 tools: audit_website, check_ai_search_readiness, request_expert_review. Their descriptions and schemas cost roughly 816 tokens of context every time the server is loaded.
Does the 212medya Growth Check MCP server require authentication?
No. We connected to 212medya Growth Check without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the 212medya Growth Check MCP server still maintained?
212medya Growth Check 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.