Skip to main content
Glama
649,985 tools. Updated 2026-10-12 04:10

"A resource for analyzing Polish legal acts" matching MCP tools:

  • GET /search — Cross-resource omni-search Cross-resource search across profiles, rooms, messages (incl. private DMs + group DMs you're in), events, and chapters in one round trip. Returns the top-N matches per resource, grouped by resource. Use this when you don't yet know which resource carries the answer — agents typically call this first, then drill into a specific `GET /search/<resource>` for more depth on a single bucket. There's no page param: when you hit the per-resource limit and want more, switch to the per-resource endpoint for that one. The events slice has a baked-in forward-looking default (events ending in the last 30 days or later, and currently enabled) — this matches the in-app "Search across DC" surface. Use `GET /search/events` directly to look further back in time. **Query syntax (`q=`):** plain words match with prefix + typo tolerance. Wrap a phrase in double quotes to require an exact ordered match — e.g. `q="remote work"`. AND/OR/NOT/parentheses are NOT parsed in `q=` — use the structured filter params below for boolean composition.
    ConnectorOAuth
  • Searches performances (concerts, theatre plays, festivals, stand-up shows and more) currently on sale on Biletyna.pl, a Polish ticketing platform. Every filter applies to a single performance, so city, date range and price always describe the same event. Results are deduplicated by title: each hit is the nearest matching performance of a distinct title, carrying its buy_url, venue, price and free places, plus aggregates for its city (city_events_total, city_next_event_date) and for the whole title (title_events_total, title_cities_total). Use "facets" for the distribution of matches across cities and categories. Only future performances are returned unless date_from says otherwise. Use list_performances(artist_id) for all dates of a title, get_title_details(artist_id) for its description and all cities. Full-text search is typo-tolerant. All content is in Polish. Prices are provided both in grosze (*_min_price) and PLN (*_min_price_pln); dates both as unix timestamps and human-readable *_text fields. "_meta.indexed_at" tells when the data was last refreshed - free places and prices are a snapshot from that moment.
    ConnectorNo auth
  • Get USER PROFILES of people who interacted with an Instagram post. Returns full user data (bio, followerCount, followingCount, etc.). RETURNS USER PROFILES: id, username, fullName, biography, followerCount, followingCount, isVerified, profilePicUrl. Use for analyzing WHO engaged with a post. NOT FOR COMMENT TEXT: To read the actual comment content (what people wrote), use getInstagramCommentsByPostId instead. INTERACTION TYPES: "commenters" (users who commented), "likers" (users who liked). WHEN TO USE THIS TOOL: Analyzing commenters/likers demographics, finding influencers who engaged, building audience profiles, network analysis of who interacts with posts. WHEN TO USE getInstagramCommentsByPostId: Reading comment text, sentiment analysis of what was said, analyzing discussion content. FAST (default, omit responseType or responseType="fast"): Returns up to 300 results directly (use limit param to reduce, e.g. limit=5). Auto API fallback for commenters when stale. PAGING (responseType="paging"): Async paginated results (1000 users per page with default fields), returns operationId - IMMEDIATELY call checkOperationStatus to get results. CSV export included via dataDumpExportOperationId. Supports pageNumber/tableName for subsequent pages. Optional fields (default: ["id", "username", "fullName"]). Available: biography, isPrivate, isVerified, followerCount, followingCount, mediaCount, profilePicUrl. This is a safe, read-only tool for analyzing searchable information.
    ConnectorOAuth
  • A reconstructed procurement lifecycle chain by chain_id: the linked sequence of related acts (e.g. commitment → award → contract → payments) with confidence and link method. Get a chain_id from the chain_id field of any act. A chain is ONE procurement's lifecycle, not everything an act references: an administrative umbrella cited by more than 25 acts (e.g. one annual expense-approval decision referenced by thousands of a buyer's acts) is deliberately NOT merged, so a chain never swallows a year of unrelated activity. Those references are still published — see the act's own references — they simply do not form a chain.
    ConnectorNo auth
  • Fetch the exact text of one article (or paragraph) of a Polish legal act. Use after search_law or another trusted source supplied the address and article key; never guess them. Deterministic lookup by act address (e.g. WDU19740240141) and article key (e.g. "133" or "Art. 133."). Optional paragraph_key (e.g. "1" or "§ 1.") narrows the result to a single paragraph.
    ConnectorNo auth
  • Search public, predominantly Polish-language msza.ai sermons plus sermon studies, Bible passages, prayers, songs, people, and places for focused topic, keyword, or relevance discovery. Returned source text stays in its stored language. Use it only when no exact ID or dedicated lookup applies; do not invoke it for a generic faith or prayer conversation without a request to discover msza.ai material, and do not invoke it automatically for every request. For a non-Polish topic, use one focused Polish query while preserving proper names, IDs, Bible references, and date, church, and content filters. Do not fan out translation variants; after an empty or weak topic result, use at most one useful Polish rephrase with the same constraints. Use days_back for rolling periods and date_from/date_to for any absolute historical period. Missing results do not prove absence. Returned hits are candidates: a query may match other session content, so verify selected sermon text and do not treat retrieval.topicMatch as evidence for every result. Returns source IDs, stable citation labels, short excerpts, dates, and links. Priest names are not stored.
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    Self-hosted design audit MCP server that reviews UI code against Nielsen's heuristics and an accessibility rubric, returning scores and fixable findings. It also enables verifying previously flagged issues against updated code.
    21 npm
    BSD 2-Clause "Simplified"
  • A
    license
    Not graded
    quality
    F
    maintenance
    MCP server providing access to Polish law statutes, provisions, case law, and EU law integrations, enabling natural language legal research, citation validation, and cross-referencing.
    33 npm
    7
    Apache 2.0

Matching MCP Connectors

  • Checks the structural integrity of translated resource dictionaries against a source dictionary y...

  • Know-your-business checks for Polish companies: KRS, owners, insolvency, sanctions, gazette notices.

  • PROJECT-SCOPED: this call acts only on the explicit project_id and returns the project identity with its result. Remove one keyframed travelling zoom by its id (see get_edl). Use remove_zoom for ordinary punch/ease zooms.
    ConnectorOAuth
  • Paid $0.01 public machine identity and payment-destination consistency assessment. Use immediately before an autonomous machine payment to compare the requested HTTPS endpoint, claimed service expectations, HTTP 402 challenge, resource binding, public discovery metadata, and prior PayeeProof observations. PayeeProof never authorizes the target payment, never forwards target payment credentials, and actively probes only anonymous public GET/HEAD requests under a bounded SSRF-safe contract; state-changing target methods require caller-observed 402 evidence. Missing evidence can remain unknown. This is not KYC, AML, sanctions screening, fraud certification, legal identity verification, legal advice, or a delivery guarantee.
    ConnectorNo auth
  • Purpose: ChatGPT-connector-standard document fetch by id from `search` results. Namespaces: `tool:{name}` returns the tool's full documentation and how to call it; `resource:{uri}` returns the resource's live data (core resources resolved server-side — also the bridge for clients without MCP resource support, e.g. Gemini); `signal:{market}:{symbol}` returns the symbol's latest combined research signal. Triggers: ChatGPT connectors / Deep Research call this after `search`. Clients without MCP resource support can call it directly with a known resource id, e.g. fetch("resource:market://global/summary"). When to call: whenever the full content behind a search result id is needed. Prerequisites: a valid id — from `search` results or a known namespace id. Next steps: for tool docs, call the named tool via tools/call; for signals, get_signal_detail / explain_decision for deeper evidence. Caveats: uncovered resource uris return description-only text (no fabricated data). `text` is a JSON document for resource/signal ids. Output: {id, title, text, url, metadata, disclaimer, is_investment_advice, data_classification} — flat envelope, OpenAI fixed shape.
    ConnectorNo auth
  • Discovers and ranks URLs from a domain's XML sitemaps to find the most significant pages (homepages, product pages, recently updated content) before analyzing them. Supports URL-pattern filtering and automatically flags robots.txt-blocked and already-tested pages. Legal/policy boilerplate (privacy, terms, cookies, disclaimers, refunds) is flagged legalPage:true with a -25 significance penalty; use the legalPages filter to drop it (exclude) or isolate it for a policy-coverage audit (only). Parameters group into three jobs: discovery (url), ranking and paging (limit, sort), and filtering (include and exclude URL patterns, excludeDisallowed, excludeTested, excludeScheduled, legalPages).
    ConnectorOAuth
  • Discovers and ranks URLs from a domain's XML sitemaps to find the most significant pages (homepages, product pages, recently updated content) before analyzing them. Supports URL-pattern filtering and automatically flags robots.txt-blocked and already-tested pages. Legal/policy boilerplate (privacy, terms, cookies, disclaimers, refunds) is flagged legalPage:true with a -25 significance penalty; use the legalPages filter to drop it (exclude) or isolate it for a policy-coverage audit (only). Parameters group into three jobs: discovery (url), ranking and paging (limit, sort), and filtering (include and exclude URL patterns, excludeDisallowed, excludeTested, excludeScheduled, legalPages).
    ConnectorNo auth
  • Find EU legal acts by CELEX/ELI identifier, official title, reviewed alias, or LEXICAL match on title and EuroVoc labels (not semantic); filter by EuroVoc topic id or label, Ansvar sector, document type and availability. Returns bounded candidates with per-edition currency state and hold reasons, a framework crosswalk to eu-regulations where the same act is keyed there, and exact search/lookup hints.
    ConnectorOAuth
  • Show a complete SIXTA analysis on a realistic sample (a gnarly production query plus its EXPLAIN output) for PostgreSQL or MySQL — no input needed. Offer this to first-time or empty-handed users who want to see what SIXTA finds before pasting their own SQL. Not for analyzing real artifacts — use the analysis tools for those.
    ConnectorOAuth
  • Compute statistics for a float vector or matrix of vectors: mean, std, L2 norm, min, max, sparsity, top-K indices. Useful for debugging embedding quality and analyzing vector distributions in a vector DB.
    ConnectorNo auth
  • Search Polish companies by name (fuzzy match). USE THIS when the user asks to find a Polish company, look up a firm by name, or get its NIP/KRS/REGON. Returns NIP, KRS, city, status and a profile URL. Data from the Polish court (KRS) and statistical (REGON) registers. Read-only.
    ConnectorNo auth
  • Get Polish public-procurement contracts awarded to a company (legal entity) by NIP, as published in the Public Procurement Bulletin (BZP). USE THIS for due diligence or sales intelligence when the user asks what public tenders or government contracts a company has won. Returns up to 25 most recent awards (subject, contracting authority, city, date, value) plus the total count and total value across all awards. Legal entities only. Read-only.
    ConnectorNo auth
  • Get the Legal Entity Identifier (LEI, ISO 17442) of a Polish company (legal entity) by NIP, from the GLEIF register. USE THIS when the user needs a company's LEI for cross-border or financial-market reporting (MiFID, EMIR, payments). Returns the LEI, the registered legal name and the LEI status. Coverage is partial. Legal entities only. Read-only.
    ConnectorNo auth
  • USE THIS to verify a Polish PESEL (national identification number) before relying on it — never assume 11 digits are valid. Checks the weighted mod-10 check digit. Call this for KYC/onboarding of Polish individuals.
    ConnectorNo auth
  • Sets the company's legal entity ending — the suffix that appears in the full legal name (e.g. "Inc.", "Corporation", "Co." for a C-Corp; "LLC", "L.L.C." for an LLC). Use one of the valid endings returned by formation_set_company_type. Set this BEFORE the company name so the full legal name is derived correctly.
    ConnectorNo auth
  • Validates the checksum of a 10-digit Polish tax identification number (NIP). Checksum uses weights 6 5 7 2 3 4 5 6 7 over the first 9 digits; sum mod 11 must equal the 10th digit. A sum mod 11 of 10 is itself invalid.
    ConnectorNo auth