Endpoints: 28,729MCP servers: 18,413Payout addresses: 2,070Paid calls: 1,528Letters: 13Defects: 1,322counted 2 min ago
teppi

Server definition

Hash
sha256:d36c59d3c82be958af6e853b96f82dd76010ad882b32a5c640b1f9633eee149c
What it is
What a remote MCP server returned when asked what it offers: 2 tools

The blob, as servednamed by its sha256

{ "instructions": null, "tools": [ { "description": "Use this when you need to check a website's GDPR compliance. Scans the URL plus /privacy-policy and /cookie-policy pages. Returns a compliance report in JSON.\n\nReturns: 1. complianceScore (0-100) 2. cookieConsent (detected boolean, type) 3. privacyPolicy (found boolean, url) 4. termsOfService (found boolean) 5. dpoContact (found boolean, email) 6. dataRetention (mentioned boolean) 7. thirdPartyTrackers array (Google Analytics, Facebook Pixel, etc.) 8. recommendations array.\n\nExample output: {\"url\":\"https://example.com\",\"complianceScore\":72,\"cookieConsent\":{\"detected\":true,\"type\":\"banner\"},\"privacyPolicy\":{\"found\":true,\"url\":\"/privacy\"},\"thirdPartyTrackers\":[\"Google Analytics\",\"Facebook Pixel\"],\"recommendations\":[\"Add DPO contact info\",\"Add data retention policy\"]}\n\nUse this BEFORE launching a website in the EU, FOR compliance audits, due diligence on acquisitions, and regular privacy monitoring.\n\nDo NOT use for PII in text -- use compliance_detect_pii instead. Do NOT use for tech detection -- use website_detect_tech_stack instead. Do NOT use for HTTP security headers -- use network_analyze_headers instead.", "inputSchema": { "properties": { "url": { "description": "Website URL to scan for GDPR compliance (e.g. https://example.com)", "type": "string" } }, "required": [ "url" ], "type": "object" }, "name": "compliance_scan_gdpr", "outputSchema": null }, { "description": "Use this when you need to check a website's GDPR compliance. Scans the URL plus /privacy-policy and /cookie-policy pages. Returns a compliance report in JSON. POST variant of compliance_scan_gdpr -- same params passed as JSON body instead of query string.\n\nReturns: 1. complianceScore (0-100) 2. cookieConsent (detected boolean, type) 3. privacyPolicy (found boolean, url) 4. termsOfService (found boolean) 5. dpoContact (found boolean, email) 6. dataRetention (mentioned boolean) 7. thirdPartyTrackers array (Google Analytics, Facebook Pixel, etc.) 8. recommendations array.\n\nExample output: {\"url\":\"https://example.com\",\"complianceScore\":72,\"cookieConsent\":{\"detected\":true,\"type\":\"banner\"},\"privacyPolicy\":{\"found\":true,\"url\":\"/privacy\"},\"thirdPartyTrackers\":[\"Google Analytics\",\"Facebook Pixel\"],\"recommendations\":[\"Add DPO contact info\",\"Add data retention policy\"]}\n\nUse this BEFORE launching a website in the EU, FOR compliance audits, due diligence on acquisitions, and regular privacy monitoring.\n\nDo NOT use for PII in text -- use compliance_detect_pii instead. Do NOT use for tech detection -- use website_detect_tech_stack instead. Do NOT use for HTTP security headers -- use network_analyze_headers instead.", "inputSchema": { "properties": { "url": { "description": "Website URL to scan for GDPR compliance (e.g. https://example.com)", "type": "string" } }, "required": [ "url" ], "type": "object" }, "name": "compliance_scan_gdpr", "outputSchema": null } ] }
Verify it yourselfcurl -s https://api.teppi.xyz/v1/evidence/sha256:d36c59d3c82be958af6e853b96f82dd76010ad882b32a5c640b1f9633eee149c | sha256sum