Skip to main content
Glama
598,297 tools. Updated 2026-09-21 21:56

"MCP server for checking project compliance with Polish law" matching MCP tools:

  • No arguments. Returns how many MCP servers have been read at source level, and the share of them with each category of finding (credential access, network egress, install-time execution, prompt-injection surface). Use this to judge whether checking a specific server is worth it before you look one up. It reports aggregate counts only - no per-server findings, and no verdict about any individual server.
    ConnectorNo auth
  • Run a source-free compiler smoke test through the real Axint pipeline. Use immediately after installing or connecting Axint so the current agent proves it did more than start the MCP server. Use: call immediately after install or first MCP connection; use validate or run for project checks. Inputs: format changes rendering only; the smoke test has no project inputs. Effects: read-only built-in compiler smoke test; writes no files and uses no network.
    ConnectorNo auth
  • Get Lenny Zeltser's IR cross-server handoff routes — when this MCP server can't fulfill a request, which other MCP servers (or fallback workflows) to consult. Surfaces a compact subset of `ir_load_context`. This server never requests your incident notes and instructs your AI to keep them local—guidelines flow to your AI for local analysis.
    ConnectorNo auth
  • <tool_description> Check nDSG/GDPR/EU AI Act compliance status for a media buy. Verifies privacy-native architecture compliance. </tool_description> <when_to_use> Before activating a campaign or for compliance audits. Checks: no cookies, no fingerprinting, contextual targeting, data residency, revenue transparency, consent basis, agent transparency. </when_to_use> <combination_hints> create_media_buy → get_compliance_status → activate (if compliant). Use for regulatory reporting and audit trails. </combination_hints> <output_format> Overall compliance status + individual check results with details. </output_format>
    ConnectorNo auth
  • Pre-flight security verdict for an MCP server invocation. Judges BOTH server-level reputation AND the server's dependency graph (npm/pypi) against the DugganUSA threat-intel corpus (1.13M+ IOCs, Shai-Hulud + typosquat + LOLBin families). Returns BLOCK / ADVISORY / REVIEW / ALLOW with severity, evidence, dep-graph summary, and HMAC-signed response. REVIEW means we hold NO RECORD of this server -- not that it is safe. Treat REVIEW as do-not-proceed-blindly: a brand-new attacker-published server looks exactly like this. ALLOW is only returned when we actually resolved the server and scanned its dependency graph; check known_to_us and dep_graph.scanned to confirm. Use this BEFORE invoking any other MCP server tool, especially ones installed from outside the official MCP Registry.
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • Polish law via Ansvar Gateway. Cited, OAuth + paid tier.

  • US federal and state cybersecurity/privacy law MCP server with cross-state comparison

  • Check any public URL RIGHT NOW: is it up, HTTP status, response time in ms. With kind:"mcp" it instead performs a real JSON-RPC initialize handshake against a streamable-HTTP MCP server endpoint and reports the server’s self-declared name/version/protocol — useful to tell "the MCP server is down" from "my client is misconfigured". Works without an API key (rate limit 30/hour per IP). For continuous monitoring with alerts, use create_monitor.
    ConnectorNo auth
  • Get the full compliance report for a completed scan. Returns score (0–100), financial risk in EUR, per-module results, and all violations with law references, fine estimates, and fix instructions. ⚠️ Only call after the scan is complete — check status first with get-scan-status. If called while scan is still running, returns current progress instead of an error.
    ConnectorNo auth
  • Search the AI Developer Toolkit documentation: 950+ guides on Cursor, Claude Code and OpenAI Codex, covering setup, agent workflows, hooks, MCP, testing, CI and deployment, in English and Polish. Returns at most 10 ranked results, each with a short snippet rather than the article text; an empty list means the corpus has nothing on the topic. Pass a result id to `fetch` for the full text.
    ConnectorNo auth
  • Return the exact TestGraph MCP server version and live deployment identity for diagnostics. Use this when checking a stale connection, endpoint mismatch or deployment issue; ordinary writes do not require a preceding version probe. Compare build_sha and deployment_id with the public /version endpoint when troubleshooting.
    ConnectorNo auth
  • Return the exact TestGraph MCP server version and live deployment identity for diagnostics. Use this when checking a stale connection, endpoint mismatch or deployment issue; ordinary writes do not require a preceding version probe. Compare build_sha and deployment_id with the public /version endpoint when troubleshooting.
    ConnectorNo auth
  • List every state in the GreenLight plug-in (balcony) solar registry with its legal status, law name, power cap, and verification state. GreenLight records enacted law only, verified field-by-field against the enrolled bill text; entries still marked pending are under review and unconfirmed. A state not listed is simply not in the registry; that says nothing about its law. Not legal advice.
    ConnectorNo auth
  • Trigger a FRESH SNMP walk against a device. Wraps POST /api/getSNMPWalkInfo/{deviceId} (permission: tools). SLOW and SIDE-EFFECTING. Server-side this shells out to walktool with a 1200s (20 minute) timeout and writes the result into the tools_walks table. Always try snmp_walk_last first; only call this when the cached walk is missing or known to be stale. MCP tool timeout is 1200s to match the server-side cap. If the device has many OIDs the call will take real wall-clock time — let it run; do not retry on timeout without first checking snmp_walk_last (the writeback may have completed even if the HTTP response stalled). Example: snmp_walk_run({device_id: 42})
    ConnectorNo auth
  • Clear the current auth token locally. Does NOT revoke server-side MCP tokens — revoke from the Neuron dashboard (Settings > MCP Tokens) for full invalidation.
    ConnectorNo auth
  • The upcoming AI-law effective / compliance-date calendar, derived deterministically from the curated corpus (no LLM). Each entry carries the verbatim source deadline text + primary-source URL; jurisdictions whose deadline text has no explicit date are reported only as meta.undated (never given an invented date). Free at every tier. This tool returns JSON; a compliance team can also SUBSCRIBE to the same feed as a live RFC 5545 calendar at https://ai-law-tracker.com/api/v1/deadlines?format=ical (webcal). NOT legal advice.
    ConnectorNo auth
  • Generate the personalized, source-grounded AI-law COMPLIANCE REPORT for a business profile — the same deterministic engine behind the $79 report product (no LLM in the grounded path, so it cannot invent a statute, deadline, or penalty). Returns the risk assessment (1–10 score + applicable obligations) PLUS a signed download_url for the rendered PDF. `state` and `sector` are required. Paid feature (Pro+); lower tiers get a preview (risk band + counts + one sample obligation) with the PDF/download withheld and an upgrade hint returned verbatim. Every obligation is anchored to a real law + primary source. Informational only — NOT legal advice. Data by AI Law Tracker (CC BY 4.0). Informational only — not legal advice.
    ConnectorNo auth
  • Returns VoiceFlip MCP server health and version metadata. No authentication required. Use this first to verify the server is reachable from your MCP client.
    ConnectorNo auth
  • Returns a machine-readable routing map for Spala MCP clients. Identifies public and authenticated tools, supported installer clients, OAuth endpoints, project handoff rules, and project-MCP entry points.
    ConnectorNo auth
  • Spēkā esošo likumu kategorijas ar aktu skaitu katrā — pārskats, kādas nozares datubāze sedz. / List law categories with counts.
    ConnectorNo auth
  • Use when building an AI governance compliance roadmap, advising on high-risk AI deployment obligations in Colorado, or briefing boards on upcoming US state AI regulatory requirements. Colorado SB 205 takes effect June 30, 2026 — the first comprehensive US state AI law. Returns developer and deployer obligations, high-risk AI system criteria, consumer rights, penalty structure ($20,000 per violation, AG enforcement), and comparison to EU AI Act. Example: AI-based loan underwriting system deployed in Colorado requires algorithmic impact assessment, plain-language consumer disclosure before first use, 3-year audit trail with AG access rights, and annual compliance certification — noncompliance triggers $20,000 per violation. Source: Colorado SB 205, enacted May 17, 2024. $0.10 USDC per call.
    ConnectorNo auth