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.

Tinplate Edge AI Safety, Security & Data Validation

REMOTE · API.TINPLATE.DEV

39 MCP tools (7 free, 39 Pro/Team): AI guardrails, PII/secrets, MCP lint, SSRF, JSON & EU checks.

Available components

71 Trust /100

Last scanned (13 hours ago)

Scores higher than 56% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Security

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 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. 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1064 tokens (~152/item across 7 items; 7 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 Management0
  • Stability check failed: schema churn in the 6 days we've observed: 42 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
  • Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
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.

  • 19 Nov 26 +1
    • DNSSEC: fail → pass ▲ security
    • Server version: 1.0.53 → 1.0.54 functional
  • 18 Nov 26 +1
    • Tool “tinplate_agent_action_receipts” was removed ▼ security
    • Tool “tinplate_agent_action_receipts_verify” was removed ▼ security
    • Tool “tinplate_agent_code_guard” was removed ▼ security
    • Tool “tinplate_command_sql_guard” was removed ▼ security
    • Tool “tinplate_consent_tokens” was removed ▼ security
    • Tool “tinplate_consent_tokens_verify” was removed ▼ security
    • Tool “tinplate_content_provenance” was removed ▼ security
    • Tool “tinplate_email_dns_generator” was removed ▼ security
    • Tool “tinplate_eu_vat_iban_vat” was removed ▼ security
    • Tool “tinplate_hallucination_diff” was removed ▼ security
    • Tool “tinplate_hu_business_validator” was removed ▼ security
    • Tool “tinplate_ics_sanitizer” was removed ▼ security
    • Tool “tinplate_jwt_jwk_inspector” was removed ▼ security
    • Tool “tinplate_llm_messages_guard” was removed ▼ security
    • Tool “tinplate_llm_output_guard” was removed ▼ security
    • Tool “tinplate_locale_value_parser” was removed ▼ security
    • Tool “tinplate_pii_redactor” was removed ▼ security
    • Tool “tinplate_pii_redactor_restore” was removed ▼ security
    • Tool “tinplate_prompt_cache_budgeter” was removed ▼ security
    • Tool “tinplate_rag_chunker” was removed ▼ security
    • Tool “tinplate_regex_safety” was removed ▼ security
    • Tool “tinplate_schema_diff” was removed ▼ security
    • Tool “tinplate_secret_scanner_restore” was removed ▼ security
    • Tool “tinplate_semver_lockfile_judge” was removed ▼ security
    • Tool “tinplate_ssrf_firewall” was removed ▼ security
    • Tool “tinplate_tabular_rag_cleaner” was removed ▼ security
    • Tool “tinplate_tool_call_validator” was removed ▼ security
    • Tool “tinplate_ua_bot_parser” was removed ▼ security
    • Tool “tinplate_url_normalizer” was removed ▼ security
    • Tool “tinplate_workday_holiday” was removed ▼ security
    • Tool “tinplate_workday_holiday_add” was removed ▼ security
    • Tool “tinplate_workday_holiday_is_workday” was removed ▼ security
    • Tool “tinplate_command_sql_guard” rewrote its description, which is the text the model reads security
    • Tool “tinplate_email_dns” rewrote its description, which is the text the model reads security
    • Tool “tinplate_email_dns_generator” rewrote its description, which is the text the model reads security
    • Tool “tinplate_eu_vat_iban” rewrote its description, which is the text the model reads security
    • Tool “tinplate_eu_vat_iban_vat” rewrote its description, which is the text the model reads security
    • Tool “tinplate_hu_business_validator” rewrote its description, which is the text the model reads security
    • Tool “tinplate_pii_redactor” rewrote its description, which is the text the model reads security
    • Tool “tinplate_pii_redactor_restore” rewrote its description, which is the text the model reads security
    • Tool “tinplate_schema_diff” rewrote its description, which is the text the model reads security
    • Tool “tinplate_tabular_rag_cleaner” rewrote its description, which is the text the model reads security
    • Tool “tinplate_url_normalizer” rewrote its description, which is the text the model reads security
    • Tool “tinplate_workday_holiday” rewrote its description, which is the text the model reads security
    • Tool “tinplate_workday_holiday_add” rewrote its description, which is the text the model reads security
    • Tool “tinplate_workday_holiday_is_workday” rewrote its description, which is the text the model reads security
    • Schema quality: 180 → 152 ▲ functional
    • Server version: 1.0.52 → 1.0.53 functional
    • Server version: 1.0.49 → 1.0.52 functional
    • Server version: 1.0.46 → 1.0.49 functional
    • Server version: 1.0.45 → 1.0.46 functional
    • “tinplate_hallucination_diff” reworded the description of “use_ai_judge” cosmetic
    • “tinplate_prompt_cache_budgeter” reworded the description of “model” cosmetic
    • “tinplate_ssrf_firewall” reworded the description of “inspect_redirects” cosmetic
    • “tinplate_consent_tokens” reworded the description of “secret” cosmetic
  • 17 Nov 26 +5
    • Stability: 0.03 → fail ▼ security
    • Tool “tinplate_eu_id_validator” was removed ▼ security
    • Tool “tinplate_eu_vat_calculator” was removed ▼ security
    • Tool “tinplate_html_to_markdown” was removed ▼ security
    • Tool “tinplate_invoice_validator” was removed ▼ security
    • Tool “tinplate_peppol_ubl_invoice” was removed ▼ security
    • Tool “tinplate_robots_llms_analyzer” was removed ▼ security
    • Tool “tinplate_sanctions_screener” was removed ▼ security
    • Tool “tinplate_security_headers” was removed ▼ security
    • Tool “tinplate_signup_fraud” was removed ▼ security
    • Tool “tinplate_webhook_verify” was removed ▼ security
    • HTTPS: fail → pass ▲ security
    • Tool “tinplate_agent_action_receipts” rewrote its description, which is the text the model reads security
    • Tool “tinplate_agent_action_receipts_verify” rewrote its description, which is the text the model reads security
    • Tool “tinplate_content_provenance” rewrote its description, which is the text the model reads security
    • Tool “tinplate_eu_vat_iban” rewrote its description, which is the text the model reads security
    • Tool “tinplate_eu_vat_iban_vat” rewrote its description, which is the text the model reads security
    • Tool “tinplate_ssrf_firewall” rewrote its description, which is the text the model reads security
    • Schema quality: 157 → 180 ▼ functional
    • Tool coverage: 75% → 100% ▲ functional
    • Server version: 1.0.40 → 1.0.45 functional
    • Server version: 1.0.39 → 1.0.40 functional
    • “tinplate_hallucination_diff” reworded the description of “use_ai_judge” cosmetic
    • “tinplate_agent_action_receipts” reworded the description of “action_input” cosmetic
    • “tinplate_agent_action_receipts” reworded the description of “action_output” cosmetic
    • “tinplate_agent_action_receipts” reworded the description of “agent_id” cosmetic
    • “tinplate_agent_action_receipts” reworded the description of “issued_at_epoch” cosmetic
    • “tinplate_agent_action_receipts” reworded the description of “kid” cosmetic
    • “tinplate_agent_action_receipts” reworded the description of “policy_decision” cosmetic
    • “tinplate_agent_action_receipts” reworded the description of “prev_receipt_hash” cosmetic
    • “tinplate_agent_action_receipts” reworded the description of “session_id” cosmetic
    • “tinplate_agent_action_receipts” reworded the description of “tool_name” cosmetic
    • “tinplate_agent_action_receipts” reworded the description of “ttl_seconds” cosmetic
    • “tinplate_agent_action_receipts_verify” reworded the description of “chain” cosmetic
    • “tinplate_agent_action_receipts_verify” reworded the description of “expected_input” cosmetic
    • “tinplate_agent_action_receipts_verify” reworded the description of “expected_output” cosmetic
    • “tinplate_agent_action_receipts_verify” reworded the description of “jwks” cosmetic
    • “tinplate_agent_action_receipts_verify” reworded the description of “keys” cosmetic
    • “tinplate_agent_action_receipts_verify” reworded the description of “now_epoch” cosmetic
    • “tinplate_agent_action_receipts_verify” reworded the description of “receipt_token” cosmetic
    • “tinplate_agent_action_receipts_verify” reworded the description of “secret” cosmetic
    • “tinplate_consent_tokens” reworded the description of “purpose” cosmetic
    • “tinplate_consent_tokens_verify” reworded the description of “expected_scope” cosmetic
    • “tinplate_consent_tokens_verify” reworded the description of “now_epoch” cosmetic
    • “tinplate_consent_tokens_verify” reworded the description of “token” cosmetic
    • “tinplate_email_dns_generator” reworded the description of “adkim” cosmetic
    • “tinplate_email_dns_generator” reworded the description of “allow_a” cosmetic
    • “tinplate_email_dns_generator” reworded the description of “allow_mx” cosmetic
    • “tinplate_email_dns_generator” reworded the description of “aspf” cosmetic
    • “tinplate_email_dns_generator” reworded the description of “custom_includes” cosmetic
    • “tinplate_email_dns_generator” reworded the description of “dmarc_pct” cosmetic
    • “tinplate_email_dns_generator” reworded the description of “dmarc_policy” cosmetic
    • “tinplate_email_dns_generator” reworded the description of “dmarc_subdomain_policy” cosmetic
    • “tinplate_email_dns_generator” reworded the description of “ip4” cosmetic
    • “tinplate_email_dns_generator” reworded the description of “ip6” cosmetic
    • “tinplate_email_dns_generator” reworded the description of “rua_emails” cosmetic
    • “tinplate_email_dns_generator” reworded the description of “ruf_emails” cosmetic
    • “tinplate_email_dns_generator” reworded the description of “spf_policy” cosmetic
    • “tinplate_eu_vat_iban_vat” reworded the description of “verify_vies” cosmetic
    • “tinplate_pii_redactor_restore” reworded the description of “redacted_text” cosmetic
    • “tinplate_pii_redactor_restore” reworded the description of “tokens” cosmetic
    • “tinplate_prompt_cache_budgeter” reworded the description of “blocks” cosmetic
    • “tinplate_prompt_cache_budgeter” reworded the description of “estimated_cache_hits” cosmetic
    • “tinplate_prompt_cache_budgeter” reworded the description of “expected_output_tokens” cosmetic
    • “tinplate_prompt_cache_budgeter” reworded the description of “max_context_tokens” cosmetic
    • “tinplate_prompt_cache_budgeter” reworded the description of “model” cosmetic
    • “tinplate_secret_scanner_restore” reworded the description of “redacted_text” cosmetic
    • “tinplate_secret_scanner_restore” reworded the description of “tokens” cosmetic
    • “tinplate_semver_lockfile_judge” reworded the description of “after” cosmetic
    • “tinplate_semver_lockfile_judge” reworded the description of “before” cosmetic
    • “tinplate_semver_lockfile_judge” reworded the description of “fail_on_zero_ver_minor” cosmetic
    • “tinplate_semver_lockfile_judge” reworded the description of “include_dev_dependencies” cosmetic
    • “tinplate_workday_holiday” reworded the description of “end_date” cosmetic
    • “tinplate_workday_holiday” reworded the description of “include_end” cosmetic
    • “tinplate_workday_holiday” reworded the description of “include_start” cosmetic
    • “tinplate_workday_holiday” reworded the description of “start_date” cosmetic
    • “tinplate_workday_holiday_add” reworded the description of “date” cosmetic
    • “tinplate_workday_holiday_add” reworded the description of “days” cosmetic
    • “tinplate_workday_holiday_is_workday” reworded the description of “date” cosmetic
  • 16 Nov 26 +3
    • HSTS header: fail → pass ▲ security
    • Stability: unverified → 0.03 ▲ functional
    • Server version: 1.0.38 → 1.0.39 functional
    • Server version: 1.0.36 → 1.0.38 functional
    • Server version: 1.0.33 → 1.0.36 functional
    • Server version: 1.0.30 → 1.0.33 functional
    • “tinplate_agent_action_receipts” added an optional parameter “private_jwk” cosmetic
    • “tinplate_agent_action_receipts_verify” added an optional parameter “jwks” cosmetic
    • “tinplate_email_dns” added an optional parameter “records” cosmetic
    • “tinplate_html_to_markdown” added an optional parameter “cache” cosmetic
    • “tinplate_html_to_markdown” added an optional parameter “include_hidden” cosmetic
    • “tinplate_tabular_rag_cleaner” added an optional parameter “normalize_decimals” cosmetic
    • “tinplate_url_normalizer” added an optional parameter “strip_userinfo” cosmetic
    • “tinplate_secret_scanner” reworded the description of “types” cosmetic
    • “tinplate_agent_action_receipts” reworded the description of “secret” cosmetic
    • “tinplate_agent_code_guard” reworded the description of “language” cosmetic
    • “tinplate_consent_tokens” reworded the description of “secret” cosmetic
    • “tinplate_eu_vat_calculator” reworded the description of “amount” cosmetic
    • “tinplate_webhook_verify” reworded the description of “secret” cosmetic
    • “tinplate_agent_action_receipts” made “secret” optional cosmetic
    • “tinplate_consent_tokens” made “secret” optional cosmetic
    • “tinplate_webhook_verify” made “secret” optional cosmetic
  • 15 Nov 26 61

    First indexed and scored.

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://api.tinplate.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=tinplate.dev CN=WE1,O=Google Trust Services,C=US 14 Nov 2026 12 Feb 2027 ECDSA 256 ECDSA-SHA256 6dc437fb01ff03e3133893e5c2d7d6f6
SANs: tinplate.dev, api.tinplate.dev, *.api.tinplate.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 secure

Validation of api.tinplate.dev. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
tinplate.dev. DS published 2371 13 Verified
api.tinplate.dev. 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 no-referrer
permissions-policy geolocation=(), microphone=(), camera=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.tinplate.dev/mcp Verified 200
http (plaintext) http://api.tinplate.dev/mcp HTTPS enforced 301 https://api.tinplate.dev/mcp
MCP tools · 7 exposed · ~1,064 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
tinplate_cron_explainer ~173

Cron & Schedule Explainer & Validator API: Validate cron expressions, translate to plain English, and compute next N runs with DST. (Endpoint: POST /v1/cron-explainer)

NameTypeReqDescription
countinteger–Number of upcoming execution times to compute (1 to 50).
expressionstringyes5-field UNIX cron, 6-field cron (with leading seconds), or macro (@hourly, @daily, @weekly, @monthly, @yearly, @reboot). Supports L, W, and #.
from_timestring–Optional ISO-8601 starting timestamp (defaults to current UTC time).
timezonestring–IANA timezone name (e.g. 'UTC', 'Europe/Budapest', 'America/New_York').

No output schema declared.

No examples provided.

tinplate_email_dns ~132

Email DNS Deliverability Auditor API: Audit MX, SPF 10-lookup limits, DMARC, DKIM, and MTA-STS with a 0–100 score. (Endpoint: POST /v1/email-dns)

NameTypeReqDescription
dkim_selectorsarray–Optional custom DKIM selectors to probe in addition to common defaults.
domainstringyesDomain name or email address to audit (e.g. 'tinplate.dev' or 'hello@tinplate.dev').
recordsobject–Optional pre-fetched DNS records for offline auditing without live DNS-over-HTTPS queries.

No output schema declared.

No examples provided.

tinplate_eu_vat_iban ~106

EU VAT & IBAN/BIC Checksum Validator API: Validate IBAN MOD-97 checksums, BIC/SWIFT codes, and EU27 VAT formats offline. (Endpoint: POST /v1/eu-vat-iban/iban)

NameTypeReqDescription
bicstring–Optional BIC/SWIFT code (8 or 11 characters) to validate and cross-check country.
ibanstringyesIBAN to validate (spaces allowed).

No output schema declared.

No examples provided.

tinplate_json_heal ~94

Broken JSON & LLM Output Healer API: Repair malformed or truncated LLM JSON outputs into valid, schema-checked JSON in 1 ms. (Endpoint: POST /v1/json-heal)

NameTypeReqDescription
rawstringyesMalformed JSON or LLM output string (max 256 KB).
schemaobject–Optional JSON Schema (draft subset) to validate the healed JSON against without eval.

No output schema declared.

No examples provided.

tinplate_mcp_manifest_linter ~100

MCP Server Manifest & Tool Security Linter API: Audit MCP server manifests for hidden tool poisoning, shell risks, and excessive permissions. (Endpoint: POST /v1/mcp-manifest-linter)

NameTypeReqDescription
manifestobjectyesMCP server manifest JSON (tools/resources/prompts payload and/or mcpServers launch config).
strict_schemasboolean–When true, flags missing additionalProperties: false and unbounded string parameters.

No output schema declared.

No examples provided.

tinplate_prompt_guard ~249

Prompt Injection Detection API: Catch prompt injections, role hijacks, and encoded jailbreaks in user inputs and RAG chunks. (Endpoint: POST /v1/prompt-guard)

NameTypeReqDescription
block_thresholdinteger–Explicit risk score threshold at or above which verdict is 'block' (overrides sensitivity preset).
contextstring–Context hint (defaults to 'user_input'). 'tool_output' and 'rag_document' boost indirect injection risk (+15); 'llm_output' boosts exfiltration/leakage signals (+20).
sensitivitystring–Preset threshold profile: 'low' (block >= 85, review >= 45), 'medium' (default, block >= 70, review >= 30), or 'high' (block >= 50, review >= 20). Overridden if block_threshold is explicitly set.
textstringyesUser prompt, retrieved RAG document chunk, tool output, or LLM output to inspect (max 256 KB).
use_ai_judgeboolean–Enable optional Cloudflare Workers AI second-pass semantic judge (default false). Adds ~150-400 ms inference latency when true.

No output schema declared.

No examples provided.

tinplate_secret_scanner ~210

Log Redact & Secret Scanner API: Detect and mask leaked API keys, JWTs, and private keys in logs, diffs, and prompts. (Endpoint: POST /v1/secret-scanner)

NameTypeReqDescription
diff_only_addedboolean–When true on a unified git diff, ignores removed lines ('-...') and only scans added/context lines.
min_entropynumber–Minimum Shannon entropy (bits/char) required for GENERIC_HIGH_ENTROPY matches.
modestring–'token' replaces each unique secret with [SECRET_<TYPE>_<N>] and returns a caller-only map; 'mask' replaces with [REDACTED:<TYPE>]; 'partial' preserves a short prefix/suffix.
textstringyesRaw log output, .env file, code snippet, or unified git diff to scan.
typesarray–Optional allowlist of secret types to scan for. Scans all 28 types when omitted.

No output schema declared.

No examples provided.

Install

How do I install the Tinplate Edge AI Safety, Security & Data Validation MCP server?

Tinplate Edge AI Safety, Security & Data Validation is a hosted endpoint at https://api.tinplate.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 · api.tinplate.dev

# add to Claude Code
claude mcp add --transport http dev-tinplate-edge-apis 'https://api.tinplate.dev/mcp'
Common questions

What is the Tinplate Edge AI Safety, Security & Data Validation MCP server?

Tinplate Edge AI Safety, Security & Data Validation is an MCP server listed in the public MCP registry as dev.tinplate/edge-apis. 39 MCP tools (7 free, 39 Pro/Team): AI guardrails, PII/secrets, MCP lint, SSRF, JSON & EU checks. This page covers its hosted endpoint (https://api.tinplate.dev/mcp).

Is the Tinplate Edge AI Safety, Security & Data Validation MCP server safe to use?

Tinplate Edge AI Safety, Security & Data Validation scores 71 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 Tinplate Edge AI Safety, Security & Data Validation MCP server expose?

Tinplate Edge AI Safety, Security & Data Validation exposes 7 tools: tinplate_prompt_guard, tinplate_mcp_manifest_linter, tinplate_json_heal, tinplate_secret_scanner, tinplate_email_dns, and 2 more. Their descriptions and schemas cost roughly 1,064 tokens of context every time the server is loaded.

Does the Tinplate Edge AI Safety, Security & Data Validation MCP server require authentication?

No. We connected to Tinplate Edge AI Safety, Security & Data Validation without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Tinplate Edge AI Safety, Security & Data Validation MCP server still maintained?

Tinplate Edge AI Safety, Security & Data Validation 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 Tinplate Edge AI Safety, Security & Data Validation MCP server?

VerifyMCP ran 13 checks on Tinplate Edge AI Safety, Security & Data Validation, 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.