← Back to search
github-tuteliq/claude-plugin

Tuteliq/claude-plugin

Trust and safety MCP server for AI agents. Detect grooming, bullying, self-harm, CSAM, fraud and deepfakes across text, voice, image and video, then triage a moderation queue and produce KOSA, DSA and GDPR evidence. Around 80 tools plus workflow skills for Claude Code and Cowork. OAuth sign-in, no API key to configure.

DECISION SUMMARY
Production trust decision

Block For Production

Production readiness
Needs remediation
Score
61.5
Rank suppressed while production readiness shows a blocking verdict.
Confidence
High
Based on evidence completeness, recency, and validation density.
Evidence age
2.7h old
Freshness: fresh. Snapshot trustsnap_42e4662a0e6cc372.
Top risk drivers
  • Utility Coverage
  • Step Up Auth
  • Recovery Semantics
Recommended actions
  • Respond to server card describes a different server: card says "tuteliq docs mcp", live says "tuteliq"
  • Add an explicit confirm/dry-run parameter or two-step confirmation flow to write, delete, exec, and egress-capable tool…
  • Align MCP-Protocol-Version, MCP-Session-Id, DELETE teardown, and expired-session handling with the transport spec.
Next action
revalidate, add safeguards, export policy
write/admin actions need confirmation safeguards + high-risk tools need review
Compare alternatives Export policy Open report JSON Dispute this assessment
Observed Attention
No observed attention
No observed attention in the current 30-day window.
  • No segmented attention signals observed in the current window.
Bucketed signal based on recent segmented Verify telemetry. Crawler and evaluator activity is not treated as confirmed human demand.
Status
Healthy
Score
61.5
Transport
streamable-http
Tools
3
DISPUTE THIS ASSESSMENT

Dispute this assessment

If any published claim about this server -- its score, a risk flag, a capability classification, or its taxonomy -- is factually wrong, tell us what evidence shows and we will review it. This does not require claiming or verifying ownership of the server first.

Verify responds to disputes within 5 business days and resolves them within 15.

Dispute history

No disputes filed for this server.

Risks

Security posture
Tools analyzed
3
High-risk tools
1
Destructive tools
0
Exec tools
0
Egress tools
1
Secret tools
0
Bulk-access tools
0
Risk distribution
low:2, high:1
Tool capability & risk inventory
ToolCapabilitiesRiskFindingsNotesEvidence
search_tuteliq read Low freeform input surface No explicit safeguard hints detected.
Schema & evidence
{
  "annotations": {
    "destructiveHint": false,
    "idempotentHint": true,
    "openWorldHint": false,
    "readOnlyHint": true
  },
  "capabilities": [
    "read"
  ],
  "input_schema": {
    "$schema": "http://json-schema.org/draft-07/schema#",
    "additionalProperties": false,
    "properties": {
      "query": {
        "description": "Search query",
        "type": "string"
      }
    },
    "required": [
      "query"
    ],
    "type": "object"
  },
  "risk_flags": [
    "freeform_input_surface"
  ]
}
Dispute this classification
query_docs_filesystem_tuteliq read Low freeform input surface Safeguards hinted in metadata.
Schema & evidence
{
  "annotations": {
    "destructiveHint": false,
    "idempotentHint": true,
    "openWorldHint": false,
    "readOnlyHint": true
  },
  "capabilities": [
    "read"
  ],
  "input_schema": {
    "$schema": "http://json-schema.org/draft-07/schema#",
    "additionalProperties": false,
    "properties": {
      "command": {
        "description": "A shell command to run against the virtualized documentation filesystem (e.g., `rg -il \"keyword\" /`, `tree / -L 2`, `head -80 /path/file.mdx`).",
        "type": "string"
      }
    },
    "required": [
      "command"
    ],
    "type": "object"
  },
  "risk_flags": [
    "freeform_input_surface"
  ]
}
Dispute this classification
submit_feedback write network filesystem High arbitrary network egress freeform input surface filesystem mutation No explicit safeguard hints detected.
Schema & evidence
{
  "annotations": {
    "destructiveHint": false,
    "idempotentHint": false,
    "openWorldHint": true,
    "readOnlyHint": false
  },
  "capabilities": [
    "write",
    "network",
    "filesystem"
  ],
  "input_schema": {
    "$schema": "http://json-schema.org/draft-07/schema#",
    "additionalProperties": false,
    "properties": {
      "feedback": {
        "description": "A clear description of the documentation issue or suggestion \u2014 what is incorrect, outdated, missing, or confusing.",
        "minLength": 1,
        "type": "string"
      },
      "path": {
        "description": "The documentation page path the feedback is about (e.g., the page you were reading, such as `/quickstart`).",
        "minLength": 1,
        "type": "string"
      }
    },
    "required": [
      "path",
      "feedback"
    ],
    "type": "object"
  },
  "risk_flags": [
    "arbitrary_network_egress",
    "freeform_input_surface",
    "filesystem_mutation"
  ]
}
Dispute this classification
Write-action governance
Governance status
Error
Safe to publish
Auth boundary
public_or_unclear
Blast radius
Medium
High-risk tools
1
Confirmation signals
none
Safeguard count
1

Status detail: 1 high-risk tool(s) are exposed without a clear auth boundary; 1 safeguard(s) and 0 confirmation signal(s) detected.

ToolRiskFlagsSafeguards
submit_feedback High arbitrary network egress freeform input surface filesystem mutation no
Recommended runtime policy
Recommended runtime policy
Allow with approval
Default policy stance (medium risk ceiling, write actions require approval, no OAuth requirement). Answers "what may an agent do right now" -- a separate question from production readiness, which answers "how suitable is this server for adoption." Customize via policy export.

No policy blockers under the default policy stance.

Action-controls diff
Snapshot changed
no
Disabled-by-default candidates
none
New actions
ActionRiskFlags
No newly added actions.
Changed actions
ActionChange typesRisk
No materially changed actions.
Critical alerts
High/critical-severity alerts
7
Production verdicts degrade quickly when high or critical-severity alerts are active.

Compatibility

Client compatibility verdicts

Client compatibility only means the server shape can work with a client. Production trust decision and write-action publishing are evaluated separately so a client-compatible server can still be blocked for production.

Client compatibility: ChatGPT
Not client-compatible
OpenAI connectors expect OAuth for remote server auth.; Dynamic client registration materially improves connector setup.; OAuth interoperability should be strong.; The tool surface is not limited to search/fetch-style read tools.; This client profile expects a read/search-only tool surface, but write, delete, or exec-capable tools are present.; OAuth is not configured, so this client cannot authenticate without additional setup.
Confidence: high (77.5)
Evidence provenance
Winner: live_validation
Supporting sources: live_validation, history, server_card
Disagreements: none
  • initializeOK
  • tools_listOK
  • transport_compliance_probeWarning
  • step_up_auth_probeMissing
  • connector_replay_probeOK — Frozen tool snapshots must survive refresh.
  • request_association_probeWarning — Roots, sampling, and elicitation should stay request-scoped.
Client compatibility: Claude
Not client-compatible
The tool surface is not limited to search/fetch-style read tools.; This client profile expects a read/search-only tool surface, but write, delete, or exec-capable tools are present.; OAuth is not configured, so this client cannot authenticate without additional setup.; Not yet safe for company-knowledge use: requires a search/fetch-only surface with no export, bulk, mutating, or high-blast-radius exposure.; Not yet safe for the Messages API remote MCP path: requires OAuth, a compatible connector profile, and no pending connector-refresh risk.; Transport compliance failed or did not complete successfully.
Confidence: high (77.5)
Evidence provenance
Winner: live_validation
Supporting sources: live_validation, history, server_card
Disagreements: none
  • initializeOK
  • tools_listOK
  • transport_compliance_probeWarning
Write-action publishing
Publishing blocked
action_safety_probe reported an unconfirmed high-risk, destructive, or exec-capable tool. Risky write actions are present without a clear auth boundary and confirmation signal. Active alert(s) affecting production readiness: Server card describes a different server: card says "Tuteliq Docs MCP", live says "Tuteliq".
Confidence: high (77.5)
Evidence provenance
Winner: live_validation
Supporting sources: live_validation, history
Disagreements: none
  • action_safety_probeError
Snapshot churn risk
Low
No material tool-surface churn detected in the latest comparison.
Confidence: high (77.5)
Evidence provenance
Winner: history
Supporting sources: history, live_validation
Disagreements: none
  • tool_snapshot_probeOK
  • connector_replay_probeOK
Client compatibility gate details
ChatGPT custom connector
Not client-compatible
OpenAI connectors expect OAuth for remote server auth.; Dynamic client registration materially improves connector setup.; OAuth interoperability should be strong.; The tool surface is not limited to search/fetch-style read tools.; This client profile expects a read/search-only tool surface, but write, delete, or exec-capable tools are present.; OAuth is not configured, so this client cannot authenticate without additional setup.
Remediation checklist
  • Add OAuth-based authentication for remote connector auth.
  • Support dynamic client registration (DCR) to simplify connector setup.
  • Improve OAuth interoperability -- see the OAuth Interop score breakdown.
  • Limit the exposed surface to search/fetch-style read tools.
  • Remove or isolate write, delete, and exec-capable tools before using this read/search-only client profile.
  • Configure OAuth for authenticated remote MCP access.
Claude remote MCP
Not client-compatible
The tool surface is not limited to search/fetch-style read tools.; This client profile expects a read/search-only tool surface, but write, delete, or exec-capable tools are present.; OAuth is not configured, so this client cannot authenticate without additional setup.; Not yet safe for company-knowledge use: requires a search/fetch-only surface with no export, bulk, mutating, or high-blast-radius exposure.; Not yet safe for the Messages API remote MCP path: requires OAuth, a compatible connector profile, and no pending connector-refresh risk.; Transport compliance failed or did not complete successfully.
Remediation checklist
  • Limit the exposed surface to search/fetch-style read tools.
  • Remove or isolate write, delete, and exec-capable tools before using this read/search-only client profile.
  • Configure OAuth for authenticated remote MCP access.
  • Remove export, bulk, mutating, and high-blast-radius exposure before certifying company-knowledge use.
  • Satisfy OAuth, compatibility, and connector-refresh requirements before using the Messages API remote MCP path.
  • Resolve transport compliance issues before wider client rollout.
Write-safe publishing
Blocked
Risky write or non-read tools are exposed without a clear auth boundary.; Risky or non-read tools lack confirmation/dry-run controls: submit_feedback.; Production readiness is blocked by an active alert: Server card describes a different server: card says "Tuteliq Docs MCP", live says "Tuteliq".
Remediation checklist
  • Add a clearer auth boundary around risky write actions.
  • Add confirmation or dry-run semantics for: submit_feedback.
  • Resolve the active alert: Server card describes a different server: card says "Tuteliq Docs MCP", live says "Tuteliq".
Verdict traces
Production verdict
Needs remediation
Degraded from Safe for evaluation: 1 open high/critical-severity alert(s) are active, including at least one that blocks even evaluation-level trust.
Confidence: high (77.5)
Winning source: live_validation
Triggering alerts
  • server_card_schema_drifted • critical • Server card describes a different server: card says "Tuteliq Docs MCP", live says "Tuteliq"
Client verdict trace table
VerdictStatusChecksWinning sourceConflicts
openai_connectors Not client-compatible initialize, tools_list, transport_compliance_probe, step_up_auth_probe, connector_replay_probe, request_association_probe live_validation none
claude_desktop Not client-compatible initialize, tools_list, transport_compliance_probe live_validation none
unsafe_for_write_actions Publishing blocked action_safety_probe live_validation none
snapshot_churn_risk Low tool_snapshot_probe, connector_replay_probe history none
Publishability policy profiles
ChatGPT custom connector compatibility
Compatible with review
OpenAI connectors expect OAuth for remote server auth.; Dynamic client registration materially improves connector setup.; OAuth interoperability should be strong.; The tool surface is not limited to search/fetch-style read tools.; This client profile expects a read/search-only tool surface, but write, delete, or exec-capable tools are present.; OAuth is not configured, so this client cannot authenticate without additional setup. Compatibility is not a production approval; company knowledge and Messages API gates remain separate.
  • Search Fetch Only: No
  • Write Actions Present: Yes
  • Oauth Configured: No
  • Admin Refresh Required: No
  • Safe For Company Knowledge: No
  • Safe For Messages Api Remote Mcp: No
Claude remote MCP compatibility
Connector-compatible
The tool surface is not limited to search/fetch-style read tools.; This client profile expects a read/search-only tool surface, but write, delete, or exec-capable tools are present.; OAuth is not configured, so this client cannot authenticate without additional setup.; Not yet safe for company-knowledge use: requires a search/fetch-only surface with no export, bulk, mutating, or high-blast-radius exposure.; Not yet safe for the Messages API remote MCP path: requires OAuth, a compatible connector profile, and no pending connector-refresh risk. Compatibility is not a production approval; company knowledge and Messages API gates remain separate.
  • Search Fetch Only: No
  • Write Actions Present: Yes
  • Oauth Configured: No
  • Admin Refresh Required: No
  • Safe For Company Knowledge: No
  • Safe For Messages Api Remote Mcp: No
Compatibility fixtures
ChatGPT custom connector fixture
Degraded
OpenAI connectors expect OAuth for remote server auth.; Dynamic client registration materially improves connector setup.; OAuth interoperability should be strong.
  • remote_http_endpoint: Passes
  • oauth_discovery: Degraded
  • frozen_tool_snapshot_refresh: Passes
  • request_association: Passes
Anthropic remote MCP fixture
Degraded
Remote MCP transport and discovery assumptions are satisfied.
  • remote_transport: Passes
  • tool_discovery: Passes
  • auth_connect: Passes
  • safe_write_review: Degraded
Recommended for
Claude Desktop
Claude Desktop is marked compatible with score 100.
Smithery
Smithery is marked compatible with score 80.
Generic Streamable HTTP
Generic Streamable HTTP is marked compatible with score 100.

Evidence

Current trust snapshot
Snapshot ID
trustsnap_42e4662a0e6cc372
Use this ID to compare server page, report, policy, MCP, homepage, ranking, and shortlist surfaces.
Snapshot generated
Aug 12, 2026 04:00:30 PM UTC
All page, report, policy, and MCP surfaces use this same server-detail snapshot shape.
Last validated
Aug 12, 2026 01:19:33 PM UTC
Age: 2.68h • evidence age tier: Verified in last 24h • display score: 61.46

Canonical machine links

Evidence confidence
Confidence score
77.5
Based on 2 recent validations, 15 captured checks, and validation age of 2.7 hours.
Live checks captured
15
More direct checks increase trust in the current verdict.
Validation age
2.7h
Lower age means fresher evidence.
Latest validation evidence
Latest summary
Healthy
Validation profile
remote_mcp
Started
Aug 12, 2026 01:19:31 PM UTC
Latency
2330.0 ms

Failures

  • oauth_authorization_server no authorization server
  • oauth_protected_resource Client error '404 Not Found' for url 'https://docs.tuteliq.ai/.well-known/oauth-protected-resource' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404
  • openid_configuration no authorization server
  • schema_divergence_probe Check completed

Checks

CheckStatusLatencyEvidence
action_safety_probe Error n/a 1 high-risk, 1 egress-capable, 1 declared non-read-only, non-read capabilities: write tool(s); no clear auth boundary; safeguards=1; confirmation=none.
advanced_capabilities_probe Warning n/a Only 3 capability signal(s): resource links, resources, roots.
connector_publishability_probe Warning n/a Publishability blockers: step up auth, action safety.
connector_replay_probe OK n/a Backward compatible with no breaking tool-surface changes.
determinism_probe OK 160.2 ms Check completed
initialize OK 201.8 ms Protocol 2025-03-26
interactive_flow_probe Missing n/a Check completed
oauth_authorization_server Missing n/a no authorization server
oauth_protected_resource Error 115.1 ms Client error '404 Not Found' for url 'https://docs.tuteliq.ai/.well-known/oauth-protected-resource' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404
official_registry_probe Missing n/a Check completed
openid_configuration Missing n/a no authorization server
probe_noise_resilience OK 520.5 ms Fetched https://docs.tuteliq.ai/robots.txt
prompt_get Missing n/a not advertised
prompts_list Missing 155.0 ms not supported
protocol_version_probe Warning n/a Claims 2025-03-26; 2 release(s) behind 2025-11-25.
provenance_divergence_probe Not_Assessed n/a Check completed
request_association_probe Warning n/a Advertised=roots; observed=none.
resource_read OK 139.2 ms 1 resource content item(s) returned
resources_list OK 160.6 ms 1 resource item(s) exposed
schema_divergence_probe Error n/a Check completed
server_card OK 201.6 ms authentication, capabilities, description, name
session_resume_probe Warning n/a no session id
step_up_auth_probe Missing n/a No OAuth or incremental-scope signals detected.
tool_snapshot_probe OK n/a Check completed
tools_list OK 220.9 ms 3 tool(s) exposed
transport_compliance_probe Warning 135.7 ms Issues: missing session id, missing protocol header (bad protocol=400).
utility_coverage_probe Missing 60.3 ms No completions evidence; no pagination evidence; tasks missing.
Known versions
  • No versions recorded.
Public server reputation
Validation success 7d
1.0
Validation success 30d
1.0
Mean time to recover
n/a
Breaking diffs 30d
0
Registry drift frequency 30d
0
Snapshot changes 30d
0
Benchmark tasks
Benchmark taskStatusEvidence
Discover tools Passes
  • initializeOK
  • tools_listOK
Read-only fetch flow Passes
  • resource_readOK
  • read_only_tool_surfaceOK
OAuth-required connect Degraded
  • oauth_protected_resourceError
  • step_up_auth_probeMissing
Safe write flow with confirmation Likely to fail
  • action_safety_probeError
Utility coverage
Probe status
Missing
Completions
not detected
Completion probe target: { "type": "resource", "uri": "mintlify://skills/tuteliqab" }
Pagination
not detected
No nextCursor evidence.
Tasks
Missing
Advertised: no
Tool snapshot diff & changelog
Snapshot changed
no
Added tools
none
Removed tools
none
Required-argument changes
ToolAdded required argsRemoved required args
No required-argument changes detected.
Output-schema drift
ToolPrevious propertiesLatest properties
No output-schema drift detected.
Validation diff
Score delta
0
Summary changed
no
Tool delta
0
Prompt delta
0
Auth mode changed
no
Write surface expanded
no
Protocol regressed
no
Registry drift changed
no

Regressed checks: none

Improved checks: none

Newly assessed dimensions: none

No longer assessed dimensions: none

ComponentPreviousLatestDelta
No component deltas between the latest two runs.
Registry & provenance divergence
Probe status
Not_Assessed
Direct official match
no
Drift fields
none
Cross-registry alias disagreements
none
FieldRegistryLive server card
Titlen/aTuteliq Docs MCP
Versionn/a1.0.0
Homepagen/an/a
Active alerts
  • Server card describes a different server: card says "Tuteliq Docs MCP", live says "Tuteliq" (critical)
    Severity: critical. The published server card's serverInfo.name does not match the live server.
Aliases & registry graph
IdentifierSourceCanonicalIdentity evidenceScore
github-tuteliq/claude-plugin github_topic_registry yes canonical 61.5
Alias consolidation

Strong alias identity requires matching remote URL, server-card URL, repository slug, or explicit registry cross-reference; shared provider namespace alone is not identity.

Canonical identifier
github-tuteliq/claude-plugin
Duplicate aliases
0
Registry sources
github_topic_registry
Source disagreements
FieldWhat differsObserved values
No source disagreements detected.

Fix it

Why this score?
Access & Protocol
24/44
Connectivity, auth, and transport expectations for common clients.
Interface Quality
33/56
How well the tool/resource interface communicates and behaves under automation.
Security Posture
22/36
How safely the exposed tool surface handles destructive actions, egress, execution, secrets, and risky inputs.
Reliability & Trust
21/24
Operational stability, consistency, and trustworthiness over time.
Discovery & Governance
13/28
How well the server is documented, listed, and governed in public registries.
Adoption & Market
5/8
Adoption clues and public evidence that the server is intended for external use.
Algorithmic score breakdown
Auth Operability
2/4
Measures whether auth discovery and protected access behave predictably for clients.
Error Contract Quality
1/4
Grades machine-readable error structure, status alignment, and remediation hints.
Rate-Limit Semantics
2/4
Checks whether quota/throttle responses are deterministic and automation-friendly.
Schema Completeness
3/4
Completeness of tool descriptions, parameter docs, examples, and schema shape.
Backward Compatibility
4/4
Stability score across tool schema/name drift relative to prior validations.
SLO Health
3/4
Availability, latency, and burst-failure profile across recent validation history.
Security Hygiene
3/4
HTTPS posture, endpoint hygiene, and response-surface hardening checks.
Task Success
4/4
Can an agent reliably initialize, enumerate tools, and execute core MCP flows?
Trust Confidence
2/4
Confidence-adjusted reliability score that penalizes low evidence volume.
Abuse/Noise Resilience
4/4
How well the server preserves core behavior in the presence of noisy traffic patterns.
Prompt Contract
0/4
Quality of prompt metadata, argument shape, and prompt discoverability for clients.
Resource Contract
4/4
How completely resources and resource templates describe URIs, types, and usage shape.
Discovery Metadata
2/4
Homepage, docs, icon, repository, support, and license coverage for directory consumers.
Registry Consistency
3/4
Agreement between stored registry metadata, live server-card data, and current validation output.
Installability
4/4
How cleanly a real client can connect, initialize, enumerate tools, and proceed through auth.
Session Semantics
4/4
Determinism and state behavior across repeated MCP calls, including sticky-session surprises.
Tool Surface Design
3/4
Naming clarity, schema ergonomics, and parameter complexity across the tool surface.
Result Shape Stability
3/4
Stability of declared output schemas across validations, with penalties for drift or missing shapes.
OAuth Interop
0/4
Depth and client compatibility of OAuth/OIDC metadata beyond the minimal protected-resource check.
Recovery Semantics
0/4
Whether failures include actionable machine-readable next steps such as retry or upgrade guidance.
Maintenance Signal
2/4
Versioning, update recency, and historical validation cadence that indicate active stewardship.
Adoption Signal
2/4
Directory presence and distribution clues that suggest the server is intended for external use.
Freshness Confidence
4/4
Confidence that recent validations are current enough and dense enough to trust operationally.
Transport Fidelity
4/4
Whether declared transport metadata matches the observed endpoint behavior and response formats.
Spec Recency
2/4
How close the server’s claimed MCP protocol version is to the latest known public revision.
Session Resume
3/4
Whether Streamable HTTP session identifiers and resumed requests behave cleanly for real clients.
Step-Up Auth
0/4
Whether OAuth metadata and WWW-Authenticate challenges support granular, incremental consent instead of broad upfront scopes.
Transport Compliance
2/4
Checks session headers, protocol-version enforcement, session teardown, and expired-session behavior.
Utility Coverage
0/4
Signals support for completions, pagination, and task-oriented utility surfaces that larger clients increasingly expect.
Advanced Capability Coverage
1/4
Coverage of newer MCP surfaces like roots, sampling, elicitation, structured output, and related metadata.
Connector Publishability
3/4
How ready the server looks for client catalogs and managed connector programs.
Tool Snapshot Churn
4/4
Stability of the tool surface across recent validations, including add/remove and output-shape drift.
Connector Replay
4/4
Whether a previously published frozen connector snapshot would remain backward compatible after the latest tool refresh.
Request Association
2/4
Whether roots, sampling, and elicitation appear tied to active client requests instead of arriving unsolicited on idle sessions.
Interactive Flow Safety
0/4
Whether prompts and docs steer users toward safe auth flows instead of pasting secrets directly.
Action Safety
1/4
Risk-weighted view of destructive, exec, egress, and confirmation semantics across the tool surface.
Official Registry Presence
3/4
Whether the server appears directly or indirectly in the official MCP registry.
Safety Transparency
3/4
Clarity of docs, auth disclosure, support links, and other trust signals visible to integrators.
Tool Capability Clarity
4/4
How clearly the tool surface communicates whether each action reads, writes, deletes, executes, or exports data.
Destructive Operation Safety
3/4
Penalizes delete/revoke/destroy style tools unless auth and safeguards reduce blast radius.
Egress / SSRF Resilience
2/4
Assesses arbitrary URL fetch, crawl, webhook, and remote-request exposure on the tool surface.
Execution / Sandbox Safety
4/4
Evaluates shell, code, script, and command-execution exposure and whether that surface appears contained.
Data Exfiltration Resilience
3/4
Assesses export, dump, backup, and bulk-read behavior against the surrounding auth and safeguard signals.
Least Privilege Scope
1/4
Rewards scoped auth metadata and penalizes broad or missing scopes around privileged tools.
Secret Handling Hygiene
3/4
Assesses secret-bearing tools, token leakage risk, and whether the public surface avoids obvious secret exposure.
Supply Chain Signal
0/4
Public metadata signal for repository, changelog, license, versioning, and recency that supports supply-chain trust.
Input Sanitization Safety
3/4
Penalizes risky freeform string inputs when schemas do not constrain URLs, code, paths, queries, or templates.
Tool Namespace Clarity
4/4
Measures naming uniqueness and ambiguity across the tool namespace to reduce collision and confusion risk.

1 component(s) not assessed for this run: Provenance Divergence

Experimental candidate components
Personal Data Exposure
8.5
Experimental candidate, weight 0. Export and bulk-access evidence only; no impact on totals, verdicts, rankings, or gates.
Actionable remediation
SeverityRemediationWhy it mattersRecommended action
Critical Respond to server card describes a different server: card says "tuteliq docs mcp", live says "tuteliq" Severity: critical. The published server card's serverInfo.name does not match the live server.
High Add confirmation and dry-run semantics for risky actions High-risk write, delete, exec, or egress tools should communicate safeguards clearly. Add an explicit confirm/dry-run parameter or two-step confirmation flow to write, delete, exec, and egress-capable tools before they can make destructive changes.
Playbook
  • For each high-risk tool (delete, exec, or network-egress capable), add a `confirm`/`dry_run` parameter or a two-step confirmation flow.
  • Document the safeguard in the tool's description so clients and agents know confirmation is required before execution.
  • Revalidate and confirm `action_safety_probe` reports the safeguard as detected.
High Align session and protocol behavior with Streamable HTTP expectations Clients increasingly rely on MCP-Protocol-Version, session teardown, and expired-session semantics. Align MCP-Protocol-Version, MCP-Session-Id, DELETE teardown, and expired-session handling with the transport spec.
Playbook
  • Return `Mcp-Session-Id` and `Mcp-Protocol-Version` headers consistently on streamable HTTP responses.
  • Honor `DELETE` session teardown and return `404` when a deleted session is reused.
  • Reject invalid protocol-version headers with `400 Bad Request`.
High Associate roots, sampling, and elicitation with active client requests Modern MCP guidance expects roots, sampling, and elicitation traffic to be tied to an active client request instead of arriving unsolicited on idle sessions. Only send roots/list, sampling/createMessage, or elicitation/create requests while handling an active client-initiated request, never on idle sessions.
Playbook
  • Only send `roots/list`, `sampling/createMessage`, or `elicitation/create` requests while handling an active client-initiated request.
  • Avoid emitting these requests on idle or newly-initialized sessions with no pending client request.
  • Revalidate and confirm `request_association_probe` no longer returns `missing` or `warning`.
High Expose /.well-known/oauth-protected-resource Without a protected-resource document, OAuth clients cannot discover auth requirements reliably. Serve /.well-known/oauth-protected-resource and point it at your authorization server metadata.
Playbook
  • Serve `/.well-known/oauth-protected-resource` from the same host as the MCP endpoint.
  • Point it at the authorization server metadata URL.
  • Confirm clients receive consistent auth hints before tool execution.
High Publish OAuth authorization-server metadata Clients need authorization-server metadata to discover issuer, endpoints, and DCR support. Publish /.well-known/oauth-authorization-server from your issuer and include registration_endpoint when supported.
Playbook
  • Publish `/.well-known/oauth-authorization-server` from the issuer.
  • Add `registration_endpoint` if DCR is supported.
  • Verify issuer, authorization, token, and jwks metadata are all reachable.
High Sync the published server card's tool schemas with the live tool surface The server card and live tools/list disagree on parameter names, required sets, or types -- clients that trust the published card will construct invalid calls. Regenerate the published server card from the live tool schemas (or vice versa) so the two agree -- see the schema divergence detail on this run for exactly which fields disagree.
Playbook
  • Diff the published `/.well-known/mcp/server-card.json` tool schemas against a live `tools/list` response.
  • Fix parameter name mismatches, required-set mismatches, and type mismatches per tool.
  • Regenerate or hand-sync the server card whenever the live tool schemas change -- treat drift as a release blocker, not a documentation nit.
Medium Adopt a current MCP protocol revision Older protocol revisions reduce compatibility with newer clients and registry programs. Advertise a current MCP protocol revision (2025-06-18 or later) in both the initialize response and the MCP-Protocol-Version header.
Playbook
  • Update the server's advertised protocol version to a current MCP revision (2025-06-18 or later).
  • Return the negotiated version consistently in both the `initialize` response and the `MCP-Protocol-Version` header.
  • Revalidate and confirm `protocol_version_probe` reports `ok`.
Medium Close connector-publishing gaps Connector catalogs care about protocol recency, session behavior, auth clarity, and tool-surface stability.
Medium Document minimal scopes and return cleaner auth challenges Modern clients expect granular scopes and step-up auth signals such as WWW-Authenticate scope hints. Return granular scopes and WWW-Authenticate challenge hints instead of forcing overly broad auth upfront.
Playbook
  • Advertise the narrowest viable scopes in OAuth metadata.
  • Return `WWW-Authenticate` challenges with scope or insufficient-scope hints when additional consent is needed.
  • Revalidate with both public discovery and auth-required flows.
Medium Publish OpenID configuration OIDC metadata improves token validation and client compatibility. Expose /.well-known/openid-configuration with issuer, jwks_uri, and supported grants.
Playbook
  • Serve `/.well-known/openid-configuration` with `issuer`, `jwks_uri`, `authorization_endpoint`, and `token_endpoint`.
  • List supported grant types in `grant_types_supported` and scopes in `scopes_supported`.
  • Revalidate and confirm the `openid_configuration` check returns `ok`.
Medium Support resumable HTTP sessions cleanly Modern MCP clients increasingly expect resumable session behavior on streamable HTTP transports. Persist session state keyed by Mcp-Session-Id and honor Last-Event-ID on GET reconnects so clients can resume a dropped Streamable HTTP session.
Playbook
  • Persist session state keyed by `Mcp-Session-Id` so a client can reconnect after a dropped connection.
  • Honor `Last-Event-ID` on GET reconnects to replay missed SSE events instead of erroring.
  • Revalidate and confirm `session_resume_probe` no longer returns `warning`.
Low Expose modern utility surfaces like completions, pagination, or tasks Utility coverage improves interoperability with larger clients and long-lived agent workflows. Expose completions, pagination, and task metadata where supported so larger clients can plan and resume work safely.
Playbook
  • Advertise `completions`, pagination cursors, and `tasks` only when they are actually supported.
  • Return `nextCursor` on large list operations when pagination is available.
  • Document task support and whether it requires step-up auth.
Low Publish newer MCP capability signals Roots, sampling, elicitation, structured outputs, and related metadata improve client understanding and ranking. Advertise only the advanced capabilities (roots, sampling, elicitation) you have actually implemented end to end in the initialize capabilities object.
Playbook
  • Add the capabilities you actually support (`roots`, `sampling`, `elicitation`) to the `capabilities` object returned from `initialize`.
  • Only advertise a capability once the corresponding request/response flow is implemented end to end.
  • Revalidate and confirm `advanced_capabilities_probe` reflects the updated capability set.
Low Publish or reconcile the server in the official MCP registry Official registry presence improves discovery confidence and cross-source consistency.
Point loss breakdown
ComponentCurrentPoints missing
Utility Coverage 0/4 -4.0
Step Up Auth 0/4 -4.0
Recovery Semantics 0/4 -4.0
Prompt Contract 0/4 -4.0
OAUTH Interop 0/4 -4.0
Interactive Flow Safety 0/4 -4.0
Dependency Supply Chain Signal 0/4 -4.0
Least Privilege Scope 1/4 -3.0
Error Contract 1/4 -3.0
Advanced Capability Coverage 1/4 -3.0
Action Safety 1/4 -3.0
Trust Confidence 2/4 -2.0
Compatibility profiles
OpenAI Connectors
66.7
partial (6 of 9 requirements met)
OpenAI connectors expect OAuth for remote server auth.; Dynamic client registration materially improves connector setup.; OAuth interoperability should be strong.
Connector URL: https://docs.tuteliq.ai/mcp
# No OAuth metadata detected.
# Server: github-tuteliq/claude-plugin
Claude Desktop
100.0
compatible (6 of 6 requirements met)
No major blockers detected.
{
  "mcpServers": {
    "claude-plugin": {
      "command": "npx",
      "args": ["mcp-remote", "https://docs.tuteliq.ai/mcp"]
    }
  }
}
Smithery
80.0
compatible (4 of 5 requirements met)
Machine-readable failure semantics should be present.
smithery mcp add "https://docs.tuteliq.ai/mcp"
Generic Streamable HTTP
100.0
compatible (6 of 6 requirements met)
No major blockers detected.
curl -sS https://docs.tuteliq.ai/mcp -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"mcp-verify","version":"0.1.0"}}}'

Governance

MCP TrustOps

TrustOps turns this report into operational controls: validation targets and SLAs, authenticated validation, semantic benchmarks, policy exports, alert subscriptions, badges, cost/compliance metadata, and runtime routing. Fresh trusted index decisions stay separate from long-tail inventory so stale scores do not masquerade as current evidence.

Evidence age tier
Verified in last 24h
Policy evidence-age limit (a runtime constraint, distinct from the public 24h freshness window and from a plan's validation target/SLA): 168.0h • confidence-weighted score (display score discounted for evidence age and confidence -- an internal TrustOps input, not the public score): 47.6 • evidence too old to display:
Policy exports
Formats: json, rego, yaml, github_action, gateway_config, client_report
Runtime routing
/v1/decide
Returns allowed tools, blocked tools, approval requirement, and reason.
Hosted runtime
Deploy trusted servers from GitHub with secrets, egress controls, releases, rollback, and audit events.
Authenticated validation
Premium publisher feature: paid authenticated runs verify scopes, write-action safeguards, and authorized tool execution.
Active trust badges
none
Semantic benchmarks
available
Templates cover GitHub, database, healthcare, web search, and CRM least-privilege jobs.
Supply chain
metadata signal
Deep scan checks are marked separately from public metadata signals.
Compliance metadata
Terms, privacy, SOC 2, HIPAA, GDPR, retention, deletion, and audit-log fields are tracked as enterprise metadata.
Alert subscription types
Status changes Score drops or recovers Evidence-age policy breach Validation schema drift OAuth or auth behavior changes Tool surface changes New or changed write tool Supply-chain signal changes Legal or compliance metadata changes
MCP Runtime hosting

Verify Hosted MCP turns a trusted server report into a managed remote MCP endpoint with GitHub deployment provenance, sandbox policy, encrypted secrets, release history, rollback, and audit/usage events.

Activation readiness
Trusted hosted runtimes require fresh validation, a passing server state, a remote endpoint, and a minimum score.
Minimum tier
TrustOps
Publisher claim plus paid TrustOps tier are required before secrets or releases can be created.
Hosted endpoint
/hosted/{namespace}/{name}/mcp
The endpoint enforces egress allowlists and records audit/usage events.
Blockers
score_below_hosting_threshold blocked_by_active_alerts blocked_by_production_readiness unsafe_write_action_surface
DeploymentStatusEndpointRelease
No hosted runtime deployments yet.
Authenticated validation sessions

Public validation is free. Authenticated validation is paid and proves scoped behavior, write-action safeguards, and authenticated tool execution.

Latest profile
remote_mcp
Authenticated session used
Public score isolation
Preview endpoint
/v1/verify
CI preview endpoint
/v1/ci/preview
Install snippets
Openai Connectors
Connector URL: https://docs.tuteliq.ai/mcp
# No OAuth metadata detected.
# Server: github-tuteliq/claude-plugin
Claude Desktop
{
  "mcpServers": {
    "claude-plugin": {
      "command": "npx",
      "args": ["mcp-remote", "https://docs.tuteliq.ai/mcp"]
    }
  }
}
Smithery
smithery mcp add "https://docs.tuteliq.ai/mcp"
Generic Http
curl -sS https://docs.tuteliq.ai/mcp -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"mcp-verify","version":"0.1.0"}}}'
Agent access & tool surface
Live server tools
search_tuteliq query_docs_filesystem_tuteliq submit_feedback
Observed from the latest live validation against https://docs.tuteliq.ai/mcp. This is the target server surface, not Verify's own inspection tools.
Live capability counts
3 tools • 0 prompts • 1 resources
Counts come from the latest tools/list, prompts/list, and resources/list checks.
Inspect with Verify
search fetch search_servers recommend_servers get_server_report compare_servers
Use Verify itself to search, recommend, compare, and fetch the full report for github-tuteliq/claude-plugin.
Direct machine links

History

Validation history
7 day score delta
n/a
30 day score delta
n/a
Recent healthy ratio
100%
Freshness
2.7h
TimestampStatusScoreLatencyTools
Aug 12, 2026 01:19:33 PM UTC Healthy 61.5 2330.0 ms 3
Aug 12, 2026 01:19:07 AM UTC Healthy 61.5 2519.8 ms 3
Aug 11, 2026 01:18:56 PM UTC Healthy 60.9 2311.9 ms not fetched
Aug 11, 2026 01:18:35 AM UTC Healthy 60.4 2608.6 ms not fetched
Aug 10, 2026 12:57:38 PM UTC Healthy 57.3 2234.5 ms not fetched
Validation timeline
ValidatedSummaryScoreProtocolAuth modeToolsHigh-risk toolsChanges
Aug 12, 2026 01:19:33 PM UTC Healthy 61.5 2025-03-26 public 3 1 none
Aug 12, 2026 01:19:07 AM UTC Healthy 61.5 2025-03-26 public 3 1 none
Aug 11, 2026 01:18:56 PM UTC Healthy n/a unknown unknown not fetched 0 none
Aug 11, 2026 01:18:35 AM UTC Healthy n/a unknown unknown not fetched 0 none
Aug 10, 2026 12:57:38 PM UTC Healthy n/a unknown unknown not fetched 0 none
Recent validation runs
Recent validation runs for this MCP server
StartedStatusSummaryLatencyChecks
Aug 12, 2026 01:19:31 PM UTC Completed Healthy 2330.0 ms action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, schema_divergence_probe, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe
Aug 12, 2026 01:19:05 AM UTC Completed Healthy 2519.8 ms action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, schema_divergence_probe, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe
Aug 11, 2026 01:18:53 PM UTC Completed Healthy 2311.9 ms not fetched (not counted in confidence)
Aug 11, 2026 01:18:32 AM UTC Completed Healthy 2608.6 ms not fetched (not counted in confidence)
Aug 10, 2026 12:57:35 PM UTC Completed Healthy 2234.5 ms not fetched (not counted in confidence)
Incident & change feed
TimestampEventDetails
Aug 12, 2026 01:19:33 PM UTC Latest validation: healthy Score 61.5 with status healthy.

Technical details

Raw evidence view
Show raw JSON evidence
{
  "checks": {
    "action_safety_probe": {
      "details": {
        "auth_present": false,
        "confirmation_signals": [],
        "reason": null,
        "safeguard_count": 1,
        "summary": {
          "annotation_conflict_tools": 1,
          "bulk_access_tools": 0,
          "capability_distribution": {
            "filesystem": 1,
            "network": 1,
            "read": 2,
            "write": 1
          },
          "declared_non_read_only_tools": 1,
          "destructive_tools": 0,
          "egress_tools": 1,
          "exec_tools": 0,
          "has_mutating_capability": true,
          "has_non_read_capability": true,
          "high_risk_tools": 1,
          "risk_distribution": {
            "critical": 0,
            "high": 1,
            "low": 2,
            "medium": 0
          },
          "secret_tools": 0,
          "tool_count": 3
        }
      },
      "latency_ms": null,
      "status": "error"
    },
    "advanced_capabilities_probe": {
      "details": {
        "capabilities": {
          "completions": false,
          "elicitation": false,
          "prompts": false,
          "resource_links": true,
          "resources": true,
          "roots": true,
          "sampling": false,
          "structured_outputs": false
        },
        "enabled": [
          "resource_links",
          "resources",
          "roots"
        ],
        "enabled_count": 3,
        "initialize_capability_keys": [
          "resources",
          "tools"
        ]
      },
      "latency_ms": null,
      "status": "warning"
    },
    "connector_publishability_probe": {
      "details": {
        "blockers": [
          "step_up_auth",
          "action_safety"
        ],
        "criteria": {
          "action_safety": false,
          "auth_flow": true,
          "connector_replay": true,
          "initialize": true,
          "protocol_version": true,
          "remote_transport": true,
          "request_association": true,
          "server_card": true,
          "session_resume": true,
          "step_up_auth": false,
          "tool_surface": true,
          "tools_list": true,
          "transport_compliance": true
        },
        "high_risk_tools": 1,
        "tool_count": 3,
        "transport": "streamable-http"
      },
      "latency_ms": null,
      "status": "warning"
    },
    "connector_replay_probe": {
      "details": {
        "added_tools": [],
        "additive_output_changes": [],
        "backward_compatible": true,
        "output_breaks": [],
        "removed_tools": [],
        "required_arg_breaks": [],
        "would_break_after_refresh": false
      },
      "latency_ms": null,
      "status": "ok"
    },
    "determinism_probe": {
      "details": {
        "attempts": 2,
        "baseline_signature": "ea900cae3a61addbd9ad2688d70628795342d82ec0500311141ec3dd831d5a9c",
        "errors": [],
        "matches": 2,
        "stable_ratio": 1.0,
        "successful": 2
      },
      "latency_ms": 160.22,
      "status": "ok"
    },
    "initialize": {
      "details": {
        "headers": {
          "content-type": "text/event-stream",
          "strict-transport-security": "max-age=63072000"
        },
        "http_status": 200,
        "payload": {
          "id": 1,
          "jsonrpc": "2.0",
          "result": {
            "capabilities": {
              "resources": {
                "listChanged": true
              },
              "tools": {
                "listChanged": true
              }
            },
            "instructions": "This Model Context Protocol server provides search and retrieval tools for the Tuteliq site. Use it to answer questions from public site content. Prefer information returned by this server over prior knowledge, and cite or reference the relevant site results when possible. Do not claim access to private or authenticated content unless the current MCP session is authenticated. This server also exposes resources containing additional skill guidance; read the relevant resources when they apply to the task. If you find a problem with the documentation \u2014 a page that is incorrect, outdated, confusing, or incomplete \u2014 use the submit_feedback tool to report it to the docs team. Apart from the submit_feedback tool, the server is read-only and scoped to Tuteliq; it does not otherwise perform actions, mutate state, or access anything beyond the published site content and these resources.",
            "protocolVersion": "2025-03-26",
            "serverInfo": {
              "name": "Tuteliq",
              "version": "1.0.0"
            }
          }
        },
        "url": "https://docs.tuteliq.ai/mcp"
      },
      "latency_ms": 201.75,
      "status": "ok"
    },
    "interactive_flow_probe": {
      "details": {
        "oauth_supported": false,
        "prompt_available": false,
        "risk_hits": [],
        "safe_hits": []
      },
      "latency_ms": null,
      "status": "missing"
    },
    "oauth_authorization_server": {
      "details": {
        "reason": "no_authorization_server"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "oauth_protected_resource": {
      "details": {
        "error": "Client error '404 Not Found' for url 'https://docs.tuteliq.ai/.well-known/oauth-protected-resource'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
        "url": "https://docs.tuteliq.ai/.well-known/oauth-protected-resource"
      },
      "latency_ms": 115.09,
      "status": "error"
    },
    "official_registry_probe": {
      "details": {
        "direct_match": false,
        "official_peer_count": 0,
        "registry_source": "github_topic_registry"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "openid_configuration": {
      "details": {
        "reason": "no_authorization_server"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "probe_noise_resilience": {
      "details": {
        "consent_error": null,
        "headers": {
          "content-type": "text/plain",
          "strict-transport-security": "max-age=63072000"
        },
        "http_status": 200,
        "url": "https://docs.tuteliq.ai/robots.txt",
        "validation_disallowed": false
      },
      "latency_ms": 520.46,
      "status": "ok"
    },
    "prompt_get": {
      "details": {
        "reason": "not_advertised"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "prompts_list": {
      "details": {
        "headers": {
          "content-type": "text/event-stream",
          "strict-transport-security": "max-age=63072000"
        },
        "http_status": 200,
        "payload": {
          "error": {
            "code": -32601,
            "message": "Method not found"
          },
          "id": 3,
          "jsonrpc": "2.0"
        },
        "reason": "not_supported",
        "url": "https://docs.tuteliq.ai/mcp"
      },
      "latency_ms": 154.97,
      "status": "missing"
    },
    "protocol_version_probe": {
      "details": {
        "claimed_version": "2025-03-26",
        "lag_days": 244,
        "latest_known_version": "2025-11-25",
        "releases_behind": 2,
        "validator_protocol_version": "2025-03-26"
      },
      "latency_ms": null,
      "status": "warning"
    },
    "provenance_divergence_probe": {
      "details": {
        "comparable_field_count": 0,
        "compared_fields": [
          "title",
          "version",
          "homepage",
          "repository"
        ],
        "direct_official_match": false,
        "drift_fields": [],
        "metadata_document_count": 2,
        "readable_sources": [
          "server_card"
        ],
        "registry_homepage": null,
        "registry_repository": null,
        "registry_title": null,
        "registry_version": null,
        "server_card_homepage": null,
        "server_card_repository": null,
        "server_card_title": "Tuteliq Docs MCP",
        "server_card_version": "1.0.0"
      },
      "latency_ms": null,
      "status": "not_assessed"
    },
    "request_association_probe": {
      "details": {
        "advertised_capabilities": [
          "roots"
        ],
        "protocol_version": "2025-03-26",
        "reason": "no_session_id_for_idle_observation"
      },
      "latency_ms": null,
      "status": "warning"
    },
    "resource_read": {
      "details": {
        "headers": {
          "content-type": "text/event-stream",
          "strict-transport-security": "max-age=63072000"
        },
        "http_status": 200,
        "payload": {
          "id": 6,
          "jsonrpc": "2.0",
          "result": {
            "contents": [
              {
                "mimeType": "text/markdown",
                "text": "---\nname: Tuteliqab\ndescription: Use when building child safety features, content moderation systems, or age-verification flows. Agents should reach for this skill when implementing KOSA compliance, detecting grooming/bullying/fraud, analyzing voice/image/video for safety, or verifying user age and identity.\nmetadata:\n    mintlify-proj: tuteliqab\n    version: \"1.0\"\n---\n\n# Tuteliq Skill Reference\n\n## Product summary\n\nTuteliq is a child safety API that detects grooming, bullying, self-harm, fraud, and other harms across text, voice, image, and video. It covers all nine KOSA (Kids Online Safety Act) harm categories with age-calibrated risk scoring, conversation-aware analysis, and identity/age verification. Use the REST API via SDKs (Node.js, Python, Swift, Kotlin, Flutter, React Native, .NET, Unity, CLI) or the MCP server for AI agents. Primary docs: https://docs.tuteliq.ai. Key endpoints: `/safety/unsafe`, `/safety/grooming`, `/fraud/social-engineering`, `/verify/age`, `/verify/identity`. API key required; store in environment variables, never hardcode.\n\n## When to use\n\nReach for Tuteliq when:\n- Building moderation systems for platforms where minors interact (gaming, social, ed-tech, messaging)\n- Implementing KOSA compliance or COPPA parental consent flows\n- Detecting grooming patterns across multi-turn conversations\n- Analyzing user-generated content (text, voice, images, video) for safety\n- Verifying user age or identity before granting access\n- Routing moderation alerts to human reviewers with severity and recommended actions\n- Processing conversations longer than 20 turns (use continuation tokens to preserve trajectory)\n- Building AI agent workflows for incident triage or compliance reporting (use MCP server)\n\n## Quick reference\n\n### Core detection endpoints\n\n| Endpoint | Input | Cost | Use for |\n|----------|-------|------|---------|\n| `detectUnsafe` | Text | 2 credits | Single-message safety check across all KOSA categories |\n| `detectGrooming` | Conversation | 3 per 10 msgs | Multi-turn grooming pattern detection with per-message trajectory |\n| `detectBullying` | Text or conversation | 2 credits | Bullying, harassment, cyberstalking |\n| `detectSocialEngineering` | Text | 2 credits | Authority impersonation, credential theft, urgency manipulation |\n| `detectRomanceScam` | Text | 2 credits | Love-bombing, financial requests, isolation patterns |\n| `detectMuleRecruitment` | Text | 2 credits | Money mule recruitment, account sharing, laundering language |\n| `analyseMulti` | Text | 1 + N credits | Run up to 10 detectors in parallel (cheaper than individual calls) |\n\n### Verification endpoints\n\n| Endpoint | Input | Cost | Returns |\n|----------|-------|------|---------|\n| `verifyAge` (biometric) | Selfie | 10 credits | Age range, is_minor, confidence |\n| `verifyAge` (document) | ID front/back | 20 credits | Age range, document type, MRZ validation |\n| `verifyIdentity` | ID + selfie + liveness | 25 credits | Full name, DOB, face match, liveness passed |\n\n### Media analysis\n\n| Endpoint | Input | Cost | Notes |\n|----------|-------|------|-------|\n| `analyzeVoice` | Audio file | 21+ credits | Base 21 (first 60s) + 15 per extra minute |\n| `analyzeImage` | Image | 7 credits | Vision + OCR + safety analysis |\n| `analyzeVideo` | Video | 95 credits | Frame extraction + per-frame vision (max 10 min) |\n\n### Context fields (improve accuracy)\n\n```typescript\n{\n  age_group: \"10-12\" | \"13-15\" | \"16-17\" | \"under-10\",  // Triggers age-calibrated scoring\n  language: \"en\" | \"de\" | \"sv\" | ... ,                   // ISO 639-1; auto-detected if omitted\n  platform: \"Discord\" | \"Roblox\" | \"WhatsApp\",           // Adjusts for platform norms\n  conversation_history: [{ role: \"child\" | \"stranger\", content: \"...\" }],  // For multi-turn\n  sender_trust: \"verified\" | \"trusted\" | \"unknown\",      // Suppresses false positives\n  country: \"GB\" | \"US\" | \"SE\"                            // ISO 3166-1 alpha-2; enables crisis helplines\n}\n```\n\n### Response fields (all detection endpoints)\n\n| Field | Type | Meaning |\n|-------|------|---------|\n| `detected` / `unsafe` | boolean | Clear yes/no for routing |\n| `severity` | string | `low`, `medium`, `high`, or `critical` (age-calibrated) |\n| `risk_score` | float | 0.0\u20131.0 for threshold-based automation |\n| `categories` | array | Which harm categories triggered (e.g., `[\"grooming\", \"secrecy\"]`) |\n| `confidence` | float | Model confidence in the classification |\n| `rationale` | string | Human-readable explanation for audit trails |\n| `recommended_action` | string | Routing key: `log`, `flag_for_review`, `immediate_intervention` |\n| `message_analysis` | array | Per-message risk breakdown (when `conversation_history` provided) |\n| `credits_used` | integer | Credits consumed by this call |\n\n## Decision guidance\n\n### When to use conversation_history vs. continuation_token\n\n| Scenario | Use | Why |\n|----------|-----|-----|\n| Single message or short burst (< 5 turns) | `conversation_history` | Simpler; no token management |\n| Long conversation (20+ turns) | `continuation_token` | Preserves trajectory state across calls; privacy-first (no server storage) |\n| Conversation exceeds 50 turns | `continuation_token` + chunking | Split into 10\u201315 turn windows; pass token forward |\n| GDPR/privacy-sensitive | `continuation_token` | Tuteliq never stores conversation text; only derived signals in token |\n\n### When to use each detection endpoint\n\n| Content | Endpoint | Reason |\n|---------|----------|--------|\n| Single message, any harm type | `detectUnsafe` | Covers all 9 KOSA categories in one call |\n| Multi-turn conversation, grooming risk | `detectGrooming` | Detects six tactics (flattery, secrecy, isolation, boundary-pushing, photo/meeting requests) |\n| Multi-turn conversation, other harms | `detectBullying`, `detectCoerciveControl`, etc. | Trajectory-aware; returns per-message risk breakdown |\n| Multiple harm types on same text | `analyseMulti` | Cheaper than individual calls; parallel execution |\n| Fraud/scam targeting minors | `detectSocialEngineering`, `detectRomanceScam`, `detectMuleRecruitment` | Specialized playbooks for each scam type |\n\n### When to verify age vs. identity\n\n| Use case | Endpoint | Tier | Why |\n|----------|----------|------|-----|\n| Age gate on sign-up | `verifyAge` (biometric) | Pro | Fast, frictionless; selfie only |\n| COPPA parental consent | `verifyAge` (document) | Pro | Confirms minor; then verify parent with `verifyIdentity` |\n| Moderator/admin verification | `verifyIdentity` | Business | Full KYC: document + face match + liveness |\n| High-assurance age gate | `verifyAge` (combined) | Pro | Document + biometric cross-reference |\n\n## Workflow\n\n### Typical moderation workflow\n\n1. **Receive content** \u2014 User sends message, uploads image, or starts voice call.\n2. **Choose detection endpoint** \u2014 Single message \u2192 `detectUnsafe`; conversation \u2192 `detectGrooming` or `detectBullying`; fraud \u2192 `detectSocialEngineering`.\n3. **Pass context** \u2014 Include `age_group` (from verified age or profile), `platform`, `conversation_history` if available.\n4. **Check recommended_action** \u2014 Branch on this field, not severity alone. Values: `log`, `flag_for_review`, `immediate_intervention`.\n5. **Route to moderator** \u2014 If `flag_for_review` or higher, queue for human review with severity, risk_score, rationale, and per-message breakdown.\n6. **For long conversations** \u2014 If > 20 turns, chunk into 10\u201315 turn windows; pass `continuation_token` from each response to the next.\n7. **Track credits** \u2014 Monitor `X-Credits-Remaining` header and `credits_used` in response; set low-balance alerts in dashboard.\n\n### Age verification workflow (sign-up)\n\n1. **Request selfie** \u2014 Prompt user to take a selfie.\n2. **Call verifyAge** \u2014 `method: \"biometric\"` for speed, or `method: \"combined\"` for higher assurance (requires document).\n3. **Store age_group** \u2014 Use returned `age_range` (e.g., `\"13-15\"`) in all future safety calls.\n4. **If under 13 (COPPA)** \u2014 Verify parent identity with `verifyIdentity`; store parental consent record.\n5. **Use verified age in detection** \u2014 Pass `age_group` to all safety endpoints for properly calibrated risk scoring.\n\n### MCP server workflow (for AI agents)\n\n1. **Add server** \u2014 Point Claude/Cursor to `https://api.tuteliq.ai/mcp`.\n2. **Authenticate** \u2014 Browser sign-in; token stored by client.\n3. **Use tools** \u2014 Agent can call ~80 tools: `detect_grooming`, `batch_review_incidents`, `get_usage`, etc.\n4. **Limitations** \u2014 Agent can only `confirm` incidents, not resolve or reopen (human moderator only).\n5. **No API key needed** \u2014 OAuth handles auth; no config file required.\n\n## Common gotchas\n\n- **Don't branch on severity alone.** Always branch on `recommended_action` \u2014 a reassembled grooming attempt (fragmented across many short messages) scores lower severity but still gets `immediate_intervention`.\n- **Pass age_group in every request.** Omitting it defaults to the most protective bracket; you lose age-appropriate calibration.\n- **Grooming requires conversation, not single messages.** A single message rarely proves grooming. Pass `conversation_history` or use `continuation_token` to preserve multi-turn context.\n- **Conversation_history is stateless; continuation_token is stateful.** If you re-send the same conversation without the token, you lose the escalation signal. For long conversations, always use the token.\n- **Continuation tokens expire in 24 hours.** If a token expires, drop it and re-seed with fresh `conversation_history`.\n- **Never hardcode API keys.** Use environment variables, secrets managers, or (for MCP) OAuth.\n- **Batch requests cost less.** `analyseMulti` with 3 endpoints costs 4 credits (1 base + 1 per endpoint), not 6.\n- **Verification requires clear images.** Poor lighting, glare, or low resolution causes OCR/face-detection failures. Provide user feedback to retake.\n- **Document expiry is checked automatically.** Expired documents fail verification; no override.\n- **Age signals prevent false positives.** Pass `context.child_age` and `context.participant_age` to grooming detection; adult-to-adult conversations short-circuit with `out_of_scope_adults`.\n\n## Verification checklist\n\nBefore submitting work:\n\n- [ ] API key is stored in environment variables, not hardcoded\n- [ ] All detection calls include `age_group` in context (or document why it's omitted)\n- [ ] Grooming/bullying detection uses `conversation_history` or `continuation_token` (not single messages)\n- [ ] Long conversations (> 20 turns) use `continuation_token` to preserve trajectory\n- [ ] Moderation routing branches on `recommended_action`, not severity\n- [ ] Error handling includes retry logic for transient errors (500, 503, rate limits)\n- [ ] Credit usage is tracked; low-balance alerts are configured\n- [ ] Verification flows include clear user feedback for retakes (poor image quality, face not detected)\n- [ ] GDPR/COPPA compliance: age verification is stored; conversation text is not\n- [ ] MCP agent workflows only call `confirm` on incidents; escalation/resolution stays with humans\n\n## Resources\n\n**Comprehensive page listing:** https://docs.tuteliq.ai/llms.txt\n\n**Critical documentation:**\n- [Quickstart](https://docs.tuteliq.ai/quickstart) \u2014 Make your first API call in 5 minutes\n- [How It Works](https://docs.tuteliq.ai/how-it-works) \u2014 Detection pipeline, context engine, age calibration, response generation\n- [Grooming Detection](https://docs.tuteliq.ai/grooming-detection) \u2014 Six tactics, per-message trajectory, severity mapping\n- [Continuation Tokens](https://docs.tuteliq.ai/continuation-tokens) \u2014 Privacy-first multi-turn analysis without server storage\n- [Verification](https://docs.tuteliq.ai/verification) \u2014 Age and identity verification, document validation, fraud prevention\n- [Error Handling](https://docs.tuteliq.ai/error-handling) \u2014 Error codes, retry strategies, SDK error types\n- [Credits](https://docs.tuteliq.ai/credits) \u2014 Per-endpoint costs, usage tracking, billing\n- [MCP Server](https://docs.tuteliq.ai/mcp-server) \u2014 Connect AI agents; ~80 tools for moderation and compliance\n\n---\n\n> For additional documentation and navigation, see: https://docs.tuteliq.ai/llms.txt",
                "uri": "mintlify://skills/tuteliqab"
              }
            ]
          }
        },
        "resource_uri": "mintlify://skills/tuteliqab",
        "url": "https://docs.tuteliq.ai/mcp"
      },
      "latency_ms": 139.22,
      "status": "ok"
    },
    "resources_list": {
      "details": {
        "headers": {
          "content-type": "text/event-stream",
          "strict-transport-security": "max-age=63072000"
        },
        "http_status": 200,
        "payload": {
          "id": 5,
          "jsonrpc": "2.0",
          "result": {
            "resources": [
              {
                "description": "Use when building child safety features, content moderation systems, or age-verification flows. Agents should reach for this skill when implementing KOSA compliance, detecting grooming/bullying/fraud, analyzing voice/image/video for safety, or verifying user age and identity.",
                "mimeType": "text/markdown",
                "name": "tuteliqab",
                "uri": "mintlify://skills/tuteliqab"
              }
            ]
          }
        },
        "url": "https://docs.tuteliq.ai/mcp"
      },
      "latency_ms": 160.55,
      "status": "ok"
    },
    "schema_divergence_probe": {
      "details": {
        "auth_scheme_mismatch": false,
        "card_auth_schemes": [],
        "card_server_name": "Tuteliq Docs MCP",
        "card_server_version": "1.0.0",
        "compared_dimensions": [
          "server_name",
          "server_version",
          "declared_vs_observed_auth",
          "tool_membership",
          "parameter_names",
          "required_parameters",
          "parameter_types",
          "output_schema_presence"
        ],
        "compared_tool_count": 2,
        "live_oauth_observed": false,
        "live_server_name": "Tuteliq",
        "live_server_version": "1.0.0",
        "server_name_mismatch": true,
        "server_version_mismatch": false,
        "severity": "critical",
        "tool_divergences": [],
        "tools_missing_from_card": [
          "submit_feedback"
        ],
        "tools_missing_from_live": [],
        "tools_with_omitted_schema": []
      },
      "latency_ms": null,
      "status": "error"
    },
    "server_card": {
      "details": {
        "headers": {
          "content-type": "application/json",
          "strict-transport-security": "max-age=63072000"
        },
        "http_status": 200,
        "payload": {
          "authentication": "none",
          "capabilities": {
            "resources": true,
            "tools": true
          },
          "description": "Search and retrieve Tuteliq documentation",
          "name": "Tuteliq Docs MCP",
          "serverInfo": {
            "name": "Tuteliq Docs MCP",
            "version": "1.0.0"
          },
          "tools": [
            {
              "annotations": {
                "destructiveHint": false,
                "idempotentHint": true,
                "openWorldHint": false,
                "readOnlyHint": true
              },
              "description": "Search across the Tuteliq knowledge base to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about Tuteliq, find specific documentation, understand how features work, or locate implementation details. The search returns contextual content with titles and direct links to the documentation pages. If you need the full content of a specific page, use the query_docs_filesystem tool to `head` or `cat` the page path (append `.mdx` to the path returned from search \u2014 e.g. `head -200 /api-reference/create-customer.mdx`).",
              "inputSchema": {
                "properties": {
                  "query": {
                    "description": "A query to search the content with.",
                    "type": "string"
                  }
                },
                "required": [
                  "query"
                ],
                "type": "object"
              },
              "name": "search_tuteliq"
            },
            {
              "annotations": {
                "destructiveHint": false,
                "idempotentHint": true,
                "openWorldHint": false,
                "readOnlyHint": true
              },
              "description": "Run a read-only shell-like query against a virtualized, in-memory filesystem rooted at `/` that contains ONLY the Tuteliq documentation pages and OpenAPI specs. This is NOT a shell on any real machine \u2014 nothing runs on the user's computer, the server host, or any network. The filesystem is a sandbox backed by documentation chunks.\n\nThis is how you read documentation pages: there is no separate \"get page\" tool. To read a page, pass its `.mdx` path (e.g. `/quickstart.mdx`, `/api-reference/create-customer.mdx`) to `head` or `cat`. To search the docs with exact keyword or regex matches, use `rg`. To understand the docs structure, use `tree` or `ls`.\n\n**Workflow:** Start with the search tool for broad or conceptual queries like \"how to authenticate\" or \"rate limiting\". Use this tool when you need exact keyword/regex matching, structural exploration, or to read the full content of a specific page by path.\n\nSupported commands: rg (ripgrep), grep, find, tree, ls, cat, head, tail, stat, wc, sort, uniq, cut, sed, awk, jq, plus basic text utilities. No writes, no network, no process control. Run `--help` on any command for usage.\n\nEach call is STATELESS: the working directory always resets to `/` and no shell variables, aliases, or history carry over between calls. If you need to operate in a subdirectory, chain commands in one call with `&&` or pass absolute paths (e.g., `cd /api-reference && ls` or `ls /api-reference`). Do NOT assume that `cd` in one call affects the next call.\n\nExamples:\n- `tree / -L 2` \u2014 see the top-level directory layout\n- `rg -il \"rate limit\" /` \u2014 find all files mentioning \"rate limit\"\n- `rg -C 3 \"apiKey\" /api-reference/` \u2014 show matches with 3 lines of context around each hit\n- `head -80 /quickstart.mdx` \u2014 read the top 80 lines of a specific page\n- `head -80 /quickstart.mdx /installation.mdx /guides/first-deploy.mdx` \u2014 read multiple pages in one call\n- `cat /api-reference/create-customer.mdx` \u2014 read a full page when you need everything\n- `cat /openapi/spec.json | jq '.paths | keys'` \u2014 list OpenAPI endpoints\n\nOutput is truncated to 30KB per call. Prefer targeted `rg -C` or `head -N` over broad `cat` on large files. To read only the relevant sections of a large file, use `rg -C 3 \"pattern\" /path/file.mdx`. Batch multiple file reads into a single `head` or `cat` call whenever possible.\n\nWhen referencing pages in your response to the user, convert filesystem paths to URL paths by removing the `.mdx` extension. For example, `/quickstart.mdx` becomes `/quickstart` and `/api-reference/overview.mdx` becomes `/api-reference/overview`.",
              "inputSchema": {
                "properties": {
                  "command": {
                    "description": "A shell command to run against the virtualized documentation filesystem (e.g., `rg -il \"keyword\" /`, `tree / -L 2`, `head -80 /path/file.mdx`).",
                    "type": "string"
                  }
                },
                "required": [
                  "command"
                ],
                "type": "object"
              },
              "name": "query_docs_filesystem_tuteliq"
            }
          ],
          "transport": "http",
          "url": "https://tuteliqab.main-kill-isr.mintlify.me/mcp",
          "version": "1.0.0"
        },
        "url": "https://docs.tuteliq.ai/.well-known/mcp/server-card.json"
      },
      "latency_ms": 201.57,
      "status": "ok"
    },
    "session_resume_probe": {
      "details": {
        "protocol_version": "2025-03-26",
        "reason": "no_session_id",
        "resume_expected": true,
        "transport": "streamable-http"
      },
      "latency_ms": null,
      "status": "warning"
    },
    "step_up_auth_probe": {
      "details": {
        "auth_required_checks": [],
        "broad_scopes": [],
        "challenge_headers": [],
        "minimal_scope_documented": false,
        "oauth_present": false,
        "scope_specificity_ratio": 0.0,
        "step_up_signals": [],
        "supported_scopes": []
      },
      "latency_ms": null,
      "status": "missing"
    },
    "tool_snapshot_probe": {
      "details": {
        "added": [],
        "changed_outputs": [],
        "current_tool_count": 3,
        "previous_tool_count": 3,
        "removed": [],
        "similarity": 1.0
      },
      "latency_ms": null,
      "status": "ok"
    },
    "tools_list": {
      "details": {
        "headers": {
          "content-type": "text/event-stream",
          "strict-transport-security": "max-age=63072000"
        },
        "http_status": 200,
        "payload": {
          "id": 2,
          "jsonrpc": "2.0",
          "result": {
            "tools": [
              {
                "annotations": {
                  "destructiveHint": false,
                  "idempotentHint": true,
                  "openWorldHint": false,
                  "readOnlyHint": true
                },
                "description": "Search across the Tuteliq knowledge base to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about Tuteliq, find specific documentation, understand how features work, or locate implementation details. The search returns contextual content with titles and direct links to the documentation pages. If you need the full content of a specific page, use the query_docs_filesystem tool to `head` or `cat` the page path (append `.mdx` to the path returned from search \u2014 e.g. `head -200 /api-reference/create-customer.mdx`).",
                "execution": {
                  "taskSupport": "forbidden"
                },
                "inputSchema": {
                  "$schema": "http://json-schema.org/draft-07/schema#",
                  "additionalProperties": false,
                  "properties": {
                    "query": {
                      "description": "Search query",
                      "type": "string"
                    }
                  },
                  "required": [
                    "query"
                  ],
                  "type": "object"
                },
                "name": "search_tuteliq",
                "title": "Search documentation"
              },
              {
                "annotations": {
                  "destructiveHint": false,
                  "idempotentHint": true,
                  "openWorldHint": false,
                  "readOnlyHint": true
                },
                "description": "Run a read-only shell-like query against a virtualized, in-memory filesystem rooted at `/` that contains ONLY the Tuteliq documentation pages and OpenAPI specs. This is NOT a shell on any real machine \u2014 nothing runs on the user's computer, the server host, or any network. The filesystem is a sandbox backed by documentation chunks.\n\nThis is how you read documentation pages: there is no separate \"get page\" tool. To read a page, pass its `.mdx` path (e.g. `/quickstart.mdx`, `/api-reference/create-customer.mdx`) to `head` or `cat`. To search the docs with exact keyword or regex matches, use `rg`. To understand the docs structure, use `tree` or `ls`.\n\n**Workflow:** Start with the search tool for broad or conceptual queries like \"how to authenticate\" or \"rate limiting\". Use this tool when you need exact keyword/regex matching, structural exploration, or to read the full content of a specific page by path.\n\nSupported commands: rg (ripgrep), grep, find, tree, ls, cat, head, tail, stat, wc, sort, uniq, cut, sed, awk, jq, plus basic text utilities. No writes, no network, no process control. Run `--help` on any command for usage.\n\nEach call is STATELESS: the working directory always resets to `/` and no shell variables, aliases, or history carry over between calls. If you need to operate in a subdirectory, chain commands in one call with `&&` or pass absolute paths (e.g., `cd /api-reference && ls` or `ls /api-reference`). Do NOT assume that `cd` in one call affects the next call.\n\nExamples:\n- `tree / -L 2` \u2014 see the top-level directory layout\n- `rg -il \"rate limit\" /` \u2014 find all files mentioning \"rate limit\"\n- `rg -C 3 \"apiKey\" /api-reference/` \u2014 show matches with 3 lines of context around each hit\n- `head -80 /quickstart.mdx` \u2014 read the top 80 lines of a specific page\n- `head -80 /quickstart.mdx /installation.mdx /guides/first-deploy.mdx` \u2014 read multiple pages in one call\n- `cat /api-reference/create-customer.mdx` \u2014 read a full page when you need everything\n- `cat /openapi/spec.json | jq '.paths | keys'` \u2014 list OpenAPI endpoints\n\nOutput is truncated to 30KB per call. Prefer targeted `rg -C` or `head -N` over broad `cat` on large files. To read only the relevant sections of a large file, use `rg -C 3 \"pattern\" /path/file.mdx`. Batch multiple file reads into a single `head` or `cat` call whenever possible.\n\nWhen referencing pages in your response to the user, convert filesystem paths to URL paths by removing the `.mdx` extension. For example, `/quickstart.mdx` becomes `/quickstart` and `/api-reference/overview.mdx` becomes `/api-reference/overview`.",
                "execution": {
                  "taskSupport": "forbidden"
                },
                "inputSchema": {
                  "$schema": "http://json-schema.org/draft-07/schema#",
                  "additionalProperties": false,
                  "properties": {
                    "command": {
                      "description": "A shell command to run against the virtualized documentation filesystem (e.g., `rg -il \"keyword\" /`, `tree / -L 2`, `head -80 /path/file.mdx`).",
                      "type": "string"
                    }
                  },
                  "required": [
                    "command"
                  ],
                  "type": "object"
                },
                "name": "query_docs_filesystem_tuteliq"
              },
              {
                "annotations": {
                  "destructiveHint": false,
                  "idempotentHint": false,
                  "openWorldHint": true,
                  "readOnlyHint": false
                },
                "description": "Report a problem with this documentation site so the docs team can fix it. Use when a documentation page is incorrect, outdated, confusing, incomplete, or has a broken example. This is for feedback about the documentation content itself \u2014 not for product support requests or feedback about this tool or assistant.",
                "execution": {
                  "taskSupport": "forbidden"
                },
                "inputSchema": {
                  "$schema": "http://json-schema.org/draft-07/schema#",
                  "additionalProperties": false,
                  "properties": {
                    "feedback": {
                      "description": "A clear description of the documentation issue or suggestion \u2014 what is incorrect, outdated, missing, or confusing.",
                      "minLength": 1,
                      "type": "string"
                    },
                    "path": {
                      "description": "The documentation page path the feedback is about (e.g., the page you were reading, such as `/quickstart`).",
                      "minLength": 1,
                      "type": "string"
                    }
                  },
                  "required": [
                    "path",
                    "feedback"
                  ],
                  "type": "object"
                },
                "name": "submit_feedback",
                "title": "Submit documentation feedback"
              }
            ]
          }
        },
        "url": "https://docs.tuteliq.ai/mcp"
      },
      "latency_ms": 220.95,
      "status": "ok"
    },
    "transport_compliance_probe": {
      "details": {
        "bad_protocol_error": null,
        "bad_protocol_headers": {
          "content-type": "application/json",
          "strict-transport-security": "max-age=63072000"
        },
        "bad_protocol_payload": {
          "error": {
            "code": -32000,
            "message": "Bad Request: Unsupported protocol version: 1999-99-99 (supported versions: 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)"
          },
          "id": null,
          "jsonrpc": "2.0"
        },
        "bad_protocol_status_code": 400,
        "delete_error": null,
        "delete_status_code": null,
        "expired_session_error": null,
        "expired_session_status_code": null,
        "issues": [
          "missing_session_id",
          "missing_protocol_header"
        ],
        "last_event_id_visible": false,
        "protocol_header_present": false,
        "requested_protocol_version": "2025-03-26",
        "session_id_present": false,
        "transport": "streamable-http"
      },
      "latency_ms": 135.73,
      "status": "warning"
    },
    "utility_coverage_probe": {
      "details": {
        "completions": {
          "advertised": false,
          "live_probe": "not_executed",
          "sample_target": {
            "type": "resource",
            "uri": "mintlify://skills/tuteliqab"
          }
        },
        "initialize_capability_keys": [
          "resources",
          "tools"
        ],
        "pagination": {
          "metadata_signal": false,
          "next_cursor_methods": [],
          "supported": false
        },
        "tasks": {
          "advertised": false,
          "http_status": 200,
          "probe_status": "missing"
        }
      },
      "latency_ms": 60.26,
      "status": "missing"
    }
  },
  "failures": {
    "oauth_authorization_server": {
      "reason": "no_authorization_server"
    },
    "oauth_protected_resource": {
      "error": "Client error '404 Not Found' for url 'https://docs.tuteliq.ai/.well-known/oauth-protected-resource'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
      "url": "https://docs.tuteliq.ai/.well-known/oauth-protected-resource"
    },
    "openid_configuration": {
      "reason": "no_authorization_server"
    },
    "schema_divergence_probe": {
      "auth_scheme_mismatch": false,
      "card_auth_schemes": [],
      "card_server_name": "Tuteliq Docs MCP",
      "card_server_version": "1.0.0",
      "compared_dimensions": [
        "server_name",
        "server_version",
        "declared_vs_observed_auth",
        "tool_membership",
        "parameter_names",
        "required_parameters",
        "parameter_types",
        "output_schema_presence"
      ],
      "compared_tool_count": 2,
      "live_oauth_observed": false,
      "live_server_name": "Tuteliq",
      "live_server_version": "1.0.0",
      "server_name_mismatch": true,
      "server_version_mismatch": false,
      "severity": "critical",
      "tool_divergences": [],
      "tools_missing_from_card": [
        "submit_feedback"
      ],
      "tools_missing_from_live": [],
      "tools_with_omitted_schema": []
    }
  },
  "remote_url": "https://docs.tuteliq.ai/mcp",
  "server_card_payload": null,
  "server_identifier": "github-tuteliq/claude-plugin"
}
Capabilities
Use-case taxonomy
development search web security
Transport compliance drilldown
Probe status
Warning
Transport
streamable-http
Session header
no
Protocol header
no
Bad protocol response
400
DELETE teardown
n/a
Expired session retry
n/a
Last-Event-ID visible
no

Issues: missing_session_id, missing_protocol_header

Request association
Status
Warning
Advertised capabilities
roots
Observed idle methods
none
Violating methods
none
Probe HTTP status
n/a
Issues
none
Connector replay
Status
OK
Backward compatible
Would break after refresh
Added tools
none
Removed tools
none
Additive output changes
none
Required-argument replay breaks
ToolAdded required argsRemoved required args
No required-argument replay breaks detected.
Output-schema replay breaks
ToolRemoved propertiesAdded properties
No output-schema replay breaks detected.