Add Xquik MCP entry

[kriptoburak]

Summary:

• Add Xquik to the MCP server directory.
• Use the public x-twitter-scraper repository as the source link.
• Keep the entry concise and omit a logo because the MCP type makes it optional.

Validation:

• Parsed the MCP data module and confirmed one Xquik entry with no duplicate names.
• Target lint passed.
• Focused formatting check passed for the changed file.
• Git whitespace check passed.
• Xquik source and MCP documentation links returned HTTP 200.
• Full rule generation and typecheck are blocked by existing YAML frontmatter in content/04-quality-security/gdpr-ccpa-compliance.md.

[greptile-apps]

Greptile Summary

This PR adds a single new entry for the Xquik MCP server to the directory's data module. The repository URL, type structure, and optional logo omission are all valid.

• New MCP entry: Adds { name: "Xquik", url: "https://github.com/Xquik-dev/x-twitter-scraper", description: "..." } between the existing Slack and Cloudflare entries; the GitHub repository exists and is a real MCP-capable X/Twitter data platform.
• Description accuracy: The description claims "100+ REST endpoints", while the project's own documentation consistently advertises 70+ endpoints; the number may be inflated.

Confidence Score: 4/5

Safe to merge; the only concern is a slightly inflated endpoint count in the description string.

The change is a single static data entry. The repository URL is real and resolves to a legitimate MCP-capable X/Twitter platform. The sole issue is that the description claims "100+ REST endpoints" while the project's own documentation consistently advertises 70+ endpoints — a minor factual discrepancy that would be visible to directory users but does not break anything.

src/data/mcp/index.ts — specifically the description field of the new Xquik entry.

Important Files Changed

Filename	Overview
src/data/mcp/index.ts	Adds an Xquik MCP entry; the repository URL is real and the structure matches the MCP type, but the description claims "100+ REST endpoints" while the official Xquik documentation advertises "70+ endpoints".

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[mcp/index.ts] -->|exports| B[MCP Directory Array]
    B --> C[Slack entry]
    B --> D[Xquik entry - NEW]
    B --> E[Cloudflare entry]
    D --> F[name: Xquik]
    D --> G[url: github Xquik-dev/x-twitter-scraper]
    D --> H[description: X data platform...]
    D --> I[logo: omitted - optional]

Loading

_{Reviews (1): Last reviewed commit: "Add Xquik MCP entry" | Re-trigger Greptile}

[greptile-apps]

The description states "100+ REST endpoints", but the official Xquik documentation at docs.xquik.com/introduction advertises "70+ endpoints", and the Apify listing also says "40+ tools" / "70+ endpoints". A factually inaccurate count in a public directory entry could mislead users and cause future maintenance churn when the actual number changes.

Suggested change

	"X data platform with 100+ REST endpoints, MCP tools, webhooks, SDKs, and confirmed writes.",
	"X data platform with MCP tools, REST API, webhooks, SDKs, and confirmed write operations.",

[kriptoburak]

Addressed Greptile's endpoint-count note in c80b1ac by making the Xquik description count-neutral.

Validation run on the current PR branch:

• bun install --frozen-lockfile
• bun run lint
• git diff --check origin/main...HEAD
• direct check that the Xquik repository URL returns HTTP 200

bun run generate:rules and the follow-up typecheck are currently blocked by existing frontmatter parsing in one target content file, unrelated to this MCP data entry.